system.mdw - File on Server

[Greg]

Hopefully an easy one for someone out there...

I have an accounting program that I built in Access 97. I have the
data file on our server and the application (as well as the MDW file)
on each of the work stations. I would like is to be able to use the
same MDW file (placed on the server) for all of the machines so when I
am making changes to the MDW file I only have to make the changes once.
I though that this would be an easy task by runing the Join Workgroup
program and linking everyone to the same file... I tried this and they
all run fine but the changes are only evident on the work station that
I made the changes on... the other computers seem to still be using the
old version. I thought that if the software was closed and re-opened
then it would "see" my changes but it didn't work. I also tried only
making changes when no one other then my machine was opened when I made
the changed... this didn't make a difference either... Any ideas would
be greatly appreciated.

Thanks,
Greg

 

[Albert D. Kallal]

You are on the right track, and on the right idea.....

As a general rule, I always shared the mdw file on the server, and obviously
changing passwords, adding new users, or changing permissions would not work
if each user has a copy.

Joining the workgroup file on the server *should* work, but then again, I
have seen users change this!!!

What you need to do is provide a shortcut to launch your application, and in
that shortcut *includes* the workgroup file.

There has several benefits

* you don"t need to join a workgroup, and thus each time a user launches
other ms-access applications, they don't get a annoying logon prompt (why
force them to logon for every other mdb/mde they use besides yours??).

* Anyone who uses a notebook, or detached computer can still use other
mdb files. You *really* do not want the default workgroup file pointing to
the network share, since they will be attaching to the workgroup file
anytime they launch ms-access....even when NOT using your application.

* any other software on the computer that needs its own workgroup file
will NOT be effected because you now use a shortcut, and NOT have to go
around to each machine and join the workgroup file. I find the default
setting seems to get changed, or comes undone by messy users. I never really
did figure out why it never stuck to my workgroup file, but with a shortcut,
I don't care, don't worry, and don't have to change it on any machine.....

So, provide a shortcut to launch your appcation.

Typical shortcuts look like:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"
"c:\program files\RidesXP\RidesXP.mdb"
/wrkgrp "c:\Program Files\RidesXP\Rides.mdw"
/User "RidesAdmin" /pwd "password"

The above shortcut is of course on one line. And, the above includes a user
+ password (I use this for my development machine, as I HATE having to type
in the user name over and over -- but, as a normal practice, you would not
include the /user and /pwd to the shortcut....

Also, the above path name is quite different for 97 msaccess.exe, so, check
your machines (I think it is c:\program files\office\msaccess.exe)

I actually now use "inno" to install/update the mde to my users, and my
scripts also provide a desktop shortcut. My installs (or updates) now look
like:

http://www.kallal.ca/ridestutorialp/upgrade.html

You can find the inno installer here (it is free)
http://innosetup.org/isinfo.php

My inno installs actually pluck out the registry location of
msaccess.exe....so, if the user has a non default install of access, they
still work...

 

[Greg]

Hi Albert,

Thanks for your help... unfortunately I seem to still be having the
same issue as when I moved my workgroup file to the server and joined
multiple computers to it. I modified my shortcut as required on 2
computers. I logged in on one computer and added a new user to it. I
then logged in on the other computer and checked the user listing and
it didn't contain the user that I added. Back on the 1st computer it
was there... any ideas?

Thanks again for your help,
Greg

 

[Greg]

My bad... I should have removed my old short cut off my desktop as it
was the one I used thinking it was the new one. The actual "new"
shortcut I made works as explained. Thanks again for your help.