Different versions of Access causing Crash?

[Ceejay64]

Hello All,
I am in a pickle here, and could use some of your sound advice. I have a multi-user Access 97 db that was just introduced to the users recently. It is housed on one of the network servers here, and is set to open as "shared" for the default with no locks. It is a duplicate of others I am using in different departments which all work fine, but this one is constantly crashing. I often get calls that it is displaying a msgbox telling the person trying to open it that it "isn't a database" or is "missing." Additionally, the .ldb file is staying open even if the db is closed, thus locking things up. I do have it split, so my backend is OK, but this is getting nutty.
I'm wondering if some of the machines are trying to open it in Access 2000 (and converting it in the process) while the others have Access 97, which is what it was built in.
Would this cause these problems?
Any advice would be greatly appreciated, and thanks for your time!
~Ceejay64

 

[ghudson]

Your db maintenance just went up for you will have to keep two working versions!

You will have to split the db. The back end must stay in Access 97 and you will need two front ends [one in Access 97 and 2000]. You will need to distribute the correct front end to each user. Or...you will have to provide shortcuts for each user depending on which version of Access they are using to open the correct front end.

Your Access 2000 users are opening and converting the Access 97 db into Access 2000. Access 2000 does not know what the file is since it can not open the Access 2000 db.

Maybe somebody else has a better way to do this?

HTH

 

[Ceejay64]

Ugh - that's what I was afraid of.
Well, since it's already split, I'm that much ahead of the game there, but I have no idea how many terminals the front end is actually running on, or which version they're running.
Guess it's time for a field trip out on the factory floor.
Thanks for your help.

 

[Ceejay64]

OK - I came in again today to a crashed database. The users swear that no terminal has A2K on it, so they don't think that's the problem.
It just keeps going down, and the .ldb file NEVER closes. Our computer department isn't "authorized" to maintain Access, so I can't ask them for assistance. I can on occasion get them to boot all the open ones and delete the .mdb and .ldb files for my database, which I then back up, but it keeps happening again anyway.
Please offer any suggestions you can think of as to why this #^$%*** thing keeps going down...I'm ready to hit DELETE forever!

 

[ghudson]

A lot of things can cripple Access. The most common is when the users do not allow Access to properly shut down. Ctrl Alt Deleting the db to close it can corrupt the db. You should ensure that all users are closing the db from your exit button. I also suggest that you give each PC a custom shortcut to open the db.

Here is a sample Target: line that you can use...

"C:\Program Files\Microsoft Office\Office\msaccess.exe" "X:\YourDB.mdb"

That will ensure they are using the right version of Access if everybody has Access installed in the same location.

I also suggest that you import all of the db objects into a brand new Access database to remove any doubt that there is any piece of curruption in your db.

As always...repair, compact and back up your troubled db's often!

HTH

 

[ghudson]

Also, does every body have access to add, delete and modify files in the network folder that the db is located in? They must be able to create, edit and delete the *.ldb file.

The .ldb [record locking] file will disapear when the last user has successfully closed the db. You can open the .ldb file with Notepad to see who is [was] in the db. That should narrow down who might be causing problems with the db.

If you can not manually delete the *.ldb file then somebody is still in the db or somebody's PC did not successfully close the db and their PC still has a connection to the db. You will have to reboot all PC's listed in the .ldb file to close the connection. Then you should be able to delete the .ldb file.

HTH

 

[Ceejay64]

Yes, everyone has access (no pun intended) because it is on a common drive with no restrictions. It most likely is stemming from improper shutdowns, although I have timers that will force forms and eventually the program itself to close automatically. I had people leaving it open 24/7, sometimes multiple copies on the same terminal with some of my other databases. The timers worked wonders, and allowed me the opportunity to get in and do repairs and compacting on a regular basis.
I will do all of your suggestions, and report back. Wish me luck...and THANKS!

 

[Ceejay64]

Gotta tell you, I really dig that opening the .ldb file with notepad...I didn't realize you could do that! That's too cool.
Thanks again!

ps - I must be honing in on it (knock wood)...it only crashed once today