MS Access multiuser database

[Guest Brent]

Is it necessary for each TS user to have their own copy of the front end of a

split, multiuser database?

 

Currently each TS user has a short cut the same front end .mde and each

opens their own 'instance' of that file when they log into Access.

 

For the most part it works well for users and I like the convenience of just

having to replace one file when updates are rolled out.

 

The reason I ask is that occasionally an on-open update procedure fails with

error 3009 - a certain table can't be locked because it is already open or in

use.

 

Users should not be opening this table directly but lots of forms and

queries use it.

 

Thanks for your thoughts.

 

Brent

[Guest Paul Shapiro]

Re: MS Access multiuser database

 

TS is the same as multiple LAN workstations using Access. Stability improves

if each user has their own copy of the front end.

 

I usually setup a simple .cmd file on the server that will copy the current

FE to a particular folder under My Documents and then run Access to open

that file. I create a shortcut to that .cmd file in the same server folder.

Copy that shortcut to each user's desktop, and that's how they run the

application. Each time they run the app they get the latest version

automatically. No need to compact the FE because the master copy is never

used and therefore doesn't bloat.

 

"Brent" <Brent@discussions.microsoft.com> wrote in message

news:E2868CD0-8E33-46AA-8B83-336ACC11CFEC@microsoft.com...

> Is it necessary for each TS user to have their own copy of the front end

> of a

> split, multiuser database?

>

> Currently each TS user has a short cut the same front end .mde and each

> opens their own 'instance' of that file when they log into Access.

>

> For the most part it works well for users and I like the convenience of

> just

> having to replace one file when updates are rolled out.

>

> The reason I ask is that occasionally an on-open update procedure fails

> with

> error 3009 - a certain table can't be locked because it is already open or

> in

> use.

>

> Users should not be opening this table directly but lots of forms and

> queries use it.