compacting access DB on terminal server

[Guest Jim Burke in Novi]

My database is split 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. I have never had a problem with compacting on my laptop, this is

only on the terminal server. 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.

[Guest Peter Dickason, MCSE, CCA, CNE]

Re: compacting access DB on terminal server

 

Jim, it sounds as if you have a mismatch with the version of Access the

database is in and the version you are trying to compact it with. I've seen

that do the problem you describe. Hope this helps.

 

Pete

[Guest Jim Burke in Novi]

Re: compacting access DB on terminal server

 

That was it! Thanks much. By sending it to my laptop, doing the compact,

sending it back, and re-defining security it works perfectly. A bit of a

hassle, but it works.

 

"Peter Dickason, MCSE, CCA, CNE" wrote:

> Jim, it sounds as if you have a mismatch with the version of Access the

> database is in and the version you are trying to compact it with. I've seen

> that do the problem you describe. Hope this helps.

>

> Pete

>

>

>