Access 2007 backup menu won't back up my database

[kkkwj]

I'm using Access 2007, with what I think is a normal database that I've built up over the past month (maybe 15 tables, <1000 records, 20 queries, 4 or 5 reports and macros). I'm not an experienced Access programmer, so I don't think I'm doing anything fancy with security settings or any other such stuff. (If I have, it's surely by accident, not by intent.)

When I try to back up the db using the simple office button -> manage -> backup method, access generates a date-stamped backup filename and opens a file save dialog for me, but it ALWAYS fails to backup the database. I always get the same error message when I click save, whether I save on my machine, or on a network drive.

"Could not use '<path to the current database dir><backname>.accdb; file already in use."

This same error occurs when I create a new blank database with a single Table1 in it, so I don't think it's my database.

Does anyone have any idea why this might be happening? I scoured the net for help, but nothing. I checked various Access forums, but nothing. So I arrive here after I've done my homework... thanks

 

[kkkwj]

Anyone? This issue seems so simple, but it's a block. The only time I ever saw Access 2007 create a backup file for me was once when it crashed, sent an error report to Microsoft, and asked me if I wanted Access to backup and repair and restore my database. I said yes, and it did what backup was supposed to do---closed the db, offered me a time-stamped backup filename (which I accepted), wrote out the backup, and read in and opened a good copy of the db. Go figure. Do you suppose some installation options can affect this kind of behavior? (I've tried various alternatives such as opening shared or exclusive, but without any good results.)

 

[ijt]

Hi did you get the answer to this problem as I'm having the same issue. Ian

 

[ijt]

Did you find a solution to this problem of ms access not backing up as I'm having the same issue.
Thanks ijt

 

[RuralGuy]

Is everyone working within the Trusted Location?

 

[Huck]

It works for me if I copy the database to my desktop then do the Backup function from there. It should save it back to the desktop with a date.

 

[eric_powell]

I, too, am experiencing this same error. I am working on an HP laptop running Vista and Access 2007. The database is in 2007 format (.accdb).

I have also found that this behavior occurs even when I create a new database and try to back that up, which makes me think corruption is not the problem.

People on other forums seem to have resolved somewhat similar issues using 'Compact & Repair', but this didn't resolve it for me. Additionally, someone is this thread mentioned that they were able to copy the database to the desktop and do the backup from there. This has also not worked for me.

I have also tried to save the database under a different name and/or in a different format, but the save operation is blocked by a similar type of error.

Finally, I was trying to use word mailmerge through access vba and I received an error about "The database has been placed in a state by user
'Admin' on machine 'MY' that prevents it from being opened or locked."

I would be very grateful to anyone that could offer some insight here. I believe all these problems are related, but I have no idea where to start.

Oh yeah, and I did check the access options and the database is definitely in 'shared' mode, (as opposed to 'exclusive').

 

[RuralGuy]

I would create a new empty db and Import all of the old db into it. Then try the same things with the new db.

 

[eric_powell]

I can give that a shot, but I already tried creating a new database and filling a single table with a couple records, and even that I could not back-up.
So it seems to be a setting or bug that isn't specific to my one database.
Oh, and I tried saving, compacting & repairing, etc., and I could not do that either.
Do you have any other suggestions?

 

[boblarson]

I can give that a shot, but I already tried creating a new database and filling a single table with a couple records, and even that I could not back-up.
So it seems to be a setting or bug that isn't specific to my one database.
Oh, and I tried saving, compacting & repairing, etc., and I could not do that either.
Do you have any other suggestions?

Do you have the trusted location set yet?

 

[eric_powell]

Thanks for the suggestion, Bob. Unfortunately, I DEFINITELY have a trusted location set.
I appreciate the suggestion, though. Does this seem like an issues I should try to take to Microsoft? Is there anyway to actually take an issue to them?

 

[eric_powell]

OK, everyone, I seem to have struck upon the workaround/fix, although it doesn't provide a lot of closure about why this occurs.

Basically, I had originally installed access and created the database under a different windows user, one which later got a little messed up (long story). Thankfully, I had not completed the deleted that user, and when I logged in using that account, I was successfully able to back-up a new "dummy" database. Similarly, I was able to copy the DB in question to this user and back it up as well.

That all makes reasonable sense, (although it's not pleasing), but the real head-scratcher is that when I logged back onto the other user, the one in which I originally experienced the problem, I was suddenly able to back up and save the database in question!??!?!

Thus, it seems that Access somehow needed to be "reminded" or "refreshed" by the original user account. This, of course, begs the question: What the heck would I have done had I deleted that user account?

Does this make sense to anyone? Is there something I should know about Access/Vista to avoid such problems in the future -- (other than not to use Vista )?

Thanks again to bob & ruralguy for their replies and suggestions.