Thanks Sergey and Arto
Since it was the only form created by a wizard in my application and a small one at that I decided to just create a new one in VFP9. That fixed the problem with the VFP9 build. Works fine in VFP8 also. Something got corrupted over time.


I normally don't add a new thread to an old one - but when I print reports in VFP 9 using the ReportListener a number of the fields end up with ***** and I need to increase the length of the fields. I know you can print the reports in VFP9 as the default is VFP8, however then you have two user interfaces which I think is confusing to the user.

Other than just running all the reports is there anything one can do to prevent this or find the offending fields.

Thanks to both of you for your help.

Gaylen






Gaylen






>>I have a VFP8 application that I am converting to a VFP9 application.
>>I have one form that hang the VFP9 build when trying to create the app. When I run the form by itself with either VFP8 or 9 it works fine. When I create the VFP8 application there is not problem with the form, However when I use VFP9 the build stops and the file ends up getting corrupted. I have to use the three finger exercise to exit out. And when I try to open the form using either 8 or 9 I get a c0000005 error.
>>
>>Interesting the form is a form that was made by the form wizard and only has 2 fields and 1 table.
>>
>>Anyone know why VFP9 is hiccuping on that type of form?
>
>Hi Gaylen,
>
>My guess is that form is corrupted in some way. For starters, I would open the form as a table and pack it. After that I would isuue COMPILE FORM on it. If it doesn't help, I would create a new test project with just that form and try to build it. Don't forget to open VFP Debugger before build. The Project Manager outputs build log into Debug Output window.