Hello fellow migrators,

I too am in the middle of a conversion.

My approach is to write a program which steps through the project and creates a new one in a new directory file by file. Frankly, all are left the same so far except the screens. I have placed an early attempt in the UT files section, but it is very inclomplete and incorrect. Within a month I'll be placing a more evolved version.

Let's stay in touch on this subject since it is a very important one for many of us.

Alex



>Hi Eric. Very good points. I should have stressed that in my response. The UI is the big issue with the conversion. Thanks.
>
>>I am currently in the middle of a 2.6 for DOS to 6.0 conversion as well.
>>I have the luxury of having a great deal of VFP 5 AND 6 experience already though.
>>
>>While I agree with Evan's assesment overall, I think that there are somethings that you can do to speed up the re-write.
>>
>>I would definitely keep the code that you previously might have kept in a procedural library. Most of the time code (such as functions and procs specific to an app) will work great as is. There's no real need to convert the majority of it. (maybe just a little tweaking)
>>
>>You definitely don't want to try to convert any of the screens, but I am using my old report forms as a basis for creating my new reports. They don't just port over very well, but I have written a utility that goes into the frx file (after VFP converts it) and it automatically sets the page layout (landscape, letter, etc.) and changes some of the horizontal positions so they fit within the report form (otherwise some fields may be way off to the right out of view). Most of all that is left is the layout and font stuff.
>>
>>Although the report form conversion process is a bit tedious, it beats reinventing every report.