compacting database on terminal server

[Jim Burke in Novi]

My database is spit up between the appl and the tables. The production
application runs on a terminal server. When I compacted the DB with the
tables, our users end up getting an error saying that someone has the
database exclusively. When I am logged on as an adminstrator I can use it
fine, there's no problem. Here's what I do:

1) compact the original production DB into a new one (in case of problems
with the compact)
2) rename the original, then rename the new one to the production name.

When I look at the security options in properties after I do the compact and
the renames, everything looks fine. But somehow it seems that the compact
does something to make the system think that someone still has exclusive use
of the DB. Is there another step i need to take to fix the problem? Any help
is appreciated! I ended having to point the appl to the old, pre-compacted
tables DB.

 

[Alex Dybenko]

Hi,
check that users has full control to folder where mdb is located

--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com

 

[Jim Burke in Novi]

That's the very first thing I do whenever I do anything with files on the
server. They have full control. I thought that maybe a re-boot of the server
might free things up, but that didn't work. It's as though once the compact
is done, the system thinks that Administrator has the DB exclusively for some
reason. I log on with one of the user's IDs, with nobody else on the server,
and I get the error. I log on as Admin and I can use it just fine.

 

[Jim Burke in Novi]

Turns out it's due to the version of Access on my laptop being different than
the version that's on the server. I sent the DB to my laptop, compacted it,
sent it back, re-defined security rules and it works.