Easy distribution of .mdw file

[Gareau, Dany]

I have a secured database (with user level security) witch need to be
deployed across many location. Obviously I need to supply the .mdw too for
the db to be usable. Overwriting the local system.mdw is a bad idea, since
other db will be affected too. I understand that I need to supply the
correct shortcut in the form:
"full path to msaccess.exe" "path to mdb or mde" /wrkgrp "path to mdw" (tnx
Joan Wild)

However, the path to msaccess and path to the db may vary from one user to
other. Is there a simple way to do this ? Ideally the users will just drop
the .mdb, .mdw and shortcut in one place, and voila: copy, click on the
link and there you go. Alas, I suspect this utopian solution will not work
and the shorcut will need to be edited for each user. I there a way to do
this automatically ? Or somehow integrate the .mdw and db in one file ?

 

[Rick B]

First, you should not be overwriting the SYSTEM.MDW, you should have created
a new MDW named something different. ( I use secure.mdw).

Secondly, you would typically not give each person the mdw. You would
maintain it in one central location. If someone needs to gain more access,
you wnat to be able to do it in the mdw file that you are using (and that
they are using). IF that is not practical because they are in different
phisical locations, then I would think you would still have one copy of the
mdw working on their LAN and shared by all the users in that office.
Someone there should be in charge of maintaining it. If each user is on
their own out in the field, then you may indeed need to send them an mdw
file. (I'd still not replace the deafault SYSTEM.MDW)

Rick B

 

[Gareau, Dany]

Hi Rick,
I understand that overwriting system.mdw is not the solution. There is no
LAN avaiable for some of my users; so I must supply them a copy of the .mdw
file (no other choice here). They are indeed "out in the field" (in hunting
and fishing reserves to be precise), and unfortunatly there is no system
administrator there. So the installation procedure must be very simple. I
still need a way to generate that shortcut based on where access is
installed on their system and where the .mdb and .mdw are placed. Thanks for
your input anyway!

 

[TC]

But that doesn't solve the problem of how the shortcut knows the path
to msaccess.exe. The OP is asking how to write the shortcut without
having a fixed path for msaccess and the database.

OP, this topic was covered here within the last month. Google for posts
containing the word "createobject" in that perid, in this newsgroup.

HTH,
TC

 

[david epsom dot com dot au]

One alternative is to use a short executable stub program (or even
a special Access Application) to load your database. The executable
locates Access (finding the correct version), and starts Access
using your command line. The program can be as complex as necessary
to find your application and your workgroup, before starting Access
with your application using your command line.

Another alternative is to use the /profile switch instead of the
/workgrp switch. The /profile refers to a profile stored in the
registry having all the normal Access registry entries, including
the Jet configuration, the workgroup location, loaded add-ins,
library location etc. A profile name can be the same on all
workstations: you just have to adjust the registry entry to point
to the correct workgroup file.

A third alternative is to just use the Admin login with the
standard workgroup file - but put the application file under
the users My Documents folder. Only that user (or administrators)
will be able to see inside the My Documents folder, so only
that user will have access to the database file.


(david)

 

[Gerald Wolf]

Why don't you use an installation program like Wise or SMS which are able
to create links while running the setup?

/Gerald