Unrecognized Database Format

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I really need some help with this...I'm on the verge of going nuts. I have a
back-end that 6-7 users link to with a front-end database. Almost twice a
day we are getting this "Unrecognized Database Format" error, which forces us
to log everyone out so that the back-end can be repaired. I've done a bunch
of research on MSDN here and other sites, and the issue seems to stem from
Jet 3.51 incompatability with Access 2000. So I went and updated all the PCs
and currently everyone has Access 2000, no one has Jet 3.51 at all (all are
using 4.0), DAO is not used or even referenced in the database, all the
databases have been created with Access 2000...as far as I can tell, I've
done everything that needs to be done -- but we're still getting this error.

Has anyone encountered extensive problems with this or have any ideas at all
on what I could do next? Thanks.
 
For Windows NT/2000

Server side, you add a Reg_Dword value named;
"EnableOplocks"
and set it's value to 0
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Been there did this some years back. Best solution is to migrate the Access
backends to SQL server and be done with it.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I really need some help with this...I'm on the verge of going nuts. I have
a
| back-end that 6-7 users link to with a front-end database. Almost twice a
| day we are getting this "Unrecognized Database Format" error, which forces
us
| to log everyone out so that the back-end can be repaired. I've done a
bunch
| of research on MSDN here and other sites, and the issue seems to stem from
| Jet 3.51 incompatability with Access 2000. So I went and updated all the
PCs
| and currently everyone has Access 2000, no one has Jet 3.51 at all (all
are
| using 4.0), DAO is not used or even referenced in the database, all the
| databases have been created with Access 2000...as far as I can tell, I've
| done everything that needs to be done -- but we're still getting this
error.
|
| Has anyone encountered extensive problems with this or have any ideas at
all
| on what I could do next? Thanks.
 
Dave -

Thanks for the response. Unfortunately, I'm just a guy in the Finance
department, and I have no administrative rights to PCs or to servers, so I
can't really try out your solution. I'm trying to avoid contacting my IT
department, because to be honest, they aren't very helpful and I end up
researching and solving the questions I ask them myself anyways.

I suppose the only thing I can do is test all the PCs individually by
performing every possible action in each of their front ends and checking the
back end to find out when and by whom it gets corrupted. Thanks.

Jeff
 
OK, but that isn't going to help you solve the problem.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Dave -
|
| Thanks for the response. Unfortunately, I'm just a guy in the Finance
| department, and I have no administrative rights to PCs or to servers, so I
| can't really try out your solution. I'm trying to avoid contacting my IT
| department, because to be honest, they aren't very helpful and I end up
| researching and solving the questions I ask them myself anyways.
|
| I suppose the only thing I can do is test all the PCs individually by
| performing every possible action in each of their front ends and checking
the
| back end to find out when and by whom it gets corrupted. Thanks.
|
| Jeff
 
If the problem is the OpLocks setting (and that is, at least, a strong
possibility) then you may be wasting your time. To the best of my knowledge,
changing the setting on the server is the only solution to that particular
problem.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.


goblinstands said:
Dave -

Thanks for the response. Unfortunately, I'm just a guy in the Finance
department, and I have no administrative rights to PCs or to servers, so I
can't really try out your solution. I'm trying to avoid contacting my IT
department, because to be honest, they aren't very helpful and I end up
researching and solving the questions I ask them myself anyways.

I suppose the only thing I can do is test all the PCs individually by
performing every possible action in each of their front ends and checking
the
back end to find out when and by whom it gets corrupted. Thanks.

Jeff


Dave Patrick said:
For Windows NT/2000

Server side, you add a Reg_Dword value named;
"EnableOplocks"
and set it's value to 0
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Been there did this some years back. Best solution is to migrate the
Access
backends to SQL server and be done with it.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I really need some help with this...I'm on the verge of going nuts. I
have
a
| back-end that 6-7 users link to with a front-end database. Almost
twice a
| day we are getting this "Unrecognized Database Format" error, which
forces
us
| to log everyone out so that the back-end can be repaired. I've done a
bunch
| of research on MSDN here and other sites, and the issue seems to stem
from
| Jet 3.51 incompatability with Access 2000. So I went and updated all
the
PCs
| and currently everyone has Access 2000, no one has Jet 3.51 at all (all
are
| using 4.0), DAO is not used or even referenced in the database, all the
| databases have been created with Access 2000...as far as I can tell,
I've
| done everything that needs to be done -- but we're still getting this
error.
|
| Has anyone encountered extensive problems with this or have any ideas
at
all
| on what I could do next? Thanks.
Click to expand...
Click to expand...
 
Back
Top