Multi User Issues

[Dave]

Access 2003
Database is split but no security and no "MDE"
front end and back end are in the same directory on the server.

I want to just put a shortcut of the front end on each workstation (5
machines) but it does not seem to allow it to be open in multiple machines
that way.
So what I have done is make a "Copy" of the front end on the root of each
desktop C drive and then put a shortcut of that copy on the desktop.
Why can't I get the first method to work properly?
Isn't this possible or am I just missing something?

Any help here will be appreciated.

Thanks in advance
dave

 

[Arvin Meyer [MVP]]

Access 2003
Database is split but no security and no "MDE"
front end and back end are in the same directory on the server.

I want to just put a shortcut of the front end on each workstation (5
machines) but it does not seem to allow it to be open in multiple machines
that way.
So what I have done is make a "Copy" of the front end on the root of each
desktop C drive and then put a shortcut of that copy on the desktop.
Why can't I get the first method to work properly?
Isn't this possible or am I just missing something?

Stop! Users should NEVER share a front-end, nor is it a good idea to run it
from a server unless it is a terminal server. Run a separate copy of your
front-end application from each workstation to avoid conflicts and
corruptions.

 

[Dave]

SO you are saying that the way I am currently doing it IS THE correct way?

 

[Larry Linson]

SO you are saying that the way I am currently doing it IS THE correct way?

Why do you ask that? The front-end should reside on each user's machine...
that's where it is going to execute, but the way you have it set up, every
object it uses will have to be retrieved across the network. If you have
multiple users concurrently logged in to the same front-end, you
signifiantly increase the probability of corruption..

Larry

 

[Rick Brandt]

Why do you ask that? The front-end should reside on each user's
machine... that's where it is going to execute, but the way you have
it set up, every object it uses will have to be retrieved across the
network. If you have multiple users concurrently logged in to the
same front-end, you signifiantly increase the probability of
corruption..
Larry

He did indicate in his previous post that he is running a local copy on each
person's PC. He just thought that was a hack to solve his problem rather
than the correct way to do it.

 

[BruceM]

No. Arvin said you should place a copy of the FE, not a link to the FE, on
each computer.
Remember that with Access you are creating an application. Access is a
development environment, not an application. There is nothing analogous to
a blank document, spreadsheet, presentation, etc. Until you create a table
there is no place to store information. With Excel you could have a
spreadsheet (data file) on the server, but each user needs a copy of Excel
on their computer. Although Access can work up to a point with several
users in the same application (mdb file), the best way (the only effective
way with several concurrent users or a large user base) is for each user to
have a copy of the application (the front end) on their computer.
BTW, I realize there are server-based applications and other situations that
may run contrary to my statement about each user needing a copy of Excel to
view a spreadsheet in a network location, but my point remains. I'm not
trying to split technological hairs.

 

[Rick Brandt]

No. Arvin said you should place a copy of the FE, not a link to the
FE, on each computer.

From the OP...

He is doing it correctly now. He just didn't know that you are supposed to
do it that way.

 

[BruceM]

I saw "front end and back end are in the same directory on the server" and
didn't sort out the rest of the post. When I saw "link" I read it too
quickly, and took it to mean a link to the FE on the server.

 

[Dave]

Rick has correctly assessed what I am doing now and what my dilemma is.
It seems that everyone agrees that a "COPY" on each workstation and not a
"SHORTCUT" on each workstation is the CORRECT way to do this.
So I am fine and I appreciate all the input.

dave

 

[Tony Toews [MVP]]

Rick has correctly assessed what I am doing now and what my dilemma is.
It seems that everyone agrees that a "COPY" on each workstation and not a
"SHORTCUT" on each workstation is the CORRECT way to do this.
So I am fine and I appreciate all the input.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating a directory named after the user on a server. Given
a choice put the FE on the Citrix server to reduce network traffic and
to avoid having to load objects over the network which can be somewhat
sluggish.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/