Point to correct .MDW file

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have created an application that requies the user to log in. I have
compiled the app into a .mde. I know I can distribute it along with my
System.MDW file that they can use to replace their current one. But this
also causes the user to enter their userID and password even when they open
any other Access files.

Is there a way, when the user opens my .mde, to point to my own XXX.MDW
file, which they have placed in the same folder as the .mde?

If possible, I do not want to have them do anything other than place the
..mde file and the XXX.MDW file in a folder and open the .mde.
 
Bill said:
Is there a way, when the user opens my .mde, to point to my own
XXX.MDW file, which they have placed in the same folder as the .mde?

If possible, I do not want to have them do anything other than place
the .mde file and the XXX.MDW file in a folder and open the .mde.
Click to expand...

The only way to do it is to give them a desktop shortcut that has a target
of

"full path to msaccess.exe" "path to mde" /wrkgrp "path to mdw"

If they all put it in the same folder, and they all installed Access to the
same place, then you can create the shortcut for them and just tell them to
put it on the desktop.
 
I tried as you said... moved my System.MDW to the same folder as my
application, renamed it to XXX.MDW. Then created a new vanilla System.MDW in
the proper location for Access. Then created a shortcut to my application,
specifying the full path to the app and / wrkgrp full path to XXX.MDW

Security is now completely bypassed.

What am I not doing?
 
Bill said:
I tried as you said... moved my System.MDW to the same folder as my
application, renamed it to XXX.MDW. Then created a new vanilla
System.MDW in the proper location for Access. Then created a
shortcut to my application, specifying the full path to the app and /
wrkgrp full path to XXX.MDW
Click to expand...

You need to include the full path to msaccess.exe or the switch is ignored,
which is an indication of a problem...
Security is now completely bypassed.
Click to expand...
What am I not doing?
Click to expand...

You didn't implement security properly to begin with. From the sounds of
it, you modified your original system.mdw - that workgroup is common to
every installation of Access in the world. The first step is to create a
new workgroup file using the workgroup administrator.

If you miss a single step, your database won't be secure. Be sure to follow
the steps outlined in the FAQ
http://support.microsoft.com/?id=207793
 
Joan,

I unsecured my database, downloaded and followed the Security FAQ, creating
my own new Workgroup file and setting up all my users. Everything worked,
EXCEPT when I decided to test the shortcut, I moved the Workgroup to a
different location, security was lost. When I moved the Workgroup file back
into place, it was still lost, and the workgroup file I was now pointed to
was one called "system1.mdw" in the normal location for SAystem.mdw.

I consider this a valid test, because when I send the files to the users, I
have no control over which hard drive or directory into which they install
things, except that all the items I send them will be put into one directory.

Any suggestions?
 
Bill said:
Joan,

I unsecured my database, downloaded and followed the Security FAQ,
creating my own new Workgroup file and setting up all my users.

I consider this a valid test, because when I send the files to the
users, I have no control over which hard drive or directory into
which they install things, except that all the items I send them will
be put into one directory.
Click to expand...

You are correct, it is a valid test. What it is telling you is that you
missed a step in securing it. Every step, must be followed exactly.

Security is not simple. You can try the steps I've outlined at
www.jmwild.com/AccessSecurity.htm
 
Joan,

I went to your site and picked up the doc Access 2002/2003 Security Step by
Step.

I have followed the steps meticulously 4 different times now. When I am
joined to the workgroup I create, everything is fine, but when I rejoin the
default workgroup system.mdw, whether I open the secured mdb directly or
through a shortcut, specifying the workgroup file I created, I get the same
results: NO request for a password, and a message saying I have no
privileges to access the mdb. As soon as I rejoin the created workgroup,
everything is fine again.
 
Bill said:
Joan,

I went to your site and picked up the doc Access 2002/2003 Security
Step by Step.

I have followed the steps meticulously 4 different times now. When I
am joined to the workgroup I create, everything is fine, but when I
rejoin the default workgroup system.mdw, whether I open the secured
mdb directly or through a shortcut, specifying the workgroup file I
created, I get the same results: NO request for a password, and a
message saying I have no privileges to access the mdb.
Click to expand...

This sounds good! You rejoin the default system.mdw and try to open the
secure mdb you should get no login, and be told you don't have permissions.

If you open through a shortcut, specifying the workgroup file, you should
not get this result. You should be presented with a login. Post back with
exactly what you have in the target of the shortcut. It sounds as though
you are missing the full path to msaccess.exe at the front.

eg.
"C:\Program Files\Microsoft Office\Office\msaccess.exe"
"C:\somefolder\mydb.mdb" /wrkgrp "c:\somefolder\mysecure.mdw"

As soon as I
rejoin the created workgroup, everything is fine again.
Click to expand...

This would be good. There is something missing from your shortcut.
 
Joan,

The full path to Access did it, along with clearing another glitch. It is
"/wrkgrp" not "/(space)wrkgrp"
 
Bill said:
Joan,

The full path to Access did it, along with clearing another glitch.
It is "/wrkgrp" not "/(space)wrkgrp"
Click to expand...

That's right; without the full path to Access, the switch is ignored (and
your default system.mdw workgroup is used).

My sample didn't have a space in it, but glad you got it working.
 
Back
Top