David

No, I didn't look to see if the VFP8 wizards were all changed to VFP9 classlibs. That could have been the problem. I have both 7,8,and 9 installed on my development machine. I have one other application which I used several wizard created forms and I will check before I convert them over.

I appreciate your response. I have run into a few picadillos in converting over a large application to VFP9 but overall it seems to port well.

As the man who fell off a 40 story building and get to the 20 floor and said "So far so good"-:)

Thanks
Gaylen




>Gaylen,
>
>>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.
>
>Are you sure the VFP8 wizard classlib references were all changed to the VFP9 classlibs? That isn't going to happen automatically. If you are developing on the machine where both are installed it'll be problematic because the build process will keep finding the 8 and 9 stuff.
>
>>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.
>
>You can programatically open the FRXs and increase the widths of the numeric fields.