Maybe you're right, I will try to study the class libraries. I already have done quite a bit of coding to enable/disable the buttons (and finished with it at this point), and then now I top of that, I need to security over that.

Chuck

>Well. There are different ways you can do it. Of cause also depending what level of security you wish? From forms to field level.
>
> I would suggest you design your levels and put it all into tables.
>
> Then for instance in the Init event of the controls you can place your code to either enable, disable or make invisible as needed out from cross-reference with for example the control source and yoru designed security levels based on user.
>
> But get used to VFP class libraries first.
>
>

---

>Excuse me for my limited knowledge with VFP class library, but would something like a PROCEDURE be the way to do it? The way I did it in ol' days was type the long coding of security in a PRG and then have the program go back and forth (man, it's was so long that I even touch any security, since all my work here for 4 years was fully open access, and now this one needs the security). It's gonna take a while to refresh my memory (sigh).
>

---

>
>HTH,