>>Has anyone else run into a problem where, upon saving changes to a form, method code mysteriously gets swapped to other methods? For example, all of the code from the form's INIT method moves to the REFRESH method, and vice-versa. This happened to me before on a particular app I wrote in VFP5, and then it just happened to me again today on a completely different VFP 6 app. (I do have SP3 loaded.) I can't figure out what makes it happen, because it doesn't happen every time. When it happens though, it swaps code from several methods, but not all of them. It happens to object methods and form methods. The only thing similar about these two apps is that they both use a pageframe. Finally, I will add that in thinking it was related to my custom class library, I did some testing using only the VFP foundation classes, and the problem still happened.
>>
>>Any ideas?
>
>You're not losing your mind. I've had it happen before but never took the time to isolate the cause. Lately, I've been dealing with a bug in the class editor. If I'm editing (for example) a custom method of a subclassed line object, the editor window displays the name of my custom method in the "Procedure" dropdown when, in fact, Fox is writing the code under another method/event (usually the Click event). This becomes obvious when I take a look at the Window list under the Window menu pad. Flaky, eh?

PMFJI: I posted a question about two months ago on the same type of problem. I had an associate with dataenvironment swapping methods, and I had an optiongroup on a different screen form that kept getting trashed at about the same time. Both were flatfile forms, no pageframes, but had multiple tables in use for lookups, etc. The consensus at the time here (UT) was that the screen form table itself had become corrupted, and after rebuilding my screen from scratch I have had no further problems. Just packing it and/or appending from one scx to another used as tables was not good enough. For me it wasn't such a big deal at the time, as the forms were relatively simple, but if yours are really complex it could be a problem. Cut and paste between the 'bad' one and the 'good' one might make it less painful...

HTH

Rob