Hi Thomas,

I tried opening one of the old 2.6 screens inside VFP8 via its project manager. I was asked if I wanted a visual or functional conversion. Either one produces some really strange results.

I'm guessing that its because the 2.6 code wasn't "well written" since it was using a third party code generator (gentab?) for faking a tabbed container. All of the old screens also had a similar thing to do 3D effects.

I guess the conversion process can't handle these situations very nicely. Now, I'm thinking about starting from scratch. At least I have a base to start with even if it requires running both VFP8 and FP2.6 Windows simultaneously to do a "manual" conversion.

Mike

>Hi Mike,
>
>I just ported a large insurace app from FPW to VFP6:
>
>(going into Beta 3 on Thursday, to be shipped via CD
>and the net september 16th: You have to be in the
>latest Version that is not any more officially
>supported by MS <g>)
>
>and it was quite easy.
>
>If it is still a FPDos app, you should port it to FPW first,
>since the same code should be able to run. If it looks ok,
>porting is an option I'ld ALWAYS recommend if the code of the
>app is (for 2.6 standards) "well written".
>
>I fixed up a few bugs in the screen converter so that
>it works flawless on our testscreens, but running the old
>.spr's is another viable option.
>
>my 0.02 EUR
>
>Thomas