Microsoft Access 2007 database opens as read-only, but shouldn't

matttye

Hi,

The database I need help with is at work, so I can't try anything right now, but I'm hoping people can offer suggestions that I'll then try at work on Monday.

I work in a small office with about ten PCs, that are all networked. My computer is the "server" but it's basically just a regular PC, albeit the best in the office. File sharing is enabled.

So there is a Microsoft Access 2007 database on my computer that I have shared with certain users. My colleague can access the database but it always opens in read-only mode for her and she can't make any changes.
I checked a few things already: -

1. She definitely has read and write access to the folder that the DB resides in and also to the DB itself. She can create, delete, modify etc. any other files in that folder.
2. There is no .ldb/.laccdb file with the same name in the folder (locking file).
3. The database is not currently open by any other user.
4. The database is not password protected.

Please note that it opens in read/write mode on my computer EVERY TIME; it's just when my colleague accesses it from her computer that it opens read only.

Any ideas?

Thanks

johnmc

Does this help?
http://www.utteraccess.com/forum/Sharing-Access-Database-t1264601.html&hl=cannot+open+as+write

matttye

johnmc wrote: »

Does this help?
http://www.utteraccess.com/forum/Sharing-Access-Database-t1264601.html&hl=cannot+open+as+write

Looks like it, I'll try that on Monday.

Thanks!

Jivesinger

What happens if your colleague tries to create a new database (just a dummy one, as a test) for themselves? Just create a blank database and create a table in it with a couple of fields, save a few records, close and reopen and make sure they can still save changes.

First I'd get them to try it on their own local drive (in case there's some option in Access that isn't being selected).

Then see if they can repeat the steps and create a dummy database on the shared folder.

This won't solve anything, but may narrow down where the issue is.

matttye

Rather embarrassingly the problem was "tunnel vision" on my part.

There was a box popping up when I started Access that I didn't bother to read... until today. Trial expired

We need to buy a key if she wants to be able to edit the database.

I have split it into a frontend and backend though, so at least it is now ready.

Thanks!