Results 1 to 4 of 4

Thread: Read Only error

  1. #1
    Join Date
    May 2009
    Posts
    30

    Unanswered: Read Only error

    Hi,

    Getting slightly stressed at Access these days. Another day, another error.

    Anyway, most bizarre, my database was working absolutely fine, no issues at all, nice and smooth. Literally 5 mins later I attempt to go back in, and out of the blue it says its Read Only. I now cannot make any amendments to it whatsoever. Nor can other users. Nothing was changed in it other than the usual use, where certain actions are restricted anyway.
    All the backups and previous versions also all give a read only message all of a sudden.

    I mean really, what has happened?

    Thanks
    (a stressed and frustrated office worker)
    Last edited by chrisatwork; 07-07-09 at 09:28.

  2. #2
    Join Date
    Mar 2009
    Location
    Dorset
    Posts
    119
    Some things to try:

    1. Check which version of Access the database is written in and which version you are trying to open it it.

    2. Check folder permissions.

    3. Check the database file permissions.

    4. If you are on a network try opening the file locally.

    5. Check the .ldb file is not hanging around after Access is closed. Come right out of access, and check whether the .ldb file is still there. If it is, delete it and try opening the db again. (You may need to change xp's setting in Explorer to show hidden files).
    Regards
    JD

    Software-Matters

  3. #3
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    alos check each person who was in the application at the same time and find out if they opened the db in exclusive mode
    find out if they were making changes to the design either inadvertatnly or deliberately

    both these things can cause a db to suddenly become read only
    I'd rather be riding on the Tiger 800 or the Norton

  4. #4
    Join Date
    May 2009
    Posts
    30
    Thanks guys, real good advice....I think I 'may' have found the prob, someone tried to access it using Access 97. And considering what you have advised, it makes sense this could be the cause.

    Is this something/a prob thats well known?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •