Hi, Damien.
how can I move the mdw
without screwing things up?
This locking database file problem comes into play whenever a user needs to
log into the database in exclusive mode. You need to decide whether making
this change is worth the pain involved. Personally, I'd go with the pain
now to keep from increasing the pain later as more users get added to the
workgroup.
If you decide to make the change, then you'll need to communicate with your
users immediately so that you can make this change with the smallest snafu.
You have the choice to change the name of the MDW file or change the
location of the current MDW file to another network shared directory. Then
you'll create a Windows shortcut to open the secured database with the new
name or new location of the MDW file.
The next step depends upon how your users are currently opening the
database. If your users have a shortcut (which includes the current MDW
file) to the database on their desktops, then you'll need to distribute the
new shortcut to your users and have them replace their old one <yikes!>. If
the users are joined to the workgroup from the current MDW file, then
they'll all need to join the default Access workgroup (System.MDW) <groan!>,
then you'll need to distribute the new shortcut to your users and have them
replace their old one <yikes!>. If your users aren't currently using a
shortcut, then they certainly will after you distribute the new shortcut.
Don't expect this to go smoothly. Murphy was an optimist, you know. ;-)
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)