Another MDW file question

[Thooom]

OK, I'm very familiar with using a shortcut to open a db and "point" Access to a particular MDW (workgroup) file for userids/passwords. I feel that's the _only_ way to set up a networked/multi-user database. Otherwise, a user can get his/her own system.mdw file involved (via "joining" the workgroup)....make changes to that.....and one day loses the link between the original MDW and the database. So, my question is:

Is there any way for an Access app (mdb/mde) to override the command-line path to the security (mdw) file? I ask because I'm troubleshooting some username/password problems at work, and to be _certain_ I'm using the correct workgroup file I'm starting with a shortcut, pointed directly to an MDW file on a network share.

The thing is, if I open the db with that shortcut....and open up the security file info once I'm in the db (Tools | Security | Workgroup Administrator...), it lists a DIFFERENT mdw file than the one that I scripted in the shortcut's properties! Is this possible (for an app to be "hard coded" to a particular location)? Does anyone know what else may be causing my loss of control over which MDW file gets referenced? Thanks.

Oh, I'm using Access 2002 in XP.


Thooom

 

[statsman]

Will it allow you to sign in and does it work once you do?

It may be that the .mdw was changed in the FE but never uploaded into the back end.

If it works as is, just rename the current .mdw to the name in the shortcut.

If it doesn't, you may have to create a new .mdw.

 

[Thooom]

Will it allow you to sign in and does it work once you do?

It may be that the .mdw was changed in the FE but never uploaded into the back end.

If it works as is, just rename the current .mdw to the name in the shortcut.

If it doesn't, you may have to create a new .mdw.

Well, it works, but what I don't understand is why Access lists a different MDW as its current MDW. If you go to Tools | Security | Workgroup Administrator, isn't the MDW file displayed the one Access is currently using? Or is it simply the Registry setting Access has stored showing the _default_ MDW (used if none is specified with a shortcut)?

Basically, I need to be able to open up a remote location's mdb file (preferably by opening it directly by double-clicking) and have that mdb file use its "own" MDW file (the MDW file the remote users use). I need to be able to open up the remote database in order to fix some table data, but I need access to their currently active users/accounts.

When I tried this before (I used a shortcut to specify the _remote_ mdb's path and the _remote_ mdw's path), I didn't see the remote users listed when I opened up Tools | Security | User and Group Accounts. I don't see how this is possible. It's as though the database is "overriding" the shortcut's paramters. Am I making sense yet?


Thooom

 

[jclu]

What's the command line statement you're passing in the shorcut? Maybe if you list it here, it might help. Also, when you double-click the shortcut and the mdb is open, and you go to Tools | Security, does it show you which mdw file is being used? We have a similiar thing at my work, and the mdb and mdw file the shortcut is referencing are both stored in the same network folder, and the mdb seems to be using the correct mdw file.

 

[statsman]

I had a similar problem with Access once, but not with an MDW. I copied a table which basicly had the data I wanted, but needed a little tweaking. We'll call the original table TableA.
I renamed the new table TableB.
When doing queries or whatever they wouldn't work. I went back into the code and even though I had renamed the new table TableB, everything was still set to "Copy of TableA".
Could somthing like this have happened? Was the name of the mdw changed but the change didn't take?
I'm just thinking out loud here.