Of course you can model a user authentication dialog which opens when the native application starts (or based on other runtime parameters), accepts a username and password entered by the user and sends them to the server for verification, then based on the servers response decide whether to display or hide certain (or all) parts of the gui (as I suggested in my previous answer). The only thing here is that it cannot be automatic, and based on the user-role-permission mechanism.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
