Shortcut needs to work in a Domain instead of a workgroup

[Cathyann10]

This is a path for the desktop icon for our timekeeper access database. We
use this all day long and it works great! However we are in the process of
setting up a Windows Server 2003 and it will be a Domain and not a workgroup
environment. I tried to change the "WRKGRP" to Domain but that don't work...
Can anyone tell me how to make this Icon work?

"C:\Program Files\Microsoft Office 2007\Office12\MSACCESS.EXE" "C:\Documents
and Settings\Administrator\My Documents\Time Clock\Time Keeping 0.0.mdb"
/WRKGRP "C:\Documents and Settings\Administrator\My Documents\Time
Clock\Secured.mdw"

The icon does 3 things:
1st it points to Access 2007
2nd it points to the actual "Timekeeper" Database
3rd is the security file

Thank you for any help you can offer me!!

Cathyann10

 

[Douglas J. Steele]

There's nothing about that shortcut that should require change.

What happens when you try using it?

 

[Cathyann10]

When I click on the Icon a message pops up from Access and says "Record(s)
can not be read; no read permission on "Volunteers'." Could it be the
permissions for the foler on the server?
Just a little more info... we are 1/2 done with installing and changing all
7 computers to the new domain. The shortcut works on the computers that are
still set up as a workgroup but the ones that are set up on the Domain will
no longer access the timekeeper with that Icon. The file is in the same place
(file and path) other than the domain
Even though the shortcut says workgroup will it still work in a Domain?

Thank you!
Cathyann10

 

[Douglas J. Steele]

The "WRKGRP" in this case is an Access term, not a network term. It's how
Access refers to the system database (the MDW file) that contains the user
information. It has nothing to do with whether you're using a workgroup or
domain network.

The inability to read data would imply that the users don't have the
necessary permissions. They require a minimum of Read, Write and Create on
the folder where the mdb resides. It's usual to give them delete on the
folder as well, but's it's not actually necessary. If you don't give them
delete, the locking file (the LDB file) won't get deleted when the last user
exits the database, which will lead to problems when you want to compact the
database.

Incidentally, it would probably make more sense to have the MDW file on the
server as well as the back-end database.