Preventing .ldb Locking With Linked Tables

[billschu]

Hi,

I have an Access database on a server an Access interface linked to the tables in this central database. The problem I'm having is that when one or more users open a form in the interface (that has as it's recordsource one of the linked tables), the .ldb file appears and I get locked out my database. It seems like I can make changes to the queries but not the modules or any of the code.

Is there anyway to still utilize the linked tables but not get locked out? I tried to set the database to "Exclusive" for the default open mode (Advanced Tools), but that didn't seem to do anything.

Thanks,
Bill

 

[seaport]

Bill,

As I understand, a backend database is not supposed to have any code, and even queries. All data processing capability should be built in the front-end db (the interface, in your term). So my suggestion is to move your code in from the database (that tends to be locked) to an front-end database.

Hope this helps.

Seaport

 

[billschu]

Thanks Seaport.. in general I would agree, and yes most of the code is in the interface. I do have a small amount of code in the database to do refresh tasks though (it downloads data from our Oracle ERP database every morning).

I'm not expecting to have to edit this code that much either so maybe its not too much of a problem, but I would still like to know if there is a way to prevent the locking.

Bill

 

[seaport]

I would say that there is no way to prevent the locking.

Seaport

 

[easyit]

You cannot prevent the creation of the .ldb file - besides that has nothing to do with your problem. However, it seems that the locking out has more to do with how the users are accessing the DB. If you dont'have security in place, than every user is an administrator and they automatically have the right to opening objects exclusively. So I would suggest that you checkout how t secure your DB properly.

 

[MoLaker]

Another suggestion...

Instead of putting code in your back-end, create another front-end to perform the updating process. Place this new front-end in an area not accessible to others and link it to your back-end. Other users would never(well, maybe never if you do it right) have this database open. You could then modify to your heart's content.

 

[willir]

MoLaker and SeaPort are correct. The back end should only have data. You can have more than one front end that links to the backend. Most often, you will have the end-user front end, but you can have an administrative task front end (for backups, etc).

Richard