This article was previously published under Q236878
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Moderate: Requires basic macro, coding, and interoperability skills.
In Visual Basic for Applications code, when you try opening a table or query from a secure database with the OpenRecordset method, you may receive the following error message:
Run-time error '3112': Record(s) can't be read; no read permission on 'tablename'
You receive this error even though you have sufficient permissions to open and view the table or query.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. Through code, you must define the workgroup information file before opening the secured database. The following code demonstrates how to do this:
Function OpenMyDb() Dim WS As Workspace Dim DB As Database Dim Rs As Recordset ' Define the workgroup information file (system database) you will use. DBEngine.SystemDB = "C:\Windows\System\MyWkgrp.mdw" ' OPTIONAL: Create a workspace with the correct login information 'Set WS = CreateWorkspace("NewWS", "MyID", "MyPwd", dbUseJet) ' OPTIONAL: If you set the workspace object, you can use the new ' workspace with the OpenDatabase command. For example: 'Set Db = WS.OpenDatabase("C:\My Documents\MyDB.mdb") ' Set DB = OpenDatabase("C:\My Documents\MyDB.mdb") Set Rs = DB.OpenRecordset("MyTbl") Rs.Close Set Rs = Nothing DB.Close Set DB = Nothing ' OPTIONAL: If you set the WS object, use the following to clean up 'WS.Close 'Set WS = Nothing MsgBox "Done"End Function
Although you receive the error mentioned in the "Symptoms" section, you are still able to link manually or import tables and queries from that secure database.
If you are using a macro to open a database, you cannot join the workgroup information file that is required to log on.
Steps to Reproduce Behavior
Create a new workgroup information file named MyWkgrp.mdw.
Open any database, and change the password for the Admin user.
Create a new user named MyID as a member of the Admins group.
Quit and then restart Access. Log on as MyID.
Create a new database named MyDB.mdb and save it in the C:\My Documents folder.
Remove the Admin user from the Admins group.
Add one table to the database and name it MyTbl.
Add a few records to the table.
Give the Users group only Read Data and Read Design permissions for the MyTbl table.
Close MyDb.mdb, and then create a new blank database.
Insert a new module and type the following code:
Function OpenMyDB() Dim DB As Database Dim Rs As Recordset Set DB = OpenDatabase("C:\My Documents\MyDB.mdb") Set Rs = DB.OpenRecordset("MyTbl") Rs.Close Set Rs = Nothing DB.Close Set DB = Nothing MsgBox "Done"End Function
In the Debug window, type the following line, and then press ENTER:
Note that you receive the error message mentioned in the "Symptoms" section.