Access 2000 - You do not have exclusive access to the database at this time

[michael.meyer]

Hi All

I am hoping someone may be able to help.

On a Citrix Server running Access 2000 (OS = W2K3) we get the following
error whenever we open ANY database more than once. You do not have
exclusive access to the database at this time. If you proceed to make
changes, you may not be able to save them later.

I have been researching this error and have only found references to if
the system.mdw and the database file reside in the same location. which
for this exercise they are not in the same directory.

I have also found information about spliting the database, which some
databases are split and other very simple that they are not.

and the other I have found references this problem occuring when
database design changes are being which none are occuring.

I initally thought the system.mdw file was corrupt so I copied it from
another server which is working OK and then re-joined it, but to no
success.

So far this happens evey time a database is opened more than once at
the same time and only in Access 2000. I am going bannanas and so far
my searches in the groups do not suggest a resolution to this one.

Does anyone have sugestions?

Thanks
Mike

 

[Nick Coe \(UK\)]

Double check that you're opening the database in shared mode
under Tools|Options IIRC.

Could be a locking file (.ldb) left after a crash,
corruption or improper closedown. Close Access, make
CERTAIN no one else is trying to open that mdb and then look
for the .ldb file in the same directory as the .mdb. If
it's NOT there you're OK and if it is there delete it, copy
your mdb for backup purposes and run compact/repair.

--
Nick Coe (UK)
Available - Will work for money
http://www.alphacos.co.uk/ AccHelp + pAnimal
http://www.pjandcoe.co.uk/ Online Store

In
(e-mail address removed) typed:

 

[Mike]

Double check that you're opening the database in shared mode
under Tools|Options IIRC.

Could be a locking file (.ldb) left after a crash,
corruption or improper closedown. Close Access, make
CERTAIN no one else is trying to open that mdb and then look
for the .ldb file in the same directory as the .mdb. If
it's NOT there you're OK and if it is there delete it, copy
your mdb for backup purposes and run compact/repair.

Hi Nick

I have checked each DB and they are all set to Shared.

I have checked each DBs lock File and they are being created and
removed correctly.

I have run a Copact and Repair on each DB to no result also.

Any other ideas?

Thanks
Mike

 

[aaron.kempf]

mdb is a disease.

you should be using Access Data Projects with SQL 2000.

 

[Arvin Meyer [MVP]]

Citrix and Terminal Server have per user licenses and usually only allow a
user to logon once. The default unsecured Access user is "admin" and if you
don't have a split database, this can bite you.

The solution is to have a separate folder for each user with a front-end in
that folder. The data (back-end) can reside in a central directory either on
the Citrix server, or on any other server that Citrix can see on the
network. Our local Access apps run from 20 remote locations to a Terminal
Server in Orlando connected to a server database which is also used by 30
other local Access users. We use a separate front end for every user and
have absolutely no problems.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Joseph Meehan]

mdb is a disease.

you should be using Access Data Projects with SQL 2000.

Please ignore the troll.

 

[Mike]

Hi

I understand what you are saying, however the initial thought of this
is daunting.

The weird thing is that I have an old Citrix Server, which they all
work fine on, the only difference is that the old server runs W2K
instead of W2K3. When I need to I can load balance the app between the
two citrix servers and those on the old server work but those on the
new one do not.

Do you think that W2K3 could be causing it, or have an variable that
may be effecting this?

Mike

 

[Arvin Meyer [MVP]]

I doubt it. I have run Access 97 through 2002 on both Win 2K and Win 2K3
Terminal Servers. I must admit, I like the 2003 servers better as they are
easier to manage. I suspect that your problems on the 2003 server are
permissions oriented. Microsoft makes sure 2003 servers have many of the
previously defaulted on settings, turned off. Unfortunately, I am not an
expert in servers any more, having given most of that up years ago when I
started working as a developer full time.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Mike]

Ideally I would like to keep the Application as a single copy running
from the server since this is what we have been using, and the task to
change Citrix to use many copies for each user is a large task to
implement.

Do you have any ideas which permissions I should be looking at what
what for?

Does anyone else out there have any ideas?

Cheers, thanks for all you help
Mike

 

[Arvin Meyer [MVP]]

Ideally I would like to keep the Application as a single copy running
from the server since this is what we have been using, and the task to
change Citrix to use many copies for each user is a large task to
implement.

Unfortunately, this may lead to corruption, but of course if you have good
backups and an understanding boss, that should be of little worry.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Rick Brandt]

Ideally I would like to keep the Application as a single copy running
from the server since this is what we have been using, and the task to
change Citrix to use many copies for each user is a large task to
implement. [snip]

Actually setting up a Citrix Access app so that each user has their own copy of
the front end is a task that would take about 5 minutes. Setting up a system to
automatically propogate updates of that front end as they are issued would take
a few minutes more.

Both require some knowledge and you might have to acquire some free tools
(depending on requirements), but there really is no excuse not to do this the
proper way rather than the improper way. You've spent more time posting to
these groups than it would have taken to accomplish.

 

[aaron.kempf]

MDB doesn't work with more than one user; use Access Data Projects.

 

[aaron.kempf]

more importantly

if you do use MDB; programmatically set options to 'default open mode =
shared'

instead of just setting this once; do it programmatically so it repairs
itself

-aaron

 

[Tony Toews]

Ideally I would like to keep the Application as a single copy running
from the server since this is what we have been using, and the task to
change Citrix to use many copies for each user is a large task to
implement.

As the others have stated you do not want to share a FE as it will corrupt sooner or
later. And/or have other interesting problems.

As far as setting up Citrix goes all you need is a one line .cmd file which calls the
msaccess.exe and passes the name of the FE MDB/MDE. Alternatively if you want to use
my Auto FE Updater to keep the FE updated then create a one line .cmd file which
calls the startmdb.exe and passes the path and name of the INI configuration file.

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

 

[aaron.kempf]

if you share a FE it will get corrupted?

surely this is just true for MDB; not for ADP right?

i just wish that ms would fix these bugs i mean jesus you guys accept
this crap?

'it will become corrupted' means microsoft gives us all a full refund
for every copy of access ever