Problem with reports converted from FoxPro 2.6 1

[rmarotta]

Despite Microsoft's claim that VFP will convert and run FPW 2.6 Reports without change, I'm finding that there are some &quot;sizing&quot; issues after conversion.<br><br>Lines that used to end at the edge of the page bleed over to a new line.&nbsp;&nbsp;And errors that read &quot;Page Header band is too large to fit on page.&quot;&nbsp;&nbsp;This is occurring even though the font and font size have not changed.<br><br>Do I need to change property settings before or after converting?&nbsp;&nbsp;Is there a patch for the converter.app that fixes this?<br><br>

 

[dgrewe]

Since When Were MicroSofts Claims Totally Truthful?&nbsp;&nbsp;They Only Tell You What They Want You To Know So You Will Use Thier New Products?&nbsp;&nbsp;Needless To Say, Everyother Company Does The Same Thing, Except MicroSoft Just Does It More Often.&nbsp;&nbsp;<br><br>I have yet to get any complex report to convert from FPW to VFP.&nbsp;&nbsp;The converter&nbsp;&nbsp;program works well on simple reports with no Data Groups are headers Groups or Title pages. The only thing you can do is redesign the report in VFP.&nbsp;&nbsp;From the early release information of the new VFP7 (if you can trust what MS saids), nothing was done to improve the Report form designer.<br><br>The other option is to move your reports away from MicroSoft and use a 3rd party report form designer like FoxExpress,&nbsp;&nbsp;Crystal Reports,&nbsp;&nbsp;RR, etc.&nbsp;&nbsp;They have a <font color=red>MUCH</font> better reputation of supporting conversion upgrades then MicroSoft. <p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br><a href= > </a><br>

 

[rnerison]

Have you had any trouble with screens/forms converted from 2.6?

 

[dgrewe]

VFP will run V2.6 Screens Exactly as they are.&nbsp;&nbsp;You do not need to convert them.<br>As a mater of fact, you can design a screen in 2.6 and any Version of VFP will run it. There will be some differences in the look and feel of it, but it will work. You only need to change them if you want to add the OOP functionality to them.&nbsp;&nbsp;Then I suggest you do not try to convert them, Just start from scratch with a total rewrite. <p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br><a href= > </a><br>

 

[Guest_imported]

I used to have lots of problems in migration from 2.6 to ver 6.0. Specially all the lines on the&nbsp;&nbsp;2.6 screen are acceptable to&nbsp;&nbsp;version 6 does not at all. The best thing is if you can convert it into version 3.0 and then version 6. Make sure only select the function conversion otherwise you will get plenty of problems.<br><br><br><br>Saeed<br>

 

[rnerison]

Maybe I am alittle confused with all the Visual Foxpro, but I only copied my .spr files and built an exe in Visual. I did not use a converter program. Unless I am misunderstanding, that is what you mean by conversion, correct? We have several similiar applications that we have built a VFP exe with, four of them are giving me the same problem with these two screens, where two of them are running fine. The two screens I am referring to are modal and the first one called is built from an array. Could there just actually be coding issues that 2.6 allows, but VFP doesn't?

 

[dgrewe]

If you start VFP and them do Modi screen xxxx Then a VFP warning appears that the report is a previous version fp and asks if you want to convert the screen.&nbsp;&nbsp;THAT IS THE CONVERTER PROGRAM. <br><br>Just copying the files and telling VFP to run them is not a conversion. <p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br><a href= > </a><br>