Database corruption question

[Gina Maylone]

Hi!

I have a client who is experiencing "unrecognized database format blablabla" every few days. I once again found myself looking for causes of db corruption, and the one that just kills me is "Concurrent Database Usage". Isn't an Access database, split properly, meant to be used by concurrent users?? There are 6 at the most using it concurrently. I have meant to address this before, but got sidetracked...Your feedback is always appreciated!

[ranman256]

this can happen if all users are in the SAME db. If you dont split the db, it can cause problems.

split the db , tables & forms(everything else)
put the tables (backend) on a share folder,
give EVERY user their own copy of the frontend (forms)
this should stop corruption.

[Gina Maylone]

It is split correctly. Everyone has their own FE and the BE is on server in a shared folder.

[JoeM]

The one user who is getting these error messages, are they using the same version of Access as everyone else?
If not, what version are they using, and what version is everyone else using?

[Gina Maylone]

I believe everyone has the same version, but I am double checking with the admin right now.

[CJ_London]

might also help if you clarify which 'database' has the error - the BE or the FE? From the posts so far, sounds like it is the FE? However only the backend is being used concurrently so the error message implies it is the BE.

The other question to clarify is how are your users connecting to the BE - via a wired lan? wirelessly?

[Gina Maylone]

That would only be true if the error is indeed caused by concurrent usage. The error was generated on the front end as far as I can tell, however, it is possible it came from the backend, I guess? I've seen the error pop up on another user's computer, compact and repair took care of it at that time. The FE's are hardwired to the server. Note, the error is intermittent. Making it difficult to track down. Thanks everyone for your input!

[CJ_London]

I guess?

If the BE was corrupted, all users would have a problem. Compact and repair will only impact the file that is compacted, presumably a front end.

Note that compact/repairing a file may not remove all corruption. It could still leave a 'seed' that can grow into another corruption. Better to provide the user with a fresh front end from your development area - even backups may carry that seed.

Does your FE create/delete temporary tables? If so, that can bloat the FE ultimately to the 2Gb limit and you will get corruption type error messages which compacting can resolve. Better to create your temp tables in a temporary db the destroy the temporary db when done.

[Gina Maylone]

I said "I guess" because I don't know for sure which generated the error (FE or BE). Is there a way I can be sure?

No temporary tables.

I'm going to create a new FE and import all the objects and send it over to them. Hopefully that will take care of the issue.

Thanks all!