I need a bit of help with a problem that I just experienced. I created a 
SYSTEM.MDW file for a shared DB some time ago but ultimately decided to go 
with my own security instead - user names and passwords as opposed to 
Access UserLevel Security. That made it where I no longer needed the 
SYSTEM.MDW file any longer or at least that is what I thought. I just 
tried to remove that file and when I did I lost all access to any DB on my 
machine.

My question is how to I end the link between my DB and the SYSTEM.MDW file 
so that it can be safely deleted or the program can be saved to another 
folder location?

Thanx for any and all help....


Kenny

Kenny

Access is always linked to a MDW file. When you were experimenting with 
user-level security, did you create a new MDW file? Or did you use the 
default one?

Brian

> I need a bit of help with a problem that I just experienced. I created a 
S> YSTEM.MDW file for a shared DB some time ago but ultimately decided to 
go 
w> ith my own security instead - user names and passwords as opposed to 
A> ccess UserLevel Security. That made it where I no longer needed the 
S> YSTEM.MDW file any longer or at least that is what I thought. I just 
t> ried to remove that file and when I did I lost all access to any DB on 
my 
m> achine.

> My question is how to I end the link between my DB and the SYSTEM.MDW 
file 
s> o that it can be safely deleted or the program can be saved to another 
f> older location?

> Thanx for any and all help....

> 
K> enny

Brian

Thanx for the reply .. I created a new file. It seems by your reply that I 
do need to keep the file somewhere on the system. The problem is that I 
saved the file in a location with the DB and now I am required to change 
the location of the DB. When I tried that I also moved the *.mdw and that 
is where me problem began. I would be fine if I could move the *.mdw with 
the DB and it would work... Any ideas??

Kenny

If your users access the application through a shortcut you can make
explicit reference to the mdw file in the command line like:-
"apppath/appname.mdb" /wrkgrp "mdw file path and name"

HTH
Omar
-----Original Message-----
From: Kenny Alligood [mailto:kennyalligood@h...] 
Sent: 24 September 2002 15:14
To: Access
Subject: [access] Re: SYSTEM.MDW

Brian

Thanx for the reply .. I created a new file. It seems by your reply that I 
do need to keep the file somewhere on the system. The problem is that I 
saved the file in a location with the DB and now I am required to change 
the location of the DB. When I tried that I also moved the *.mdw and that 
is where me problem began. I would be fine if I could move the *.mdw with 
the DB and it would work... Any ideas??

Kenny


  DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee.  Access to this
message by anyone else is unauthorised.  If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful.  Please immediately contact the sender if you have received this
message in error. Thank you.

Kenny

The MDW file that Access uses is linked to your Access installation - NOT to a particular database. If you are not using the user
level security in your database, I'd suggest you relink Access to the default SYSTEM.MDW file. 

You'll find this in either the system, system32 or the MS Office installation directory, depending on the version of Access you're
using.

Brian

>  from:    Kenny Alligood <kennyalligood@h...>
>  date:    Tue, 24 Sep 2002 15:13:47
>  to:      access@p...
>  subject: Re: [access] Re: SYSTEM.MDW
> 
> Brian
> 
> Thanx for the reply .. I created a new file. It seems by your reply that I 
> do need to keep the file somewhere on the system. The problem is that I 
> saved the file in a location with the DB and now I am required to change 
> the location of the DB. When I tried that I also moved the *.mdw and that 
> is where me problem began. I would be fine if I could move the *.mdw with 
> the DB and it would work... Any ideas??
> 
> Kenny

1 Create a blank database with the DEFAULT system security file.

2. Re-link system file you made with the database and open the new black
database.  EXPORT all tables, queries, forms and everything else, including
click the options box at the bottom of the export window and select menus
and toolbars so it will take them as well.

3.  After importing the objects, close access and using the workgroup admin,
re-link the DEFAULT system file and there you go.  No more security is
needed to run the program.  Runs on the default security file with no
password or security.

Terry

-------Original Message-------

From: Access
Date: Monday, September 23, 2002 6:58:06 PM
To: Access
Subject: [access] SYSTEM.MDW

I need a bit of help with a problem that I just experienced. I created a 
SYSTEM.MDW file for a shared DB some time ago but ultimately decided to go 
with my own security instead - user names and passwords as opposed to 
Access UserLevel Security. That made it where I no longer needed the 
SYSTEM.MDW file any longer or at least that is what I thought. I just 
tried to remove that file and when I did I lost all access to any DB on my 
machine.

My question is how to I end the link between my DB and the SYSTEM.MDW file 
so that it can be safely deleted or the program can be saved to another 
folder location?

Thanx for any and all help....


Kenny
.