Results 1 to 3 of 3

Thread: Back End Only Opening Read Only
Thanks Thanks: 0 Likes Likes: 0

  1. #1
    Board Regular
    Join Date
    Oct 2008
    Location
    New York, NY
    Posts
    104
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Default Back End Only Opening Read Only

    So this has happened now 2 days in a row --

    I administer an Access DB with 12-15 users -- each user has an .accde copy of the front end on their desktop and the back end is on a shared server.

    I got a call saying that all of a sudden nobody could add a new entry to the db. I look into it and for some reason I can only open the Back End Read Only. I ensure that nobody is in the db and there is no laccdb lock file. But still, I can only open the back end read only.

    I make a copy of the back end -- make that the new back end db, and re-write everything to link to the new back end. I give all the users the new version and everything works fine.

    The next morning, the same issue happens again. I again made a new back-end, etc.

    Any ideas on what this is and how I can prevent it in the future?

  2. #2
    Board Regular
    Join Date
    May 2013
    Posts
    654
    Post Thanks / Like
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)

    Default Re: Back End Only Opening Read Only

    I would look at the properties for the file and see if it has been set to read only?

    If so, are the other files in the folder also set.?
    Is some process running that sets all files in folder to read only.?

    First test is the actual file itself.?

    HTH
    Office 2007
    Access novice. Sometimes trying to give something back

  3. #3
    Board Regular
    Join Date
    Jun 2015
    Location
    Ontario, Canada
    Posts
    1,702
    Post Thanks / Like
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)

    Default Re: Back End Only Opening Read Only

    Likely one or more users does not have the correct permissions on the be folder. Everyone must have full permissions otherwise they cannot delete or edit the lock file. If they cannot delete, a user can still open but put the db in a read only mode (or is it "exclusive"?). Last user out deletes lock file, but the db is "locked". Don't forget that a folder can inherit permissions from a parent folder, so that can be part of the problem as well (i.e. users may have the requisite permissions but the folder may have a limitation imposed from upstream). You might check to see if there is a command line switch for "shared" so that you can open the be with it, but I don't think so. You might be able to create a small db utility that will reset the be property back to shared. I have never done that, but I have altered other db properties with such db's.
    Tips for posting problems:
    1) "doesn't work" doesn't help. Post error message text/numbers and/or state what's happening.
    2) if posting code or sql, use code tags; specify on which code line errors occur, if applicable
    3) try to be specific; assume we know nothing about your issue - because we don't!

    Make all suggested changes in copies of your database or to its objects.

    "1 out of 1010 people understand binary. The other 1001 don't."

Some videos you may like

User Tag List

Tags for this Thread

Like this thread? Share it with others

Like this thread? Share it with others

Posting Permissions

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