Re: Multiple users on an Access database

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


--
Joan Wild
Microsoft Access MVP
"AlanK" <AlanK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4FC52773-C0C7-4B20-876C-9772E13203A0@xxxxxxxxxxxxxxxx
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.

"Keith Wilby" wrote:

"AlanK" <AlanK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:34D8B280-A852-4991-B3BA-E71B195ED5F5@xxxxxxxxxxxxxxxx

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?


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


.

Relevant Pages

  • Re: Exclusive access to the database
    ... Do you mean that two managers can't modify the same report at the same time ... "Rick B" wrote: ... You should split your database into Front-End and BAck-End. ...
    (microsoft.public.access.security)
  • Re: Which Version of Access
    ... Redesign of the database is not an option. ... > Andy wrote: ... >> a dynamically generated report). ... > design changes" can also be done in the open event of the report without ...
    (microsoft.public.access.modulesdaovba)
  • Re: Multiple users on an Access database
    ... users your could modify it and save it, it is not possible in later version ... I've split the database however I'm still encountering problems. ... design of a Report or Form the following message appears " Microsoft ... Access can't save design changes or save to a new database object because ...
    (microsoft.public.access.security)
  • Re: convert report created in design mode to editable vba
    ... You can modify a report programmatically, by opening it in design view, ... You can then use CreateReportControl or whatever to modify it. ... However, that is not something you want to do in a production database, as ... rather than allenbrowne at mvps dot org. ...
    (microsoft.public.access.reports)
  • Re: Dynamic Report Fields
    ... you have a table whose design changes, or may change, each ... You want a self-adjusting report to determine what is in the table ... and re-create or modify itself to accommodate, ... Microsoft Access MVP ...
    (microsoft.public.access.reports)