Jack: When I read your post I shared a problem I had that took a while to figure out so that it might help lead to your solution. It sounds like it's not the same problem. Also, my situation only happened when I first started using a new framework and only when I ran the form in the IDE - because that is a nice feature of the framework. The errors I got were due to inexperience with the framework by putting code in the wrong methods. The restarting VFP helped me figure out what was happening and once I figured out what was causing it, it doesn't happen any more.
Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jack Skelley Sent: Tuesday, October 31, 2006 7:47 AM To: [EMAIL PROTECTED] Subject: Re: VFP8: Missing Code...Again... Jeff: Thanks to all that replied. So are we going backwards? There are more features in every release but the *simple stuff* is now causing issues. In the apps I write I have a startup.prg that is set as the main. So my form is always saved before it is run (and I have save form before run as well as a default for forms) and then I invoke the startup prg. For example, in this app, the startup .prg initializes cpptimer.fll, sets global variables, hides the screen, blah, blah, blah then it launches the main form. I have not seen the scrambled code you mention. Just missing code in the objcode with the method code mostly being intact. When I program I have lots of errors (and hopefully I find them before the user does)! I tell everyone that all my pencils have erasers and the erasures are well used. So to quit VFP on every error and the reload would be and unbelievable amount of time. So what are we overlooking? Regards, Jack Skelley Jeff Johnson wrote: > Jack: I've been using VFP9 and have had this happen quite a bit. I traced > it to this: When running a form in the VFP environment I get an error. If > I save the form, it will save some of the methods in the wrong place. Ie: > the init code will be in the click code and the click code will be in the > init. Initially I would save the form and have to go back and move > everything around. > > What I do now, is when I get an error when running a form, I quit FoxPro and > start it up. The form will be fine when re-opening FoxPro. > > It appears to me that the index of the form gets messed up when there is an > error. I have never seen this is VFP7 and I have it under control in VFP9. > > Jeff > > Jeff Johnson > [EMAIL PROTECTED] > 623-582-0323 > Fax 623-869-0675 [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
