How can I get rid of opening with /WRKGRP system.mda?

I revivied an old database that used this to open it:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"c:\access\oldDB.mdb" /WRKGRP "c:\access\system.mda"

That required me to use a username and password to open it.

I then made the mistake of opening a current database and suddenly it now
requires the same username and password. I don't need the old database,
just some code from it.

How do I remove the username and password completely from the database I use
all the time, and so do a couple of other people? I tried to set the
password to blank but this didn't work. I also tried using

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"c:\access\oldDB.mdb" /WRKGRP "C:\windows\system32\system.mdw"

I can now open the database if I use the system.mdw but I don't want to; I
want to be able to click on it and it opens, which it won't without a
username and password.

How can I fix this mess panic!?

Thanks,
Mich
(Posted in the security group earlier - no answer)

It sounds like you are joined by default to system.mda. Open the workgroup
administrator (either Start, Run, wrkgadm.exe or Tools, Security, Workgroup
Administrator) and click on Join and join c:\windows\system32\system.mdw


--
Joan Wild
Microsoft Access MVP

M Skabialka wrote:
I revivied an old database that used this to open it:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"c:\access\oldDB.mdb" /WRKGRP "c:\access\system.mda"

That required me to use a username and password to open it.

I then made the mistake of opening a current database and suddenly it
now requires the same username and password. I don't need the old
database, just some code from it.

How do I remove the username and password completely from the
database I use all the time, and so do a couple of other people? I
tried to set the password to blank but this didn't work. I also
tried using
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"c:\access\oldDB.mdb" /WRKGRP "C:\windows\system32\system.mdw"

I can now open the database if I use the system.mdw but I don't want
to; I want to be able to click on it and it opens, which it won't
without a username and password.

How can I fix this mess panic!?

Thanks,
Mich
(Posted in the security group earlier - no answer)

Whew, thanks! I thought I was in quite a pickle there!

I never did like the security that comes with access, preferring to use
windows security on the back-end data.

Mich

"Joan Wild" wrote in message
...
It sounds like you are joined by default to system.mda. Open the
workgroup administrator (either Start, Run, wrkgadm.exe or Tools,
Security, Workgroup Administrator) and click on Join and join
c:\windows\system32\system.mdw


--
Joan Wild
Microsoft Access MVP

M Skabialka wrote:
I revivied an old database that used this to open it:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"c:\access\oldDB.mdb" /WRKGRP "c:\access\system.mda"

That required me to use a username and password to open it.

I then made the mistake of opening a current database and suddenly it
now requires the same username and password. I don't need the old
database, just some code from it.

How do I remove the username and password completely from the
database I use all the time, and so do a couple of other people? I
tried to set the password to blank but this didn't work. I also
tried using
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"c:\access\oldDB.mdb" /WRKGRP "C:\windows\system32\system.mdw"

I can now open the database if I use the system.mdw but I don't want
to; I want to be able to click on it and it opens, which it won't
without a username and password.

How can I fix this mess panic!?

Thanks,
Mich
(Posted in the security group earlier - no answer)

M Skabialka wrote:
Whew, thanks! I thought I was in quite a pickle there!

I never did like the security that comes with access, preferring to
use windows security on the back-end data.

I'm surprised that hasn't caused problems. Users need
read/write/create/delete permissions on the folder where the BE is, in order
to create the associated ldb file.

--
Joan Wild
Microsoft Access MVP

They do, they just don't know where it is!

"Joan Wild" wrote in message
...
M Skabialka wrote:
Whew, thanks! I thought I was in quite a pickle there!

I never did like the security that comes with access, preferring to
use windows security on the back-end data.

I'm surprised that hasn't caused problems. Users need
read/write/create/delete permissions on the folder where the BE is, in
order to create the associated ldb file.

--
Joan Wild
Microsoft Access MVP