In the WC, when you have a solution with logon required and you use your own login form, the user is first presented with Servoy’s login, then your custom login form. As far as I can see, Servoy’s login form doens’t actually log in the user in this case.
In both the WC and the SC: when a user has logged in and then closes his solution and tries to open a solution again which requires login, the security.login will fail, because he is still logged in.
Programatically working around this by checking if allready logged in has the undersired sideeffect that you’re thrown out of the solution you try to open and are presented with the solution open dialog again and the other option (not loggin in when allready logged in) also won’t work, because you will not get passed the login form.
So, in short: When the user is allready logged in: Can the custom login form be skipped and can Servoys login form be skipped if a custom login form is setup in the WebClient?
Paul