Workgroup file shortcut not working

  • Thread starter Thread starter rockinchris
  • Start date Start date
R

rockinchris

Guest
I'm using Access 2000 and Office 2000

I created an Access application that is linked to an Oracle read-only database that prints shipping labels. I created a workgroup file named "test.mdw" that is specifically for that application. I already checked the "test.mdw" file and it works properly. The Access application, "LabelTest.mdb" and the workgroup file, "test.mdw", were placed on the C Drive of my computer.

Then, I created a shortcut that is suppose to link the Access file to that particular workgroup file, so that it does not use the Access system workgroup file instead that all other Access files use. The shortcut target was entered as follows:
C:\LabelTest.mdb/ wrkgrp\test.mdw
Once I saved the target it became
C:\LabelTest.mdb wrkgrp\test.mdw

For some reason, the Access system workgroup file is overriding the test.mdw file, so the permissions I set up for that application are not working correctly. My main issue here is that I do not want users to be able to open up the linked tables and view/export the data. I do not believe that hiding the tables provides enough security since it can be easily switched.

Any Suggestions?
 
Proper syntax of the shortcut is

"x:\Msaccess.exe" "x:\LabelTest.mdb" /wrkgrp "x:\test.mdw"

Substitute x with your drive letter.
 
Oh, and sorry to inform you but you have not implemented security properly or you would not be able to get in at all. You need to read the Microsoft Security faq located here

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

Even if you do get the shortcut to work anyone will be able to get around it by not using the shortcut as you did.
 
Thanks...that worked.

The reason I was able to get into the application was because the default system workgroup file on my PC does not have any permissions. Therefore, the application opened fine because it was using my default file that has no security.

Once I move the application, app-specific workgroup file, and shortcut to our shared network drive, it will be different. There we have restricted folders and so forth. I'm just testing it out right now on my PC.
 
Your situation won't change just from moving it to the server. Someone who has permissions to the folder will be able to open the db without going through the shortcut and change anything they want to because the db will default to their system.mdw which also has no permissions.

You have to follow the directions in the security faqs concerning the removal of the Admin user from the Admins group and the removal of all permissions from the User group in order to properly protect the db. Once you have done this even if a person has permissions to be in the folder if they don't use the shortcut they will be locked out.
 
That sounds like a good idea and I'll probably start doing that now just to get in the habit of it. However, besides myself , only our IT administrators will have access to the restricted folder. The Access application links to 4 of about 370+ tables in our Warehouse Management System. The IT Admins already have access to all of the tables in our WMS.

Therefore, there's no concern with them. My main concern was with the facility workers in our warehouses being able to access the data. Thanks for your help.
 
As long as the folder is protected you should have no worry other than one of your counterparts deciding that they don't like your db design and changing it on you.
 
That's not a worry either...the tables are linked and read-only.
 

Users who are viewing this thread

Back
Top Bottom