"This often is a result of sharing a frontend on the server. You should
instead split the database and give each user their own copy of the frontend
on their workstation."
Joan, could you please explain in a little more detail how and where I would
give my users their own copy of the Frontend? What objects would be in the
FE for the user?
Vera
> Joan, could you please explain in a
> little more detail how and where I
> would give my users their own copy
> of the Frontend? What objects would
> be in the FE for the user?
The Front End contains Queries, Forms, Reports, Macros, Modules, and
sometimes local lookup tables (data that changes infrequently, for use with
List and Combo Boxes, mostly). They would be linked to a Back End on a
shared folder somewhere on your network (performance better if on a domain
on a server).
There's an introductory presentation on Access in a Multiuser Environment
that I did for my user group that you can download from
http://appdevissues.tripod.com. It will identify topics that I thought
worthwhile to discuss, and a bit more.
There's an article at http://accdevel.tripod.com that deals with a simple
approach to assuring users can obtain recent front end upgrades and that
they have to have "mandatory updates".
The best collection of detailed information and links on the subject of
Access in the multiuser environment is at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm. At the same site, you'll be able to
download Tony's Auto FE Updater -- his approach to making sure the users
have the proper front end.
Larry Linson
Microsoft Access MVP
Vera in Las Vegas - 14 Dec 2004 20:53 GMT
Thanks, Larry. I will check out the sites.
> > Joan, could you please explain in a
> > little more detail how and where I
[quoted text clipped - 25 lines]
> Larry Linson
> Microsoft Access MVP