Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

My Security still doesn't work From Server

Status
Not open for further replies.

erwin001

IS-IT--Management
Mar 28, 2006
51
US
I'm attempting to secure my database on a company server. I have set up the security using Tools/Workgroup Administrator, however from my PC the security seems to be in place. When I access it from a different pc, no logons are requested. The database just opens. I set the security.mdw file from my PC. When I open the database from a different PC, the security.mdw is set to the local user. I even set up a password for the default Admin user. But no luck. I have followed a number of post, but to no avail. I feel as if I'm following the steps correctly. Does anyone have any ideas?
 
You need to create a shortcut to the database and in the target of the shorcut, after the database path type /wrkgrp "path to mdw file" - Of course all users must have rights to database and security file. Then direct the users to open the database using the shorcut. I have placed my shorcut in a different location so that my users are not tempted to open the actual database file instead of using the shortcut, just make sure the shorcut finds all the necessary files.
 
I created a short cut by right clicking on the database file that I'm attempting to secure. After creating the short cut I right clicked on the shortcut. The Shortcut to WMS_MAIN_MENU.mdb Properties window opens. Currently in the Target window is "D:\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\WMS_MAIN_MENU.mdb\

The Security.mdw file is contained in the same folder. I understand that this file could be named anything, database.mdw for example. Therefore, if I'm understanding your solution, I should add Security.mdw to the end of the current target. For example,

"D:\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\WMS_MAIN_MENU.mdb\Security.mdw

The above path represents the shortcut. Each user attempting to acces my database should have access to the shortcut only. This should solve my problem? Is this correct?



 
Should it look like this?

"D:\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\WMS_MAIN_MENU.mdb/wrkgrp D:\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\wmsReportSystem.mdw"
 
Given D is your network drive and all users have D mapped to the same thing, then the shortcut should look like this:

"D:\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\WMS_MAIN_MENU.mdb" /wrkgrp "D:\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\wmsReportSystem.mdw"

Every user needs to access the database from the same path. They will still need rights to the mdb file in order to open it, which is why I placed mine in a seperate folder from the shortcut.

 
It depends on how a person hits the server. The drive letter may be different for each user. This could be my problem. If D:\ is the network drive for my PC, it's possible that A:\ could be the network drive another user, or G:\ for another. However, each person hits the same network server. What do you think? I know how to map the drive without using a drive letter.
 
A UNC works in my environment, go ahead and give it a try - I was unintentionally misleading on my last post. The Target of the shortcut needs to start by pointing at the msaccess executable - Example:

"C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" "\\server\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\WMS_MAIN_MENU.mdb" /wrkgrp "\\server\Documents and Settings\teanderson\Desktop\WMS DATABASE REPORT REPOSITORY7april2006\WMS_MAIN_MENU.mdw"

I know that you will run out of space at one point in the Target field, but I am unsure as to what the limitation is.
 
The following path is how I set my target's shortcut.

Code:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "\\log-lake-fp1\shared\ENGINEERING SERVICES\TSG and Reporting\WMS Security\WMS_MAIN_MENU.mdb" /wrkgrp "\\log-lake-fp1\shared\ENGINEERING SERVICES\TSG and Reporting\WMS Security\wmsReportSystem.mdw"

It works fine from my pc. I however have two problems. In the properties window of the shortcut, there is a start in path listed. The path set is as follows:

Code:
"A:\Functional User Group\Report Repository Database\WMS DATABASE REPORT REPOSITORY12april2006"

A:\ is the network drive. However, each user may have a different network drive letter naming convention for it's start in path. When I attempt to access the shortcut from a different PC the shortcut doesn't look like an access shortcut icon, and when I double click on the icon, I get an error message.

Another problem is that my "PathToAccess" is

Code:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"

I'm running Windows XP. Other user's "PathToAccess" may be

Code:
"C:\Program Files\Microsoft Office\OFFICE10\MSACCESS.EXE"

Does anyone have any ideas? I'm very close to getting access security to work.
 
Thanks for all of your help. The shortcut works fine! I need to get the different paths "PathToAccess" "PathToDatabase" /wrkgrp "PathToWorkgrooup" correct.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top