Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Security implementation
Message
From
13/01/1997 04:29:18
 
 
To
07/01/1997 22:17:53
John Adams
John T. Adams Software Consulting Svcs
Keedysville, Maryland, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00016369
Message ID:
00017159
Views:
65
>One thing you may consider is categorizing you fields, and creating a subclass for each category, then you could issue a setall for the classes that the user can access/can't access. This would speed up the refresh if the overhead proves too high.

Nice idea, I'll try that later, for now it all works and with minimal overhead.

Since I have a SecurityEnabled property I can bracked the code with IF... and not have the overhead for controls with a security level of 0.


The big problem was where users had defined security for page3 of a pageframe different to pages 1 and 2
Complicated by my design to put the VCR and Add/Save/Undo controls on the FORM instead of 3 copies one for each page.

I added a UIEnabler object, that in its UIEnable would refresh the current page (because non-current pages don't get refreshed) and would check its security level and use that to enable/disable the ASU edit control.

Worked just fine.


>Good Luck.

Thanks, I made my own luck by asking here and on CompuServe.
Just beacuse I'm a SYSOP on CIS doesn't mean I know everything, wish I did <g>
Previous
Reply
Map
View

Click here to load this message in the networking platform