Method code swapping in VFP8 SP1

VFP8 SP1 on XP Pro SP1

I've seen this reported in other versions of VFP, but not in
VFP8. After editing a form and running it, I got some odd errors.
I went back into the form and found that several methods had
their code swapped. The code from the Load and Init methods
had been swapped, the code from the Show and Unload methods
had been swapped. How's that for scary?

This form has about 40 custom methods added to it and only the
native methods that had code in them got swapped. The custom
methods were all fine.

In VFP's defense, at the time this happened, (but after the form
had been saved, compiled, and run) VFP crashed due to another
issue. I suspect these events are related since I've never
seen this code swap problem before this.

-- TRW
_______________________________________
t r w 7
at
i x dot n e t c o m dot c o m
_______________________________________

Leemi
Tue May 03 16:55:52 CDT 2005

Hi TRW:

No, I have not heard of this behavior before. I have heard of code being
lost after a C0000005 error but not method code being swapped.

I guess the only defense I an think of would be to save your form often.
You could always use source control as well. Maybe someone lese has a
better idea.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003

>VFP8 SP1 on XP Pro SP1

>I've seen this reported in other versions of VFP, but not in
>VFP8. After editing a form and running it, I got some odd errors.
>I went back into the form and found that several methods had
>their code swapped. The code from the Load and Init methods
>had been swapped, the code from the Show and Unload methods
>had been swapped. How's that for scary?

>This form has about 40 custom methods added to it and only the
>native methods that had code in them got swapped. The custom
>methods were all fine.

>In VFP's defense, at the time this happened, (but after the form
>had been saved, compiled, and run) VFP crashed due to another
>issue. I suspect these events are related since I've never
>seen this code swap problem before this.

>-- TRW
>_______________________________________
>t r w 7
>at
>i x dot n e t c o m dot c o m
>_______________________________________

Matthew
Tue May 03 20:55:14 CDT 2005

Hi Tim,

I had experienced this situation several years ago in VFP6 SP5. It is also
confirmed in a book which was written by Jim Booth & Steve Sawyer,
"Effective Techniques for Application Development with Visual FoxPro 6.0".
The authors suggest that open the form's .scx file as a table, REPLACE ALL
ObjCode WITH "", close the table, and then issue the VFP to recompile all of
the code in the Methods field.
I did not try this because I did not know this method at the time of the
problem. I just recovered from the backup files.

Matthew

"Tim Witort" <trw7at@ixdot.netcomdotcom> ¼¶¼g©ó¶l¥ó·s»D:Xns964B93ED4A49Ftimwitortwrotethis@207.217.125.201...
> VFP8 SP1 on XP Pro SP1
>
> I've seen this reported in other versions of VFP, but not in
> VFP8. After editing a form and running it, I got some odd errors.
> I went back into the form and found that several methods had
> their code swapped. The code from the Load and Init methods
> had been swapped, the code from the Show and Unload methods
> had been swapped. How's that for scary?
>
> This form has about 40 custom methods added to it and only the
> native methods that had code in them got swapped. The custom
> methods were all fine.
>
> In VFP's defense, at the time this happened, (but after the form
> had been saved, compiled, and run) VFP crashed due to another
> issue. I suspect these events are related since I've never
> seen this code swap problem before this.
>
> -- TRW
> _______________________________________
> t r w 7
> at
> i x dot n e t c o m dot c o m
> _______________________________________

trw7at
Wed May 04 10:31:21 CDT 2005

>>VFP8 SP1 on XP Pro SP1
>
>>I've seen this reported in other versions of VFP, but not in
>>VFP8. After editing a form and running it, I got some odd errors.
>>I went back into the form and found that several methods had
>>their code swapped. The code from the Load and Init methods
>>had been swapped, the code from the Show and Unload methods
>>had been swapped. How's that for scary?
>
>>This form has about 40 custom methods added to it and only the
>>native methods that had code in them got swapped. The custom methods
>>were all fine.
>
>>In VFP's defense, at the time this happened, (but after the form
>>had been saved, compiled, and run) VFP crashed due to another
>>issue. I suspect these events are related since I've never
>>seen this code swap problem before this.
>
Lee Mitchell seemed to utter in
news:iPJTtqCUFHA.2184@TK2MSFTNGXA01.phx.gbl:

> Hi TRW:
>
> No, I have not heard of this behavior before. I have heard of code
> being lost after a C0000005 error but not method code being swapped.
>
> I guess the only defense I an think of would be to save your form
> often. You could always use source control as well. Maybe someone lese
> has a better idea.

Source control is what saved me several hours of work on
this one.

-- TRW
_______________________________________
t r w 7
at
i x dot n e t c o m dot c o m
_______________________________________