Access on the Server

[jalgier]

Greetings,

I have been having problems (about once a week) with my Access application. The database is running on an NT 4.0 server with about 4 people accessing it via a shortcut on their desktop. The app is about 15MG, and like I said, I have about a problem a week where I have to kick everyone out to do a repair and compact. Now the problem is the database seems to get corrupted (the .lbd) file won't close and can't be deleted until you shut down server. This last time even that didn't work and I had to replace the app with a back-up copy. Here is the question...

Would installing Access on the server help at all? Does it make a difference? Is there anything I can do with the server to reduce the downtime? Any suggestions will be considered.
Thanks in advance.

 

[khokanson]

Because Access uses the JET database engine and all of the data manipulation/calculations are done by the clients, any modification of the server on which the files reside should have no effect.

One of the biggest complaints about Access and JET is it's record locking capabilities. The ldb file is where Access keeps track of locked records. Access is built with ease of use in mind. Unfortunately in order to deliver most of the functionality that Access has (easy filtering, easy record navigation) compromises had to be made and most of those compromises involved multiple users. As a result the more users you have updating and browsing information at the same time, the more record locking related problems you will run into.

 

[BNPMike]

My application is on an NT server and has not had problems.

An inherent weakness of Jet is that as threads are controlled by a each client pc there is no way 'Jet' can recover if a transaction fails leaving the database physically inconsistent.

Installing Access on the server makes no difference as it still runs on the client.

You can install MSDE on the server - if they'll let you - in which case your problem goes away. MSDE is an active process and looks after its own integrity. mike.stephens@bnpparibas.com