Moving a secure database

I have a database that is currently on a shared drive. I made the database a secure database using the User Level Security Wizard. This worked great. Now I am being told by our CTO that it needs to be moved to another drive (which will have the same permissions). Will there be any problems with this move?

Also, once you make a database secure through the User Level Security Wizard, can I make it a regular old database again?

Thanks.

Gale - Trying Not To Be A Newbie - Fulton

>Will there be any problems with this move?

Gale,

I have moved my secure databases to other offices (using Access 2000) but you must make sure that the security file (.mdw file extension) is also still available or moved with the database. I really like using the access startup extensions so that the default mdw file or errant mdw files are not used. For example, in the desktop icon, under shortcut properties of the icon, I place the following in the "target":

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" n:\Hours\cmsTime.mdb /wrkgrp k:\server\AML2000.mdw

Realize that n:\hours and k:\server are drives and directories on our network. Substitute your own drives and directories

>Also, once you make a database secure through the User Level Security Wizard, can I make it a regular old database again?

I just read up on this yesterday. I have not attempted it, but it can be done. Look up in Access help for "Remove user-level security"

Hope this helps a little. You are the first person I have ever attempted to help on this forum!

BetsyBean

Hey there...I just used your: How to get the Username post about 10 minutes ago.

Thank for the infor on the secure database moving and "un-securing"

Going back to the username post, I am looking to extract the user logged into the database instead of the network. This will do for now, but if say Joe is logged onto a computer, and Ted acceses this database from that computer, he still has to log into the database with his username and password (from the User Security Wizard). However, my log file will say it was Joe because he was logged into the network.

Like I said, this will do for now, but I am going to work at it because I am using this new database for my techs to log installation issues from their computer and create a database that will eventually lead to an FAQ report.

LWells has ben a really big help in getting me started on using Access, and now I am trying to use it for everything...ha ha ha.

Thank you again.

Hi Gale,

Take a look at this link and see if it has anything useful for you in trying to figure out who is logged in. It may just be a variation of what you already have.

http://support.microsoft.com/kb/198755/EN-US/

lwells

I understand the code and what it will accomplish, but it doesn't seem to work with my secured database. But it's OK, it is only my idea for this particular database, not a requirement. The user logs in to add an issue report. The report is then e-mail to me and that has their log in name, date and time. So I really already have what I need, I was just trying to make a record log.

Thanks.