Joining MDW files

  • Thread starter Thread starter George
  • Start date Start date
G

George

Hi all,

I have encountered a little problem in XP. I create a new
MDW file (New.mdw) inside a database (DB1.mdb) and create
a user/password. Afterward, I create a shortcut to DB1
that points to New.mdw. At this point, I am prompted for a
password when opening this database by directly clicking
on DB1.mdb and its shortcut.

However, an existing database of mine (DB2.mdb), when I
attempt to open it, prompts for a password as well.
Somehow it thinks that the default mdw file associated
with itself is changed. Therefore I log into DB2 (using
the user name and password created in new.mdw) and join
its workgroup file back to System.mdw (thru Workgroup
Adminstrator). I then exit out of DB2.mdb and am able to
open it without being prompted a password.

At this point, the shortcut to DB1 still works: it
prompots for a password. However, directly clicking on DB1
does not prompt for a password. I then join its workgroup
file back to New.mdw (thru Workgroup Adminsitrator). This
fixes DB1: both the shortcut and its own icon work.
However, DB2 now uses New.mdw and prompts for a password.
I'm back to the loop again.

My question: how can you specify that only 1 database
(DB1.mdb) usest the new.mdw file, while all other existing
databases (such as DB2.mdb) still use System.mdw?
 
Hey George,

Access always uses a .mdw file when opening a database. By default, Access
is pointed to system.mdw somewhere in your local drive. This means if you
manually open a database using File>>Open, or double-clicking on an mdb file
in explorer, Access automatically uses whatever mdw file it's previously
pointed to.

Two ways to change this default:

- Join a different mdw file using Workgroup Administrator. Once you join
this different mdw file, this different mdw file will be the default.

- Override the default mdw file by creating a shortcut:
"<path to msaccess.exe>" "<path to frontend.mdb>" /wrkgrp "<path to
security.mdw>" on your desktop. Overriding in this case means it's effective
only during this session, the default mdw is still whatever mdw file Access
is pointed to BEFORE this session.

Also see my inline comments below


HTH
Immanuel Sibero



George said:
Hi all,

I have encountered a little problem in XP. I create a new
MDW file (New.mdw) inside a database (DB1.mdb) and create
a user/password.
Click to expand...

At this point you probably joined New.mdw. Therefore, new.mdw becomes the
default.
Afterward, I create a shortcut to DB1
that points to New.mdw. At this point, I am prompted for a
password when opening this database by directly clicking
on DB1.mdb and its shortcut.
Click to expand...

This makes sense, since you're joined to New.mdw.
However, an existing database of mine (DB2.mdb), when I
attempt to open it, prompts for a password as well.
Click to expand...

Yes, Access will prompt for a password since you're still joined to New.mdw
Somehow it thinks that the default mdw file associated
with itself is changed.
Click to expand...

Correct, the default has changed.
Therefore I log into DB2 (using
the user name and password created in new.mdw) and join
its workgroup file back to System.mdw (thru Workgroup
Adminstrator). I then exit out of DB2.mdb and am able to
open it without being prompted a password.
Click to expand...

This makes sense since you reverted back to the original system.mdw that
Access comes with. All unsecured database will open without being prompted
with a password

At this point, the shortcut to DB1 still works: it
prompots for a password.
Click to expand...

This works because you're overriding the mdw file with New.mdw, even though
the default has been changed back to system.mdw.

However, directly clicking on DB1
does not prompt for a password.
Click to expand...

No password required here, since you're joined back to system.mdw. This
tells me that New.mdw may not be properly secured. Is the user Admin still
there? Does it have administrative rights??

I then join its workgroup
file back to New.mdw (thru Workgroup Adminsitrator). This
fixes DB1: both the shortcut and its own icon work.
However, DB2 now uses New.mdw and prompts for a password.
I'm back to the loop again.

My question: how can you specify that only 1 database
(DB1.mdb) usest the new.mdw file, while all other existing
databases (such as DB2.mdb) still use System.mdw?
Click to expand...

Use the override method with shortcut on your desktop. This is actually a
commonly used method. Dont bother running Workgroup Admin on workstations to
join different mdw files. Just leave them joined to their local system.mdw.
 
Back
Top