-
Hi Guys
Having a bit of a problem. Trying to open a mde database, I kinda think that a mde file is a mdb file that has been compiled . Is this right ?
When I try to open the mde app I get this message:
Record(s) can'tbe read; no read permission on MSysModules2
what does this mean and why cant I open it ?
I know this program has password protection for the different users of the app. Thier are two groups users and sysadmin set up for this app. I am trying to access the app over the network and prob don't have the same mdw file as the users, could this be the problem ? I didnt think it would be as I thought I would get prompted to enter a username and password where I could then log on as sysadmin with the correct password. Is this not the case ?
Any help understanding what is happening would be much appreciated.
Locutus.
-
That's a database corruption problem. One of your objects **** the bed. Here are the different ways to handle it, in descending order of time consumption and ascending order of likelihood of success:
1) Create a new mdb file, import all objects (except linked tables - relink the tables manually) from the corrupted database in one shot.
2) If 1 doesn't work, try the same thing except just the queries, then modules, then reports, then forms, then tables. (Macros are evil)
3) If you can't import anything from the corrupted file, you have to export from it. Open the mdb without running the app (hold shift down when you open it). Select each object, 1 at a time, and export to a new mdb.
Also, when importing/exporting, hit the options button to include relationships, Import/Export Specifications, and any Menus and Toolbars you have defined.
Good luck, it's a frustrating problem. I've noticed that exact error mostly when a multi-user access app has it's front end on the network and everybody runs it directly from there. That's a no-no. Put the front end locally on everyone's machine...only the data should be on the network.
