Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / July 2004

Tip: Looking for answers? Try searching our database.

Backend corruption

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Don - 22 Jul 2004 21:40 GMT
I have a split database where the users keep the backend
in a shared folder on the network and then they copy the
frontend to their local computer.  It has code in it to
find the backend upon first opening the database.  This
all works to this point.  There are up to 8 users at any
time.  If more the one person enters data into the
database, it becomes corrupt within a few minutes.  An
error message appears stating "Unrecognized database
format   database/path/name".  Then records become
corrupted displaying #ERROR.  It seems that the more the
users, the quicker it corrupts.  The backend database
grows from a few KB to 100-200 KB starting from 340 KB.  
The .ldb file contains one or two user ids when it
corrupts and the users vary.

The database does NOT use User Groups or a Password
although they are all prompted for a password (they all
have a common .mdw file on their computers that has been
there from before my time).  The frontend consists of
three tabs, two of which have subforms created from
queries.

When making an MDE file for the frontend, Access
states "You can't create a Microsoft Access MDE database
from a database in Microsoft Access 2000 file format.  
Close the database and convert it to the current version
of Microsoft Access.  Then create the MDE database."  So I
converted the frontend to Access 2002 and then made the
MDE file.  I did not convert the backend.  Then I tried
with a converted backend and had the same results.

All users are at the following versions of Access/Jet:
    Microsoft Windows 2000
    Microsoft Access 2002 (10.3409.3501) SP-1
    msjet40.dll        4.0.6218.0  
(they also have msjet35.dll  3.51.2026.0)

The database properties:
Default open mode:         Shared
Default record locking:     Edited record
Open databases using record-level locking is checked
DDE operations:         Enable DDE refresh
OLE/DDE timeout:         30
Refresh interval:         60
Number of update retries:     2
ODBC refresh interval:     1500
Update retry interval:         250

I'm having a very difficult time pinpointing the problem.  
Any suggestions will GREATLY be appreciated!
Thank you!
Tony Toews - 23 Jul 2004 06:23 GMT
>I have a split database where the users keep the backend
>in a shared folder on the network and then they copy the
>frontend to their local computer.  

FWIW I specifically created the Auto FE Updater utility so that I
could make changes to the FE MDE as often as I wanted and be quite
confident that the next time someone went to run the app that it would
pull in the latest version.  For more info on the errors or the Auto
FE Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.
.

>It has code in it to
>find the backend upon first opening the database.  This
[quoted text clipped - 8 lines]
>The .ldb file contains one or two user ids when it
>corrupts and the users vary.

That rapidly and the users vary?  First thing to do is to check the
OpLocks setting on the server.

Corrupt Microsoft Access MDB Causes - OpLocks
http://www.granite.ab.ca/access/corruption/causesoplocks.htm

>When making an MDE file for the frontend, Access
>states "You can't create a Microsoft Access MDE database
[quoted text clipped - 4 lines]
>MDE file.  I did not convert the backend.  Then I tried
>with a converted backend and had the same results.

Makes sense.

>All users are at the following versions of Access/Jet:
>    Microsoft Windows 2000
>    Microsoft Access 2002 (10.3409.3501) SP-1
>    msjet40.dll        4.0.6218.0  
>(they also have msjet35.dll  3.51.2026.0)

6218 is SP6 which is a bit old but fairly stable.

>I'm having a very difficult time pinpointing the problem.  
>Any suggestions will GREATLY be appreciated!

Thanks for the detailed description of the problem and the
troubleshooting efforts you've clearly already done.

Please let us know if the Oplocks fix does or doesn't work.

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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.