Ensuring secured split database is opened in shared mode

  • Thread starter Thread starter Silvester
  • Start date Start date
S

Silvester

I have a secured split A2000 database that I would like to ensure is opened
in shared mode. Even though tools | options | advanced is set to "shared"
both in the fe and be, the database opens in exclusive mode.

How can I ensure that my database is opened in shared mode only ?

TIA
 
Silvester,

Is the database located on your server? If it is, the users who open it
must have full permissions on the network to the folder in which it is
located - Read, Write, Create, Delete, Execute, etc. This is because, each
time a user opens the database the LDB file which keeps track of who is
using the database must be modified. And, when the last user closes the
database, the LDB file must be deleted.

hth,
 
Silvester said:
I have a secured split A2000 database that I would like to ensure is opened
in shared mode. Even though tools | options | advanced is set to "shared"
both in the fe and be, the database opens in exclusive mode.

How can I ensure that my database is opened in shared mode only ?
Click to expand...

On whose PC? Those options you are describing are not options of the file,
they are options of Access on that particular PC. Setting them on one PC
has no affect on others.

Also, you will get exclusive opening by the first user if they do not have
adequate permissions to the folder where the MDB file resides. ALL users
must have Create, Use, Modify, Delete permissions on that folder otherwise
the creation, modification, and deletion of the Access locking file (LDB)
file cannot be successful.

If the first user cannot create an LDB file in that folder when they open
the MDB then the file will be opened exclusively since an LDB file is
required for multiple users to be in the file at the same time.
 
Just to clarify... the database is split but it is an app in which the fe
and be will be distributed and both will reside on the users machine.

Right now the db is opening in exclusive mode and it is not possible to
compact the be from the fe unless it is in shared mode.

This is the reason I want to get the db into shared mode.

Thanks for any help
 
Silvester said:
Just to clarify... the database is split but it is an app in which the fe
and be will be distributed and both will reside on the users machine.

Right now the db is opening in exclusive mode and it is not possible to
compact the be from the fe unless it is in shared mode.

This is the reason I want to get the db into shared mode.
Click to expand...

I'm not positive, but I'm pretty sure that you can't compact the BE from
the FE if the BE is opened *at all* (exclusive or shared). If you close
all FE objects that link to the BE then the BE will be closed completely at
which point you can use a routine in the FE to compact it.

The compact process requires exclusive access to the file so unless the
file is closed to begin with the compact procedure cannot proceed.
 
Back
Top