Updating data in linked table?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Here's the deal. I have a local database with a linked table to an external
Access database (all this is in Access 2002). I created a delete query to
wipe the remote table, and an add query to populate it. However, the remote
database gives a "database is read-only" popup whenever anyone has it open.
When that's the case, my queries won't work (not allowed by db state). When I
check the remote database, it IS set to Shared access on startup.

So - what's the issue, and how can I do my delete/adds?

Thanks a million!
 
Dennis said:
Here's the deal. I have a local database with a linked table to an
external Access database (all this is in Access 2002). I created a
delete query to wipe the remote table, and an add query to populate
it. However, the remote database gives a "database is read-only"
popup whenever anyone has it open. When that's the case, my queries
won't work (not allowed by db state). When I check the remote
database, it IS set to Shared access on startup.

So - what's the issue, and how can I do my delete/adds?

Thanks a million!
Click to expand...

ALL users must have full permissions on the file AND the folder it resides in.
Do they? It is required for proper management of the locking file (LDB) that
Access creates, modifies, and deletes as people come and go in the app.
 
I don't know that answer. But I know that there were two people in that
database, and yet I saw NO .LDB file in that directory. And I've never seen
that before. My alternative is to "pull" the data into the shared database
from the user's local one. But I needed a way to identify who the user was,
in order that only certain people could execute that code. I found the Eviron
function and was able to get the logon-name from the system vars. Note that
the shared database does not use MDW security, nor will it be setup that way.

Thanks for your reply!

Dennis
 
I don't know that answer. But I know that there were two people in that
database, and yet I saw NO .LDB file in that directory. And I've never
Click to expand...
seen

Yes, that makes it read-only. Without the ldb file, Access can't
tell who is writing to what, so it doesn't let anybody write anything.

Not that that is a bad thing, if you only want read-only Access.

But if you give some other user read/write/create/delete, then
the read-only users will be locked out. Access will see the
ldb file, figure that someone is writing to the file, but be unable
to put read-locks on the file (necessary to ensure that you
read an internally consistent set of data if someone else may
be writing). In that situation, Access won't even let you read
the file.

So you have to give everyone modify permission, or no-one.
Or lock out the read-only users while you write to the file.

(david)
 
Back
Top