Corrupt Access database-Run time error 3343

[Carol28]

The application is written in VB6 and uses an Access 97 database. The application is used to track phone calls. The database is opened when a user logs on. We have multiple users. A compact is run on the database every morning.

The database becomes corrupt a couple times a week. A processor attempts to pull up information for a specific client, the VB app loads the data from access to a VB form. Before it loads to the form the vb app copies the information to a set of working tables in access. The processor then receives an error message that the database is corrupt and needs to be repaired(error 3343). Running the repair corrects the problem but requires everyone to log out.

The odd thing is this:
Anyone that is already logged into the VB app and connected to the database can continuing working and updating the database with phone information without a problem. Anyone trying to log into the VB application receives the message that the database is corrupt and they cannot login. This tells me that the database is really not corrupt.

If I keep the database open and the corruption occurs, I am able to look at and open all the tables. They look fine.

Any ideas on what is going on and how to fix it without getting everyone out of the application to repair it?

Thanks,
Carol

 

[cainemart]

ummm! Try Jet Compact, you can download it from Microsoft. Sometimes this utility will help out when Access can't for corruption.

cainebean

 

[psemianonymous]

http://groups.google.com/groups?hl=...+Search&meta=group%3Dcomp.databases.ms-access

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access