Moving DB

[Nanette]

I added security to a database that I've been moving back and forth between
work and home. I copy the database onto a thumb drive and bring it home and
visa versa.

This holiday I experimented with adding security. Everything worked fine,
but now I'm concerned about copying the newest database and bringing it to
work.

I'd like any comments about this and if I should attempt to completely
delete the security before I copy it and take it back to work.

 

[Douglas J. Steele]

As long as you've got the MDW that you used to add security, you should be
okay.

If you don't want to use that MDW file at work, then yes, you probably
should remove security on the copy before taking it back to work.

 

[Nanette]

Would deleting the MDW file get rid of all the security?

 

[Rick Brandt]

Would deleting the MDW file get rid of all the security?

No. If you applied security properly deleting the MDW file would make your file
useless as you should not be able to open it unless you are logged into that MDW
file.

If you CAN open it with another MDW then you never secured it properly in the
first place.

 

[Nanette]

What is the safest way to get rid of all security on a database?

 

[Rick Brandt]

What is the safest way to get rid of all security on a database?

Open the file with a profile that has administrator rights and grant full rights
on all objects to the Users group.

Close Access and reopen using the default System.MDW file.

Create a new blank file and import into it all objects from your current file.

The resulting file will be identical to one that never had security applied.

 

[Nanette]

Thanks Rick

Open the file with a profile that has administrator rights and grant full rights
on all objects to the Users group.

Close Access and reopen using the default System.MDW file.

Create a new blank file and import into it all objects from your current file.

The resulting file will be identical to one that never had security applied.