Strange linked table behavior

  • Thread starter Matt Fragale via AccessMonster.com
  • Start date
M

Matt Fragale via AccessMonster.com

For some reason which is currently outside of my knowledge, one of my
databases is exhibiting an unusual behavior. The database has no data of
it's own and is linked to a couple other databases as back ends. Certain
of the tables suddenly tell me that their recordsets are not updateable
when I try to edit them. I noticed this when running an update process that
copies data from a text file into the tables. At first I thought the
import process had broken somehow. But when I go directly to the linked
table I cannot change anything there either.

When I go to the back end of the database and open it, Access says that the
database itself is Read Only. However, when I check the properties of the
database it is not listed as Read Only. Ahhhhh, permissions! I thought.
But alas, I have read/write/execute/delete permissions to the application
and the folder that it resides in. Interestingly, this is an intermittent
problem. It happened to me two days ago, but then worked later in the day.
It worked fine yesterday as well. Now this morning, it is not updateable
again.

We have relatively recently switched to Active Directory and Windows Server
2k3. I'm not sure if this has anything to do with it, but it has odd
effects on several things so I was thinking it might.

Has anyone ever run into a similar situation? Any ideas how to fix it??
It's frustrating because I have stuff that's due kind of early in the
morning and when this occurs, everything is late.

Thanks!!
 
J

Joan Wild

Hi Matt,
But alas, I have read/write/execute/delete
permissions to the application and the folder that it resides in.
Interestingly, this is an intermittent problem. It happened to me
two days ago, but then worked later in the day. It worked fine
yesterday as well. Now this morning, it is not updateable again.

You may have those permissions, but do other users? Since it is an
intermittent problem, it sounds like another user is opening the database
exclusively, and locking you out. Check that all users have those
permissions on the folder.
 
M

Matt Fragale via AccessMonster.com

Well, that WOULD be the easy answer. But it doesn't seem to be the case.
Because that would actually lock me out of the database. When you open an
mdb exclusively, no one else can open it. I can open it just fine. It's
just that it is now Read Only. And it's the whole database, not just
specific tables. My second thought was that maybe I had the record locking
screwed up, but that's not it either.

The freaky thing is, when you go to Windows Explorer and look at it, the
mdb file doesn't say that it's Read Only. It only looks like it when you
try to open it. Everyone's permissions are what they should be.

Similar issue creeped up with one of my front end applications on users' C:
drives when we moved to Windows Server 2k3 and Active Directory. Whenever
a new user would come to a machine, it would tell the first user that the
database was Read Only, and they could not update anything. This is the
first time it has cropped up with a back end app. For the front end app,
it was easy to fix. I just put the front end app in everyone's shared
network space (which was nicer anyway since it follows them around in their
profile) and the problem was resolved. I can't do that with the back end,
obviously.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top