Re: Please explain *.mdw

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 07/17/04 

Date: Sat, 17 Jul 2004 07:43:23 -0400

If security was applied to autobody.mdb (which seems to be the case), then
you need whatever mdw file was associated with the database when security
was applied. That could be system.mdw (although realistically that would, in
my opinion, have been a mistake on the part of whoever applied security to
the database). 

-- 
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"mbox204" <noisp94@yahoo.com> wrote in message
news:O0x$Pa4aEHA.2516@TK2MSFTNGP10.phx.gbl...
> Thank you in advance.
>
> Could someone please explain the below in some level of detail, I have
> broken down the line into segments.
>
> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
>
> 1. "path to msaccess.exe"
> This I understand to be the path to where msaccess resides on my PC
>
> 2. "path to mdb" /wrkgrp
> This I understand to be the path to where my access database resides.
> What is the /wrkgrp for?  Do you use this as is or replace with something
> else like a workgroup name (i.e. /admin)
>
> 3. "path to secure mdw"
> I understand this to also be a path to the system.mdw file.  Can this be
any
> system.mdw file that is installed with Microsoft Access or must it be the
> file created when the secured database was created?
>
> The reason I ask these questions, the application I am currently working
on
> is no longer on the PC that it was developed on.  This application resides
> on a completely brand new PC and when I open the access file I get the
error
> message associated with a message as such:
>
> "You do not have the necessary permission s to use the
> 'F:\Security\autobody.mdb.  Have your system administor or
> the person who created the object establish the appropriate permissions
for
> you."
>
> The system administrator is not the person who created this application
and
> as such the person who did create the application has long been gone.
This
> application is an Access database file that was transferred to the new PC
> which has Access 97 residing on it, as well as the Access 2002.  Access 97
> is installed onto this new machine only to run this application and now
> cannot open it for some reason since it was transferred to the new
machine.
> The old machine was gutted, hard drive erased, etc, it and all content is
> history.
>
> File name of Access application is: autobody.mdb
> The is nowhere to be found any file such as autobody.mdw, only system.mdw
> and it is what was installed with the new PC when Access 97 and 2002 were
> installed.
>
> Am I out of luck on this one?  Any advice or direction to information
would
> be welcome.  To rewrite this application would cost a lot of money.
>
>

Relevant Pages

  • Re: MDE
    ... - You are using the incorrect MDW file used to secure the database. ... MDE open or not) select teh menu option Tools> Security> User and Group ... if you don't see the other User Accounts you created when the ...
    (microsoft.public.access.security)
  • Re: Whos in the .ldb first?
    ... If the .mdw file you secured the database with isn't there, ... good indication that your security wasn't set up correctly. ... >>have full permissions on the FOLDER that the database is ...
    (microsoft.public.access.security)
  • Re: security not requesting log in
    ... If you had done this, then no matter what mdw file she used, ... Another step you should have performed is to secure the database file. ... and delete all the security files and create a new file. ... opens immediately to the main screen and shows her as Admin. ...
    (microsoft.public.access.security)
  • Re: security not requesting log in
    ... If you had done this, then no matter what mdw file she used, ... Another step you should have performed is to secure the database file. ... and delete all the security files and create a new file. ... opens immediately to the main screen and shows her as Admin. ...
    (microsoft.public.access.security)
  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)