Contained controls init before the parent container. So if one of your controls is blowing up, there could be something in the framework that prevents the form from coming up. I've also seen this kind of behavior when there's a corrupted table or index.
-- rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Jeff Johnson Sent: Wednesday, January 23, 2013 2:00 PM To: profoxt...@leafe.com Subject: Form Not Initializing I have a Visual MaxFrame form in VFP9 doing something very strange. I took a working form and saved it as a different form and made the Name the new name of the form. This is something I do very often. The form loads (verified) and does not make it to the form.init (verified) and does not throw an error because I overrode the error routine to display the error. So my friend Lisa G. told me it must be in one of the controls. But why would it not throw an error? Can a control.init lock up a form? TIA -- Jeff _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04421819CDD6A@ACKBWDDQH1.artfact.local ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
