no read permissions on MSysAccounts

K

Karl Rosentrater

Hi,

Converting run-time applications from Access 97 to Access
2000 with user level security in place, using a Workgroup
Information File originally created with Access 2.0,
generates the error 'Record(s) cannot be read; no read
permission on 'MSysAccounts''. The KB article says this
can only be corrected by re-creating the Workgroup
Information File in Access 2000; in order to do that, you
need the original name, organization, and Workgroup ID
used in the original Workgroup Information File. This
information was lost with the predecessor before my
predecessor.

2 questions. Is there any way to hack these values (name,
organization, and Workgroup ID) for the Workgroup
Information File. And will the neccesity to recreate the
Workgroup Information File go away in Access 2002?
 

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

Similar Threads

Sub projects added as read only in Master file which are saved on sharepoint 1
Converting a protected database 2
Deleted Workgroup Information File 4
Workgroup File - Access 2007 2
Removing Admin Permissions from my database 1
Accessing a Jet Database with User level Security using ADO 2
Error Message:'MSysAccounts' 1
How to get rid of a workgroup .mdw file 2

Top