No read permissions

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

I am trying to access a table in anoter mdb file:

Set rst = OpenDatabase("database.mdb").OpenRecordset("Select * from
CheckItems")

I get the error:

3112, Record(s) cannot be read; no read permissopn on "CheckItems"

I can however, open a second copy of Access 97 and access that table.

Thanks,
J.
 
Jason said:
I am trying to access a table in anoter mdb file:

Set rst = OpenDatabase("database.mdb").OpenRecordset("Select * from
CheckItems")

I get the error:

3112, Record(s) cannot be read; no read permissopn on "CheckItems"

I can however, open a second copy of Access 97 and access that table.
Click to expand...


In principle, that syntax ought to work, but it looks like there's a
security issue.

Is the database being opened (which you're calling "database.mdb") secured
by user-level security? If so, does it use a different workgroup file than
the one being used by the database in which this code is running?
 
It uses the same workgroup file.
Dirk Goldgar said:
In principle, that syntax ought to work, but it looks like there's a
security issue.

Is the database being opened (which you're calling "database.mdb") secured
by user-level security? If so, does it use a different workgroup file
than the one being used by the database in which this code is running?

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)
Click to expand...
 
It uses the same workgroup file. Also there might not even be any user
security on the file I'm trying to open either.

Thanks,
J.
 
Jason said:
It uses the same workgroup file. Also there might not even be any user
security on the file I'm trying to open either.
Click to expand...


I'm not sure what's going here, unless it is simply that the currently
logged in user really doesn't have read permissions on the table in
question. Have you verified that?

I tested a similar setup and found that being logged into the correct
workgroup allowed me to open a recordset on a table in a secured external
database. So I can't help thinking that the problem is in the permissions
assigned to the specific logged-in user or group.
 
Jason said:
I can manually open the table by opening the mdb within access.
Click to expand...


Are you doing it while logged in to the same workgroup file? Can you open
Access and the original database (the one that has the code that is raising
the error), then close that database without closing Access, and then --
from that same instance of Access -- open the other database and table? If
you can do that, then I am stumped, and the only thing I can suggest is that
you send me both databases, and the related workgroup file(s) and login
credentials, to test with.

If you choose to do that, it would be best if you sent cut-down copies
containing minimal data and only the elements necessary to reproduce the
problem, compacted and zipped to minimize the transmitted size. You can get
my e-mail address by removing NO SPAM and ".invalid" from the reply address
of this message, or else from my website, which is listed in my sig, below.
I'll have a look at it, time permitting.
 
Back
Top