I am writing a new program which could use a number of screens depending on the user. I do not want to create all these screens unless they are needed. Therefore I would like to know how to define screens. I believe I could have a database containing screen numbers and a "do while !eof" statement to create these screens. On the other hand has someone a better idea????? THANKS
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Mulitiple Screens Configurable
- Thread starter bebbo
- Start date
This certainly depends on how you start these screens. If your users start a screen by choosing a menu option, you could disable (or not even show) a menu options for users who are not authorised to do so.
Restrictions are to my opinion best done at menu option level than on screen level (especially if you want to restrict users from editing/appending etc.).
I have seen applications where you can restrict someone from editing on a screen where editing wasn't even possible.
But if your application start several screens at the start depending on the user, numbering them would be a good idea.
Just add a custom property that stores this unique number.
If your are using a users table, you could add the numbers to a memo field (you would have to convert them to characters, of course (if the number is not a character))). If the corresponding number of the form is not in the memo field of the specific user, it should not be started.
As you can read, there are a gazillion ways to implement restrictions...
HTH,
Weedz (Wietze Veld)
veld4663@exact.nl
They cling emotionally to code and fix development rather than choosing practices based on analytical assesments of what works best.
After the GoldRush - Steve McConnell
Restrictions are to my opinion best done at menu option level than on screen level (especially if you want to restrict users from editing/appending etc.).
I have seen applications where you can restrict someone from editing on a screen where editing wasn't even possible.
But if your application start several screens at the start depending on the user, numbering them would be a good idea.
Just add a custom property that stores this unique number.
If your are using a users table, you could add the numbers to a memo field (you would have to convert them to characters, of course (if the number is not a character))). If the corresponding number of the form is not in the memo field of the specific user, it should not be started.
As you can read, there are a gazillion ways to implement restrictions...
HTH,
Weedz (Wietze Veld)
veld4663@exact.nl
They cling emotionally to code and fix development rather than choosing practices based on analytical assesments of what works best.
After the GoldRush - Steve McConnell
- Status
Similar threads
- Locked
- Question