Scenario: Large Access 2000 application running on a server at a customers site. Data is stored in SQL 2000 on the server. A client machine and the server machine use the application at the same time. No problem with speed or functionality. SQL Server data is backed up from the application at close each night.
Problem: The user states that he gets an error message to repair the database after running the backup (this would happen before the access application is closed). Which he does. Then a second message is generated stating that "The database is in an unexpected state." He can not reopen the application unless I remove the old copy and replace it with a backup copy kept on the server for this purpose. I could understand data corruption but why would an .mde become corrupted on a SQL backup? Or is this only masking the real problem? Could the user be doing something that would cause this to happen, like having the application open on the client while running the backup from the server or maybe a network card or hub is dropping the connection for a split second? Or am I causing this with some code that I am not aware of.
There are only 3 real possibilities: user error, hardware problems, or coding errors. I can run the backup in my office 200 times in a day and not have any problems. I can even run the backup while a client machine has the application open and I can not reproduce the error. I just don't see any code that would cause this problem.
The user is upset and I am frustrated. Does anyone have any suggestions?
Problem: The user states that he gets an error message to repair the database after running the backup (this would happen before the access application is closed). Which he does. Then a second message is generated stating that "The database is in an unexpected state." He can not reopen the application unless I remove the old copy and replace it with a backup copy kept on the server for this purpose. I could understand data corruption but why would an .mde become corrupted on a SQL backup? Or is this only masking the real problem? Could the user be doing something that would cause this to happen, like having the application open on the client while running the backup from the server or maybe a network card or hub is dropping the connection for a split second? Or am I causing this with some code that I am not aware of.
There are only 3 real possibilities: user error, hardware problems, or coding errors. I can run the backup in my office 200 times in a day and not have any problems. I can even run the backup while a client machine has the application open and I can not reproduce the error. I just don't see any code that would cause this problem.
The user is upset and I am frustrated. Does anyone have any suggestions?