Access95 security

[stormin_norm]

At my client's site they have access95 running on some client pcs. They tried to open/convert it to 2000, but received an error message.
We tried to move the database and open up privileges, but it still points to the g:\users.mdw file, not our new d:\users.mdw file.

Where do you change the security file in access95? wrkgadm.exe does not work. It must be in an .ini??

Thanks
-norm.

 

[The_Doc_Man]

It is not enough to convert the database. You must also open and convert the .MDW file, which is itself an Access database (of a limited sort.)

Or create a new .MDW file and join it. But be prepared to manually reassert your permissions on darned near everything.

The problem is that Workgroup membership for Access is a persistent registry value that can only be overridden in a couple of ways. One involves a shortcut that contains a direct workgroup reference. (Look in Access help for command-line options.) The other is to manually join a new workgroup.

 

[Parker]

At my client's site they have access95 running on some client pcs. They tried to open/convert it to 2000, but received an error message.
We tried to move the database and open up privileges, but it still points to the g:\users.mdw file, not our new d:\users.mdw file.

Where do you change the security file in access95? wrkgadm.exe does not work. It must be in an .ini??

Thanks
-norm.

The only sure way I have found is to unsecure the db first and then rebuild the .mdw.

Open the db in its origonal form and log on as admin. Change the permissions for the Users group to give full permissions for everything.
Exit and restart Access and log on as Admin. again

Create a new blank database, and leave it open.
Import all the objects from the original database into the new database.

Clear the password for Admin to turn off the Logon dialog box save the new db. You now have an unsecured version of your db.

Convert it and shift it to wherever and restructure your security.

 

[stormin_norm]

Thanks Parker & Doc_Man.

Just curious if you know how/where access95 points to the mdw file? Even with a wrkgadm join, my client still points to the network drive. She wanted to work on the database locally, but can not unlink the network mdw file from the database.
Once she gets both the database & mdw file working on her hard drive, then she can open up permissions and run the import.

-norm.

 

[Parker]

Thanks Parker & Doc_Man.

Just curious if you know how/where access95 points to the mdw file? Even with a wrkgadm join, my client still points to the network drive. She wanted to work on the database locally, but can not unlink the network mdw file from the database.
Once she gets both the database & mdw file working on her hard drive, then she can open up permissions and run the import.

-norm.

Do I understand from this that you have no access to the mdw? Have you moved the db off the network on which it originally resided without moving the .mdw with it?

 

[stormin_norm]

Do I understand from this that you have no access to the mdw? Have you moved the db off the network on which it originally resided without moving the .mdw with it?

She copied the .db & .mdw, but when she modifies the Admin user priveleges, she sees the changes on the network drive, not her local d: drive. She mentioned she could still see it pointing to the network because when she ran the wizard it showed which file she was joined to.
Shouldn't wrkgadm be the only way to switch them? Or is there another way in 95?
Thanks Parker.

 

[stormin_norm]

The only sure way I have found is to unsecure the db first and then rebuild the .mdw....

Worked great. She was able to convert it over.
Thanks Parker.

I'll see her thursday, maybe I can see how she was pointing to the network .mdw. I don't have 95, so I can test here.