Security & Compact & Repair

[Leif]

I have an admins group that is allowed to have exclusive access to the
database. I set this up so that they may do a compact & repair. However,
sometimes they get exclusive access by just entering the database.

If I remove the exclusive access right they can no longer do a compact &
repair, right? I don't know what triggers an exclusive access, but is it
possible, programmatically, to release exclusive access without exiting the
database?

Thanks,
Leif

 

[Keith Wilby]

I have an admins group that is allowed to have exclusive access to the
database. I set this up so that they may do a compact & repair. However,
sometimes they get exclusive access by just entering the database.

If I remove the exclusive access right they can no longer do a compact &
repair, right? I don't know what triggers an exclusive access, but is it
possible, programmatically, to release exclusive access without exiting
the
database?

Thanks,
Leif

Don't C&R in a production environment. Split your db, C&R your developement
copy FE before you deploy it. C&R your BE file when all users are offline.
More info on splitting here:

http://www.granite.ab.ca/access/splitapp/index.htm

HTH - Keith.
www.keithwilby.com

 

[Leif]

Keith,

Thanks for your reply.

I've been told to split the database many, many times. It causes me more
problems then it is worth.

Please allow me to narrow my question.

For an individual that logs into a secure database, and that has exclusive
access rights, what action(s) would cause the database to go into exclusive
access mode? I *assume* that simply entering the database, with no other
users present, will not cause the database to go to exclusive access, even if
the user has that right.

Thanks,
Leif

 

[Joan Wild]

Please allow me to narrow my question.

For an individual that logs into a secure database, and that has exclusive
access rights, what action(s) would cause the database to go into exclusive
access mode? I *assume* that simply entering the database, with no other
users present, will not cause the database to go to exclusive access, even if
the user has that right.

If the user doesn't have create Windows permission on the folder, they will open it exclusively.
They use File, Open and choose Open Exclusively
There is a /excl switch in the target of a shortcut they use to open it

(you should split)

 

[Leif]

humm... None of those is the case. I guess I try to reproduce the problem.

After running 4 years without splitting, supporting up to 20 simutaneous
users (because 20 is all we have in the department) very successfully, and
having used a split database before, I would not dream of subjecting myself
to the pain of a split database.

 

[Douglas J. Steele]

All I can say is that you've been extremely lucky!

What "pain" are you talking about? I split all my applications, even single
user ones. I can't imagine developing non-split applications, due to the
pain of making changes to the application...

 

[Leif]

I guess I am very lucky. I have about 6 databases in use, all working well
(corruptions occurs perhaps once every couple of years). Oldest is about 5
years.

I did have a problem until I got Tech. Service to remove optmistic locking
from the server.

The pain is the following:

1. Linked tables. I make a local copy of the production database if I want
to check on some issue with a form or report. With linked tables I meed
reset my links. With one database I don't. I've had problems in this area.
For some reason sometimes, in certain cases, I cannot relink all of them at
once. Only one at a time seems to work.

2. Forgetting to reset links such that the BE is not the correct database.

3. Slow as a dog. I did try establishing a permant link, all the usual
suggestions, still much slower then one database, in my experience.

4. I keep a history of the database on each update, including the data.
With a split database this will be more work trying to keep releases straight.

I know the heavy hitters, such as yourself and Joan recommend it, but its
caused me nothing but grief.

Regards,
Leif

 

[Tony Toews [MVP]]

The pain is the following:

1. Linked tables. I make a local copy of the production database if I want
to check on some issue with a form or report. With linked tables I meed
reset my links. With one database I don't. I've had problems in this area.
For some reason sometimes, in certain cases, I cannot relink all of them at
once. Only one at a time seems to work.

I and my clients relink tables all the time without any problems.
Whenever I ship them a new version the code automatically does the
relinking.

2. Forgetting to reset links such that the BE is not the correct database.

That's where I use a variety of techniques. If I'm working in an MDB
and linking to tables on a network drive I change the background
colour to red as a warning. As the users only ever use an MDE I turn
this off for them.

3. Slow as a dog. I did try establishing a permant link, all the usual
suggestions, still much slower then one database, in my experience.

Somewhat slower but there are a number of things you can do.
Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

4. I keep a history of the database on each update, including the data.
With a split database this will be more work trying to keep releases straight.

Copy and paste in Windows Explorer twice.

I know the heavy hitters, such as yourself and Joan recommend it, but its
caused me nothing but grief.

And me. <smile>

Your description of how well things have worked in the past is quite
remarkable. Are you still running in A97?

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/

 

[Leif]

Yes, Tony, you are absolutely also a heavy hitter.

We use Access 2003. As I mentioned, when optimistic locking was taken off
the server things went from night to day. We went from having frequent
corruptions problems to almost never.

We have only department level users, so I can request evenings exclusive
access for updates. If I do a wider scope database I may be forced for split
them. Thanks for your suggestions.

Regards,
Leif