|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
startup propertiesI want to prevent others from changing the startup properties using VBA in
another access file. I don't use User level security because I am not in a position to prevent either the database file being copied onto another machine or a workgroup file from being over written. In either of these cases I find the owner becomes unknown. There is a password on the VBA code. S wrote:
> I want to prevent others from changing the startup properties using That is only possible if you implement User Level Security.> VBA in another access file. > I don't use User level security because I Copying a properly secured MDB/MDE wold accomplish nothing for the copier unless > am not in a position to prevent either the database file being copied > onto another machine or a workgroup file from being over written. In > either of these cases I find the owner becomes unknown. There is a > password on the VBA code. they also copied the MDW. Copying the MDW would accomplish nothing if they didn't know at least one valid set of login credentials and those would have to be for someone with Administer permissions if they wanted to change the BypassKey property (assuming you set it with the ULS sensitive method). If you open a file and see Owner = "Unknown" then you must have opened it with a different MDW file than the one that was used to secure it. In most cases this would be impossible if the file were secured properly. Your reasons for not wanting to use User Level Security appear to be based on experiences where it was not implemented correctly. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com Your probably right about that. Thanks for your response it was very helpful.
S Show quoteHide quote "Rick Brandt" wrote: > S wrote: > > I want to prevent others from changing the startup properties using > > VBA in another access file. > > That is only possible if you implement User Level Security. > > > I don't use User level security because I > > am not in a position to prevent either the database file being copied > > onto another machine or a workgroup file from being over written. In > > either of these cases I find the owner becomes unknown. There is a > > password on the VBA code. > > Copying a properly secured MDB/MDE wold accomplish nothing for the copier unless > they also copied the MDW. Copying the MDW would accomplish nothing if they > didn't know at least one valid set of login credentials and those would have to > be for someone with Administer permissions if they wanted to change the > BypassKey property (assuming you set it with the ULS sensitive method). > > If you open a file and see Owner = "Unknown" then you must have opened it with a > different MDW file than the one that was used to secure it. In most cases this > would be impossible if the file were secured properly. > > Your reasons for not wanting to use User Level Security appear to be based on > experiences where it was not implemented correctly. > > -- > Rick Brandt, Microsoft Access MVP > Email (as appropriate) to... > RBrandt at Hunter dot com > > > > > What if the system.mdw is replace with the copy iAccess is shiped with and
any shortcut to a different workgroup file is deleted. So it would open with the default? Show quoteHide quote "Rick Brandt" wrote: > S wrote: > > I want to prevent others from changing the startup properties using > > VBA in another access file. > > That is only possible if you implement User Level Security. > > > I don't use User level security because I > > am not in a position to prevent either the database file being copied > > onto another machine or a workgroup file from being over written. In > > either of these cases I find the owner becomes unknown. There is a > > password on the VBA code. > > Copying a properly secured MDB/MDE wold accomplish nothing for the copier unless > they also copied the MDW. Copying the MDW would accomplish nothing if they > didn't know at least one valid set of login credentials and those would have to > be for someone with Administer permissions if they wanted to change the > BypassKey property (assuming you set it with the ULS sensitive method). > > If you open a file and see Owner = "Unknown" then you must have opened it with a > different MDW file than the one that was used to secure it. In most cases this > would be impossible if the file were secured properly. > > Your reasons for not wanting to use User Level Security appear to be based on > experiences where it was not implemented correctly. > > -- > Rick Brandt, Microsoft Access MVP > Email (as appropriate) to... > RBrandt at Hunter dot com > > > > > S wrote:
> What if the system.mdw is replace with the copy iAccess is shiped No. If it were secured *properly* you would not be able to open it unless you > with and any shortcut to a different workgroup file is deleted. So it > would open with the default? used the exact MDW fiel that was used to secure it. Any time you open an Access file with a workgroup file that doesn't require a login, then you MUST be opening it as the default user "Admin" with credentials of the default workgroup "Users". In a properly secured file neither of those entities should have enough authority to open the file so you should just get a permissions denied error. (most Access files that people think are secured are not) -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com 
Other interesting topics
Security NOT using "mdw" file
Security MDW deployment? Securing the Back-End Shorcut with pointing to two ACCESS.EXE from mdb how to openForm a form in a referenced mde file Prevent all Access files from connecting to the same Workgroup? User permissions validation text Locked Out, what did I do? How can I lock based on certain field? |
|||||||||||||||||||||||
