Exclusive access

[Guest]

We do not use a SQL server. Access files are stored on a Windows 2003 server.

Users open databases in exclusive mode but in a multiuser environment.

Here's our problem:

If Sally opens the database "enrollment.mdb" she gest enrollment.mdb.

When Suzy comes along and tries to open enrollment.mdb, she actually gets
"enrollment1.mdb" which didn't exist until that exact moment.

It's a huge problem because now there are two copies of the same database on
the server. Suzy's copy doesn't have Sally's changes and Sally's copy
doesn't have Suzy's changes.

If they opened the database in shared mode, would that problem go away?

What is causing these duplication of my databases?

 

[TC]

I don't know how the "1" file would appear like that.

/But/, you should not have multiple users updating a single mdb file at
the same time. That is commonly believed to increase the chances of
data corruption.

You should split your database into a so-called "front-end/back-end"
structure. There is a single copy of the BE, containing all of the data
(and /only/ the data). Each user has a seperate copy of the FE, which
contains all the queries, forms, reports & modules, and has links to
the actual tables in the BE.

Google those terms for more information.

HTH,
TC

 

[Guest]

I will look into your suggestion.

We do have one database designed with the "front-end/back-end" structure you
recommend and the same thing happens. If 2 users get into the database, the
second one creates a databasename1.mdb file. It's scary and frustrating.

 

[TC]

Please post back to this thread if you eventually find out what is
causing the "1" files to appear.

Cheers,
TC