>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