Corrupt MDW - About Had It :mad:

[SteelersFan]

You should never join a PC to a workgroup. Using custom shortcuts like I mentioned above enables the user to login to the db with the right workgroup.mdw file. Joining a PC to a workgroup would force the user to log into each db, even to create a brand new mdb file.

This is just a temporary fix. I am going to create the shortcuts to their databases and set the file to the mdw file in the system32 folder when I get a chance.

Thanks for the help.

 

[KenHigg]

How so? That only tells them the user name. They still need the password to log in. Those that do log in only know the password for their workgroup name. But, if somebody gets cute and learns of another groups ID and password and logs in with an ID and password that for a group that they do not belong to then the db user log will show who the user is, which PC they used and which group they logged in as. [bad sentence structure]

Hum...

If the check is a user log, why even screw with a .mdw. Just seems the whole security schema has been bastardized. But, like I said, if you're happy with it, rock 'n roll...

(Speaking of R&R - American Graffiti was on last night. Cool flick...)

Ken

 

[KenHigg]

...You should never join a PC to a workgroup.

Never is a big word. I could give you some examples where it would perfectly acceptable, but I'll spare everyone...


Ken