Thanks so much for that. I can't remember if I mentioned MS SQL Server originally -- I think I did, but it was years ago I started this thready. Unfortunately, for both me and the client involved, one of the programs that use SQL Server is our enterprise backup software, which is critical. However, your advice may help others whose software may not be as important. It's insane that this issue still exists in the current version. The developers at Intuit are well aware of what is causing the issue, and as someone who does SQL server backup development, it's disturbing they don't know how to fix it.