Grrrr!! Access 2003 Database Corrupting On Exit

[suzanne]

I have a database that had been stable until 3 weeks ago. The Access
2003 database occasionally (a couple of times a week) gets corrupted
when the last user exits the application. At least, that's what I'm
assuming since they get no error while working.

If I make a copy of the database prior to the last user logging out,
that copied DB remains undamaged. If I attempt to log back the
original DB in once everyone is out, I get the dreaded "Unrecognized
file format" error message. The frustrating part is that I can't make
it happen consistently.

This customer is running on Windows 2000 SP4 and Access 2003. The
database in on a networked server.

By in large, their PCs are configured the same, except that one has a
higher version of: MSEXCL40.DLL (v 4.00.9025.0), MSTEXT40.DLL (v
4.00.9401.0) and MSXBDE40.dll (v 4.00.9025.0) Jet libraries.

I'm really pulling my hair out with this one. Has anyone run across a
similar problem? Any ideas of what could be causing the corruption?

[Tony Toews [MVP]]

su*****@dataaccent.com wrote:

>I have a database that had been stable until 3 weeks ago. The Access
2003 database occasionally (a couple of times a week) gets corrupted
when the last user exits the application. At least, that's what I'm
assuming since they get no error while working.

No, this is an invalid assumption. If a user is in a database when it is flagged for
corruption by another user the first user won't notice anything until they exit and
go back in. Access only checks for that flag when Access opens the MDB.

>If I make a copy of the database prior to the last user logging out,
that copied DB remains undamaged. If I attempt to log back the
original DB in once everyone is out, I get the dreaded "Unrecognized
file format" error message. The frustrating part is that I can't make
it happen consistently.

Corruption seldom happens consistently.

>By in large, their PCs are configured the same, except that one has a
higher version of: MSEXCL40.DLL (v 4.00.9025.0), MSTEXT40.DLL (v
4.00.9401.0) and MSXBDE40.dll (v 4.00.9025.0) Jet libraries.

Now this is interesting because according to the Microsoft's DLL Help Database
http://support.microsoft.com/dllhelp/ those DLLs are for Windows Server 2003 SP1.
That said that DLL Help database is sometimes rather out of date.

MSEXCL40.DLL is for "Microsoft Jet Excel Isam" and is for Microsoft Windows Server
2003 Service Pack 1.

MSTEXT40.DLL - Microsoft Jet Text Isam - Microsoft Windows Server 2003 Service Pack 1

MSXBDE40.dll - Microsoft Jet xBASE Isam - Microsoft Windows Server 2003 Service Pack
1

That said it doesn't really matter as those DLLs are not part of Jet itself. The
important DLL there is MSJET40.DLL. Are the versions consistent there?

>I'm really pulling my hair out with this one. Has anyone run across a
similar problem? Any ideas of what could be causing the corruption?

For more information on corruption including possible causes, determining the
offending PC, retrieving your data, links, official MS KB articles and a list of
vendors who state they can fix corruption see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[suzanne]

On Mar 21, 5:25 pm, "Tony Toews [MVP]" <[e-mail]:

[e-mail] wrote:

I have a database that had been stable until 3 weeks ago. The Access
2003 database occasionally (a couple of times a week) gets corrupted
when the last user exits the application. At least, that's what I'm
assuming since they get no error while working.

No, this is an invalid assumption. If a user is in a database when it is flagged for
corruption by another user the first user won't notice anything until they exit and
go back in. Access only checks for that flag when Access opens the MDB.

If I make a copy of the database prior to the last user logging out,
that copied DB remains undamaged. If I attempt to log back the
original DB in once everyone is out, I get the dreaded "Unrecognized
file format" error message. The frustrating part is that I can't make
it happen consistently.

Corruption seldom happens consistently.

By in large, their PCs are configured the same, except that one has a
higher version of: MSEXCL40.DLL (v 4.00.9025.0), MSTEXT40.DLL (v
4.00.9401.0) and MSXBDE40.dll (v 4.00.9025.0) Jet libraries.

Now this is interesting because according to the Microsoft's DLL Help Databasehttp://support.microsoft.com/dllhelp/those DLLs are for Windows Server 2003 SP1.
That said that DLL Help database is sometimes rather out of date.

MSEXCL40.DLL is for "Microsoft Jet Excel Isam" and is for Microsoft Windows Server
2003 Service Pack 1.

MSTEXT40.DLL - Microsoft Jet Text Isam - Microsoft Windows Server 2003 Service Pack 1

MSXBDE40.dll - Microsoft Jet xBASE Isam - Microsoft Windows Server 2003 Service Pack
1

That said it doesn't really matter as those DLLs are not part of Jet itself. The
important DLL there is MSJET40.DLL. Are the versions consistent there?

I'm really pulling my hair out with this one. Has anyone run across a
similar problem? Any ideas of what could be causing the corruption?

For more information on corruption including possible causes, determining the
offending PC, retrieving your data, links, official MS KB articles and a list of
vendors who state they can fix corruption see the Microsoft Access Corruption FAQ athttp://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm

Many thanks Tony. This was extremely useful information. You rule!!
S.