open exclusive problem

ajetrumpet

Banned
Local time
Today, 01:57
Joined
Jun 22, 2007
Messages
5,638
Folks,

I've got one file that I would like to make a copy of in a different format (.mdb to .accdb).

Everytime I try the "Save As" within a different file type, I think Access treats the new file like it's being opened. Because of this, I am getting this error:
Cannot save the database because it has been opened exclusively by 'Admin' on "my machine"
I've checked both previous versions of the file (2000 & 2003), and both of them have a default open mode of "shared". I am trying to save it as a .accdb file from either the 2000 or 2003 version. Both files throw the error.

What could be going on here?
 
That's because acViewNormal prints the report by default...

Wrong response...

That's because conversion requires exclusive access to the DB and you cannot programmatically do it without setting up a separate Workspace (Workspaces(1) in this case) and really, unless you have a boatload of DBs, you're better off manually converting these things.
 
That's because acViewNormal prints the report by default...

Wrong response...
Very cute. :rolleyes:
That's because conversion requires exclusive access to the DB and you cannot programmatically do it without setting up a separate Workspace (Workspaces(1) in this case) and really, unless you have a boatload of DBs, you're better off manually converting these things.
What the he** are you talking about, boy? I'm not trying to do it through code. I AM manually doing it...

And rak,

I will see what that article can do for me. It's not the same message, but VBA corruption would be my first guess (after my other 2 first guesses). The amount of code in this file is very small, but the calling between subs and functions (back and forth) and timer events are plentiful. So, that could be a cause of this. We'll see...
 
Last edited:
If you're trying to do this manually, have you just tried the directly through the menus way of it, as in, Tools -> Database Utilities -> Convert Database?

That may very well be how you're doing it, but I couldn't tell if you were loading it and then trying to save it or what. Also, make sure there's not an existing LDB before you open it. If there is and you're sure no one is in the DB, then delete the LDB before opening it.

I'm sort of stabbing in the dark here, but the LDB not closing properly is fairly common, especially with multiuser DBs.
 
I know nothing about A2007 (in fact some people reckon I know nothing abut anything!)

Earlier versions of Access prompt you to convert the file to a later version when you open it, not save it. Is that not what is happening?

Excuse me if I'm talking rubbish (see first sentence).
 
I'm sort of stabbing in the dark here, but the LDB not closing properly is fairly common, especially with multiuser DBs.
This is not an LDB Moniker, and there is no multi-user environment here.

I have tried the "Convert Database" command in the Ribbon, as well as the "Save As" method. Both give the error. The picture of it is attached.
I know nothing about A2007 (in fact some people reckon I know nothing abut anything!)
I would have to agree.
Earlier versions of Access prompt you to convert the file to a later version when you open it, not save it. Is that not what is happening?
NO. :)
Excuse me if I'm talking rubbish (see first sentence).
Not a problem...
 
Last edited:
not clear from these posts

do you still have a problem

i just thought i would see what happens with an A2007 database - although i hate A2007, as it insists on reconfiguring, and interfering with my A2003 installation.

i created a dbs, converted it to A2003, and then opended the A2003, and converted to a new A2007 dbs - no errors
 
Yes, I still have the problem. I am going to try and export the objects to a new file and see what that does.
 
are you sure some timer event isnt running when the app opens - that might lock the ldb up and stop you being able to manipulate the dbs. Access always opens an ldb when it opens a database.
 
Oh, sorry. I have set a form to open when the app opens, and it does have a timer event of 10 milliseconds. :rolleyes: Is that too fast you think?
 
i dont know, but if the timer is running, it may prevent you being able to convert/copy the database. you may need to remove/disable the timer event to achieve what you want
 
i dont know, but if the timer is running, it may prevent you being able to convert/copy the database. you may need to remove/disable the timer event to achieve what you want
Well...the timer is not running, nor is any procedure when I try to do this stuff.

I close the form before I try to do this. Closing it stops the form timer, and the 1 second time interval pauses that are in use by another function (called by the form's code).
 

Users who are viewing this thread

Back
Top Bottom