I tend to do all the login stuff in the project source, after creating the data module first, then the main form and the login form. If the login fails (however many times), don't call application.run.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Marshland Engineering Sent: Sunday, 24 June 2012 10:58 p.m. To: [email protected] Subject: [DUG] Chick or egg. I'm opening an MYSql file. I am reading data from a ini file to pre-populate the fLogin edit boxes. I can't open the SQL until I have logged in and the datamodule does not allow edit boxes. If I put the TMyConnection on a login page, the datamodule components can't find the tables, even if I add the fLogin to the uses list. If I put the TMyConnection on the DM page and the call fLogin with the on create, I get an access violation message. I assume it is because the DM has not fully created itself and the components. Any Suggestions ? One is having connection function left on the DM form but it references the parameters from fLogin. I guess having a window on the DM form would be the answer. Thanks Wallace. _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
