Permissions

  • Thread starter Thread starter Leslie Isaacs
  • Start date Start date
L

Leslie Isaacs

Hello All

I have a secured A2K mdb, split with the BE (and the mdw file) on the
fileserver, and lots of FEs on various PCs. Until recently all the PC were
running W2k and A2k, but now we have 2 running Wxp and A2003. With the same
FE, and (virtually) the same shortcut to open the FEs (the difference is
just the path to msaccess.exe) on these two PCs as on all the others, I find
that most users, on the 2 new PCs, do not have permission to open the
startup form. It doesn't seem to matter how many time I set this permission
(for the entire group Users) on the 'master' FE, every time I copy the
master FE to either of the 2 new PCs I get the same permission problem.

I can't understand this because the shortcut to the FEs on the new PCs
points to the same mdw file as the shortcut on all the other PCs. The
problem seems to be something to do with the operating system, because it is
confined to the 2 PCs with Wxp.

Hope someone can help.

Many thanks
Leslie Isaacs
 
It is unlikely IMO that the permissions are being automagically changed
to something else.

Are you /certain/ you are using the exact same workgroup file in each
case? Temporarily modify the FE to display its name
(dbengine.systemdb), just to be sure.

HTH,
TC
 
Hello TC

Thanks for your reply.

The shortcut to open the FE on all the W2k PCs is:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\wkhc
database\telnumbers.mdb" /wrkgrp "\\clinical\public\secured.mdw"

The shortcut to open the FE on the two Wxp PCs is:
"C:\Program Files\MICROS~2\OFFICE11\MSACCESS.EXE" "C:\wkhc
database\telnumbers.mdb" /wrkgrp "\\clinical\public\secured.mdw"

I wasn't sure what you meant by "Temporarily modify the FE to display its
name (dbengine.systemdb)": this is obviously my ignorance, but what
exactly
should I do here?

Many thanks for your continued help.
Les.
 
Leslie said:
The shortcut to open the FE on all the W2k PCs is:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\wkhc
database\telnumbers.mdb" /wrkgrp "\\clinical\public\secured.mdw"

The shortcut to open the FE on the two Wxp PCs is:
"C:\Program Files\MICROS~2\OFFICE11\MSACCESS.EXE" "C:\wkhc
database\telnumbers.mdb" /wrkgrp "\\clinical\public\secured.mdw"
Click to expand...

Try changing that path to msaccess.exe to the full pathname i.e.
Micros~2 to Microsoft Office2 (or whatever it really is)
 
If you placed the following line of code somewhere in your startup
code, or attached to a button on a form, for example, it would display
the name of the workgroup file that Access is using at that point in
time:

msgbox dbengine.systemdb

This would serve to independently confirm that you were using the
workgroup file that you think you are using.

HTH,
TC
 
Thanks for that I have added a button to the form, with Leslie Isaacs
help,
but as I cannot access the form from the workstations that I want to check
the workgroup file for, this hasn't really helped. If you can suggest
where
else I can check for the workgroup file that would be great.
Thanks
Jane
 
Thanks for that, but unfortunately it hasn't helped because I added a
button
to the form as suggested (Les Isaacs talked me through this from home)
because I cannot access the form on the workstations that I want to check
the workgroup file for. Any further help would be much appreciated.
Thanks
Jane
 
Given the timing of your response, and your answer to other questions,
realize that you have to change the shortcut on the WinXP computers (which
you say you don't have access to at the moment)????
 
Sorry, I don't see how you can debug a problem on a remote PC, unless
there is someone there who can follow instructions - such as, to click
the new button & write down what appears in the message!

TC
 
Back
Top