mdw confusions

[Stinky Pete]

Hi all,

I've dragged a corporate db into the realities of new operating
processes, however I've come unstuck with the mdw file etc.

When it was on my local drive, the security etc was working well, so I
copied the file to the sever, renamed it and updated the paths in the
mdw file. Access to the file for me is still OK, however when other
users try to log in, the mdw file reckons the paths are not valid.
I've only used the full network paths in the mdw file to counter people
not calling drives by the same letter. This is the first time I have
upated security for a file, so even after reading the microsoft
security file, I'm still a tad confused as to why this is happening.

Thanx in advance,
Stinky Pete.

[Rick Brandt]

"Stinky Pete" <Pe**********@symbionhealth.comwrote in message
news:11*********************@79g2000cws.googlegrou ps.com...

Hi all,

I've dragged a corporate db into the realities of new operating
processes, however I've come unstuck with the mdw file etc.

When it was on my local drive, the security etc was working well, so I
copied the file to the sever, renamed it and updated the paths in the
mdw file. Access to the file for me is still OK, however when other
users try to log in, the mdw file reckons the paths are not valid.
I've only used the full network paths in the mdw file to counter people
not calling drives by the same letter. This is the first time I have
upated security for a file, so even after reading the microsoft
security file, I'm still a tad confused as to why this is happening.

Exactly what "paths" do you think exist in an MDW file? The MDW only contains
account and group information. There are no links to MDB files within and
therefore no paths.

If you are expecting others to use your MDW as their default workgroup file (not
recommended) then that is a setting that has to be changed on each and every
user's PC. Better is to provide them with shortcuts that specify the location
of the MDW file to be used.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Stinky Pete]

Hi Rick,

Thanx for the comments. No, I'm not allowing the others to use the mdw
file other than via a shortcut. Turns out the that shortcut that had
the msaccess file path, then the network file path and then the
workgroup file, had the incorrect network file path.

In short, your comments have helped and the issue is now all good.

Stinky Pete;-)

Rick Brandt wrote:

"Stinky Pete" <Pe**********@symbionhealth.comwrote in message
news:11*********************@79g2000cws.googlegrou ps.com...

Hi all,

I've dragged a corporate db into the realities of new operating
processes, however I've come unstuck with the mdw file etc.

When it was on my local drive, the security etc was working well, so I
copied the file to the sever, renamed it and updated the paths in the
mdw file. Access to the file for me is still OK, however when other
users try to log in, the mdw file reckons the paths are not valid.
I've only used the full network paths in the mdw file to counter people
not calling drives by the same letter. This is the first time I have
upated security for a file, so even after reading the microsoft
security file, I'm still a tad confused as to why this is happening.

Exactly what "paths" do you think exist in an MDW file? The MDW only contains
account and group information. There are no links to MDB files within and
therefore no paths.

If you are expecting others to use your MDW as their default workgroup file (not
recommended) then that is a setting that has to be changed on each and every
user's PC. Better is to provide them with shortcuts that specify the location
of the MDW file to be used.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com