Article ID: 236878 - View products that this article applies to.
This article was previously published under Q236878
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:
You receive this error even though you have sufficient permissions to open and view the table or query.
Run-time error '3112':
Record(s) can't be read; no read permission on 'tablename'
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:
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
Article ID: 236878 - Last Review: January 24, 2007 - Revision: 4.1
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.