Multiple users on an Access database

  • Thread starter Thread starter AlanK
  • Start date Start date
A

AlanK

I've had my database setup for some time.
The database is saved to the network.
I am now encountering problems when more than one user enters.
On occasion I get the following error message on initially opening the
database "The database has been placed in a state by user <name> on machine
<name> that prevents it from being opened or locked".
Can this be resolved without splitting the database?
 
On Tue, 4 Mar 2008 01:19:00 -0800, AlanK

Never a good idea to go against best practices.

-Tom.
 
Hi Tom,

I've split the database however I'm still encountering problems.

There are two users.

If one user has the database open (with no tables / queries / reports or
forms open) and the other user enters the database and tries to modify the
design of a Report or Form the following message appears " Microsoft Office
Access can't save design changes or save to a new database object because
another user has the file open. To save your design changes or save to a new
object, you must have exclusive access to the file". The database is in
shared mode. Any ideas?

Thanks,

Alan.
 
AlanK said:
Hi Tom,

I've split the database however I'm still encountering problems.

There are two users.

If one user has the database open (with no tables / queries / reports or
forms open) and the other user enters the database and tries to modify the
design of a Report or Form the following message appears " Microsoft
Office
Access can't save design changes or save to a new database object because
another user has the file open. To save your design changes or save to a
new
object, you must have exclusive access to the file". The database is in
shared mode. Any ideas?
Click to expand...

Hi Alan,

No offence but I think you may fundamentally misunderstand the concept of a
multi-user database. In my experience you can *never* have more than one
concurrent developer on the same front end. You should also never do
development work on a production system, rather you should have a
development copy to work on which you would then deploy to your users (one
copy each) for data manipulation and report generation. That is where the
benefit of splitting comes.

Regards,
Keith.
www.keithwilby.com
 
I've used Access databases in the past with over 10 users and this was quite
easy to achieve. i.e. Once the report was not opened by one of the other
users your could modify it and save it, it is not possible in later version
of access?

Its quite essential in my application that I'm able to modify reports when
other users are in my database, I'd be grateful of additional feed back.

Thanks,

Alan.
 
I think version 97 was the last one that allowed you to modify objects while someone else was using the mdb - not any more.

You do want to split, but more importantly, give each user a copy of the frontend on their local PC. Once you have modified/added a new report, you can distribute the new frontend to the users. Have a look at Tony Toews' site for a tool you can use to automate the distribution of the updated frontend.
http://granite.ab.ca/access/autofe.htm
 
AlanK said:
Its quite essential in my application that I'm able to modify reports when
other users are in my database, I'd be grateful of additional feed back.
Click to expand...

It's bad practice to do development work on a production system, rather you
should have a development copy to work on which you would then deploy to
your users (one copy each) for data manipulation and report generation. I
use a user-executed batch file to ensure that the latest version of the FE
is delivered to the user every time the open the app.

HTH - Keith.
www.keithwilby.com
 
Back
Top