Security files

[Freehal04]

So I have my seured db set up and I have my default mdw. file set in Access.
I created a short cut for the user to use. But when they click on the
shortcut and Access opens, I'm told that the user doesn't have the right
permissions. What's the deal with that?

 

[Joan Wild]

The shortcut target could have something amiss, or you didn't give that user Open permission on the database object.

The target needs to include"
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"

 

[Freehal04]

How do I give a user Open permission the the db object?

 

[Joan Wild]

Actually you should grant permissions on Groups, rather than Users. Tools, Security, Permissions...
In the object drop-down list choose 'Database'
Select the 'Groups' Option
Choose the Group you want to assign permission to
Check 'Open' in the permissions list and then Apply.

I have a feeling though, that you shortcut is the real problem. If you find that the Open permission is already set, post the contents of the target of your shortcut.

 

[Freehal04]

Here's the target for my shortcut. I just put it on the c drive so I
wouldn't have to look all over for it. C:\CDRL123.mdb

 

[Joan Wild]

The target needs to include both the path to msaccess.exe and the wrkgrp switch.

It is working for you as is, because you are joined by default to your secure mdw. However it won't work for your users as they are likely joined to the system.mdw that ships with Access. You should rejoin the system.mdw as your default.

Modify your shortcut target to
"path to msaccess.exe" "c:\CDRL123.mdb" /wrkgrp "path to secure mdw"
Substitute the appropriate pathnames.

 

[Freehal04]

Okay, I think I understand the concept, but if I write a path the ms
Access.exe, won't that direct the user to my exe on my cpu not on theirs?
The db is eventually going on a share drive, so that little bit confuses me.
The secure mdw is going to be on a shared drive as well, or is that not a
good thing?

 

[Joan Wild]

The path to msaccess.exe should be the path to that file on their computer.
c:\Program Files\Microsoft Office\Office\msaccess.exe (or similar) - that would be on their hard drive.
The secure mdw should be on a shared drive. I would put it there now. The "path to secure mdw" can be a UNC pathname i.e.
\\servername\share\path\whatever.mdw That way you don't need to worry whether users have the same drive mappings.

The mdb should be split into frontend/backend. The backend would be put on the shared drive. A copy of the frontend would be put on each user's computer.

Split it manually - don't use the splitter wizard. See www.jmwild.com/SplitSecure.htm When you establish the links to the tables in the backend, use My Network Places and navigate to the location of the backend (this will use the UNC pathname).

In the shortcut target the "path to mdb" would be the path to the frontend on each user's computer.