Thank you very much for the answers!
UsingTFrame was one of the options at the beginning of the project ... Maybe I didn't make a good decision... anyway... I want to implement a desktop project whose behavior is similar to a "web application".
I plan to use a main Form as a kind of base where I intend to present all the other forms with the other features of the system.
The first feature I want to introduce is a login interface. For this I implemented a simple structure that has the form frmLogin as a view.
My proposal is to present this login form inside the main form (I do not want the Login form to be presented before the Main Form) ... then, allow the user to proceed with the login and then immediately, if the login was successful, present another form, which I called "Home", and which contains a dashboard with synthetic data from the system on cards (panels) which, in turn, will function as a main menu for the other functionalities and their respective views.
The main form would function as a kind of simple browser that will allow the user to go back and forth between the forms he is opening. The general appearence would be similar to that of the gnome Nautilus.
I am stuck in this initial process, which is to define an appropriate place to present the Login Form and then present the Home Form, these two presentations would be automatic, independent of the user's action.
I already tried to use DoShow / OnShow from the main form to present the Login form and then I extended the Notification procedure (from the main form) to detect that frmLogin has been removed and thus start frmHome. But, the problem with this implementation is that I have to use frmLogin.Show in frmMain.OnShow ... but, with my level of knowledge, this complicates the control over the creation and destruction of objects associated with Login and Home .
Apologies for the text size