Hi,
I have been unable lately to update, or now even copy, microsoft database files from my desktop computer to the briefcase on my laptop computer. I started getting this error around the first of this week:
Briefcase can't open the database "**.mdb"
The Microsoft Jet database engine cannot open the file "**.mdb." It is already opened exclusively by another user, or you need permission to view its data.
I've done everything that I could think of. I've set the directory as shared. I've deleted the directory in my briefcase and copied it again from the desktop. I think it is a setting that has gone screwey in Access. I get this message for database files that I haven't even opened in years. I don't know what is going on.
Anybody know what the fix is?
I asked this on the Carlson board, but didn't get any responses yet.
thanks a bunch,
J T
When I Googled:
> Briefcase can't open the database
I came across:
http://support.microsoft.com/kb/161445
See if some of those suggestions help.
My experience with Windows Briefcase is/was very limited (meaning that I briefly experimented with it about 15 years ago) so aside from the aforementioned knowledge-base article, there will be little additional information I'll be able to provide.
--
Ladd Nelson
When the file was open a locked file was added. See if you copied the locked file that was with the original file. If so, try deleting the locked file and open the database again. Otherwise try re-copying the file making sure it is not open.
Encountered similar problems when one of my employer's computers was replaced and the new one had Windows 7. After some searching found that Windows 7 does not properly handle briefcase files, known glitch no intent to support briefcase in the future. However, Microsoft has a replacement available for download. Try SyncToy 2.1 available at http://www.microsoft.com/en-us/download/details.aspx?id=15155 I have been using it for over a year with good results.
Thanks a bunch, to everyone.
SyncToy looks like will be just what I need. Briefcase is just too buggy, and it don't look like there will be any future fixes.
