Geoff: I ask, if you use the data access class in login, because once you start classes for one aspect, in the normal case you would also do so for other things, like internationalisation, you start developing an OOP framework quite automatically, if you do things consitently.
You seem to focus a lot on the aspect of reusability. There are many aspects of OOP and focusing on just one of them you don't get the grip.
Mike,
In regard how to skip the login during development and testing:
a) I actually can initialise the framework (in short a goApp object) without starting the app, so the framework initialisation is seperated.
b) If testing the app GUI, I actuall can display the login and just make the passwort optional, that is I can choose or enter the user I want to be and test with his/her application permissions without knowing or entering the password.
c) I can switch in a mode the Windows Account name specifies my application account, as the applilcation user data is relating to the windows account name. In that modeI autologin as me.
Actually being able to test single aspects and modules and classes in the non GUI mode is saving more time than avoiding the login dialog. Often enough some form you want to test is not directly available, so you'd need several steps in the gUI to get where you want to test. That is contraproductive.
Bye, Olaf.