Question Error 3343 : Unrecognised database format (AC2007)

[AOB]

Hi guys,

I have a standard shared Access DB application (i.e. central BE on the network, multiple users running their own copy of the FE on their local machine) Has been in production for a while, no major issues.

New user has been added in recent weeks. My error logger has picked up an error he hit earlier today - doesn't appear to have been fatal (he hasn't come to me with a problem, suggesting he just "OK"d the error prompt and continued on - I need to confirm this with him though...)

Error was 3343 "Unrecognized database format 'C:\Temp\MyDB\MyDB.accde'."

Can see it was tripped on a particular form which queries certain data into a subform (so he was obviously able to open the FE and connect to the BE fine; it was several steps down the road where the error has occurred)

Have done some browsing and, somewhat worryingly, a lot of people talk of corruption, while others mention libraries (less worrying, but still...)

As I say, nobody's come to me to say there's a problem (yet), I only chanced upon it while checking in on my error log. And for all I know, he just closed that form, reopened it and it worked fine the second time.

Anybody know what might have caused the error and if I should be concerned?

Cheers!

AOB

 

[Uncle Gizmo]

I don't think this is it, but I thought it might be worth mentioning. If the locking file "*.laccdb" is not deleted when access closes it can cause the unrecognised database format error when you try and open the MS Access DB again. I don't know if 3343 is the right error code for a "locking file error".

 

[AOB]

Hmmm, yes I saw mention of that too; only problem is, there will be a locking file on the BE whenever anyone has the FE open (I use a persistant connection to maintain the locking file for the duration of a session, to speed up the queries, rather than creating and dumping the locking file for each query - I found this speeded things up immensely...) So the locking file is only deleted when everyone has disconnected?

And nobody else has had this error in 9 months of usage? Even this one particular user has only had it once in the few days since he started using it (I suspect the fact that it is happening to a relatively new user may be merely coincidence?..)