Multi User Issue's

[Dave]

Access 2003
Split database
No Security
Front end (Fe) and Back end (Be) are in the same directory on the server
"SHORT CUT" to fe on each (2) workstation

Opening the DB on each of the 2 workstations does work
HOWEVER
if it I already open on one workstation it will NOT OPEN on the other
workstation.

I have tried:
STARTING on BOTH workstations - Same results
Tried the same set up with an XP server and a win2000 server - Same results
Checked to be sure opening mode is "shared"


This is my first attempt at a multi user configuration for Access. I called
a buddy of mine who has much more experience in Access and in multi user
environments and he told me that he was currently having the same issue with
one of his clients.


any ideas what I am doing wrong or what else I should try in de-bugging the
issue?

Thanks
Dave

 

[Bob Quintal]

Access 2003
Split database
No Security
Front end (Fe) and Back end (Be) are in the same directory on the
server "SHORT CUT" to fe on each (2) workstation

Opening the DB on each of the 2 workstations does work
HOWEVER
if it I already open on one workstation it will NOT OPEN on the
other workstation.

I have tried:
STARTING on BOTH workstations - Same results
Tried the same set up with an XP server and a win2000 server -
Same results Checked to be sure opening mode is "shared"


This is my first attempt at a multi user configuration for Access.
I called a buddy of mine who has much more experience in Access
and in multi user environments and he told me that he was
currently having the same issue with one of his clients.


any ideas what I am doing wrong or what else I should try in
de-bugging the issue?

Thanks
Dave

The way Access allows sharing is by creating a temporary file with
the .ldb extension. Make sure your users have
read/write/create/delete access to the folder containing the .mdb

A much better solution, recommended by Microsoft, is to put a copy
of the front end .mdb on the user's machine, not the server. On the
server, you can remove the delete permissions, so that the .ldb can
be created. The .ldb can exist for a few days, without being
deleted, so you need a server script to delete it approximately
weekly, when nobody is in the databse, because it bloats..

 

[Paul Shapiro]

The strongly recommended best practice is for each user to have their own
local copy of the FE. However it should still be able to work in the way
you're using it. Check if the first user is opening the FE for exclusive
access. Have them open it from the file menu, open and make sure Exclusive
is NOT selected.

A simple implementation for auto-updating the clients from the master FE on
the server is to put a shortcut on each user's desktop that copies the FE
from the server to the local computer, and then starts that local copy.
Paul Shapiro

 

[Dave]

Paul,

I did get a chance to try putting a local copy of the FE on each work
station and that DID seem to work. I do not understand why the shortcut did
not work but does not really matter if that was not the best practice
anyway.

Thanks for the input.

I did not completely follow your suggestion for "auto-updating"
Can you elaborate please.

Thanks,

Dave

 

[Paul Shapiro]

When the FE is on the local workstation, the issue is how you distribute
updated versions of the FE. I've found it simple to keep the master FE copy
on a server, and have users run the program by running a simple batch file.
The file just has 2 commands- copy the FE from the server to the local
workstation, and then start that local copy.

Something like this goes in RunDB.cmd. Each user has a shortcut pointing to
RunDB.cmd on their desktop, and they double-click that shortcut to run the
db.

copy /y "\\ServerName\ShareName\FE.mdb" "%HOMEDRIVE%%HOMEPATH%\My
Documents\DBFolder\FE.mdb"

Start "DBProgramName" "%HOMEDRIVE%%HOMEPATH%\My Documents\DBFolder\FE.mdb"

 

[Dave]

got it.
that is a great idea.

Thanks much,

dave

 

[MYKLIV]

Paul,
Is this a new situation with Access ? I am having the same issue, suddenly.

I have had a fe/be split db (access 2003) that has been functioning fine,
with muiltiple users, able to get in at any time, up until about a week ago.

Yes, my fe is on the server, for just the reason you described. It makes it
a LOT easier to distribute updates. But this db worked fine, for years, up
until recently. I attributed the change to some cind of (security) patch
pushed by MS, as to WHY it stopped working. Which is why I came here and
found this thread...

Any knowledge, or understanding as to why this would just happen suddenly ?

Additionaly, I'm not sure that the IT dept here would allow a batch file to
exist on a users desktop. Security at my work place is insanely tight.

Would really like to hear back from you !

MYKL

 

[Tony Toews [MVP]]

Is this a new situation with Access ? I am having the same issue, suddenly.

I have had a fe/be split db (access 2003) that has been functioning fine,
with muiltiple users, able to get in at any time, up until about a week ago.

Yes, my fe is on the server, for just the reason you described. It makes it
a LOT easier to distribute updates.

One FE on the server? Then you need to kick the users out to install
a new version of the FE.

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.

But this db worked fine, for years, up
until recently. I attributed the change to some cind of (security) patch
pushed by MS, as to WHY it stopped working. Which is why I came here and
found this thread...

Any knowledge, or understanding as to why this would just happen suddenly ?

No idea although your hypothesis is as good as any.

Additionaly, I'm not sure that the IT dept here would allow a batch file to
exist on a users desktop. Security at my work place is insanely tight.

FWIW Boeing has approved my Auto FE Updater for use.

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/