implementing security....late

  • Thread starter Thread starter sc
  • Start date Start date
S

sc

I have a FE/BE Access2K database that I already
distributed without any security other than not showing
the database window at startup. This database will soon be
replaced by SQL server so I'm not going to make any
changes now. But, I have to develop a couple more
databases and need to have more security on them. I have
never created workgroups etc so am I going to "break" my
other application if I start to implement security now?
The recommended help sites are so full of ominous
warnings, I'm afraid to begin. Help!
 
You will not break anything provided your new databases are secured
using a customized workgroup file -- do not use the default workgroup
file. When done properly, a secured application is launched with a
shortcut that references the workgroup file to be used for that
specific Access session. All others continue to use the default,
unsecured workgroup file.



I have a FE/BE Access2K database that I already
distributed without any security other than not showing
the database window at startup. This database will soon be
replaced by SQL server so I'm not going to make any
changes now. But, I have to develop a couple more
databases and need to have more security on them. I have
never created workgroups etc so am I going to "break" my
other application if I start to implement security now?
The recommended help sites are so full of ominous
warnings, I'm afraid to begin. Help!
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
I have always copied the FE of my db to the users desktop.
For your suggestion, does the FE have to remain on the
network to be referenced correctly/simply? Pardon my
ignorance but I'm still really fuzzy on deploying security.
 
No - the FE *should* be copied to the local hard drive. The BE (shared
among several users) is on the network share. Applying security to the
BE is the most important, otherwise the users can simply open the BE
directly and bypass any security that you applied to the FE.

I have always copied the FE of my db to the users desktop.
For your suggestion, does the FE have to remain on the
network to be referenced correctly/simply? Pardon my
ignorance but I'm still really fuzzy on deploying security.
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Back
Top