Hi,

I have recently completed a project similar to this. The only difference is that I used the scx/sct's as well as the spr code.

Basically we had a Fox 2.6 app, which we had later ported to vfp6 our sales team biggest barrier to new sales was the look and feel of the product. This meant we had source code in 2.6 and the sct/scx files for the screens and spr files in the vfp6 environment. The spr code for the vfp6 system had some code changes in order to work correctly under vfp6.

In order to port it to vfp9 I started by writing some base forms and base controls for the vfp9 environment. I then created a conversion process that used the 2.6 scx/sct files to add the specific controls on to the form itself. I then used the vfp6 spr code to build a class to hold the business rules. When the form is instantiated it creates a hook into the business object and calls the business rules through the valid and when. The converter done most things from add the status bar text, inputmask etc the form's sometimes needed a quick bit of reworking to make then look tidy but significantly less work then having to re-write them.

I agree that in an ideal world a re-write will be a cleaner way of doing this, but in my case we turned around a system which had 120 screens in less than 6 months, 3 developers and 2 QA, the system is now live in 5 client sites. The company had twice attempted to re-write into vb6 and vb.net and both projects ran more than 2 years and never made it to market. Its given the new system a nice face lift using the outlook style control for the menu, date pickers etc.

I'm sure there are other converters out there and the one I wrote was quite specific to our product but if you wanted any more information then drop me a line and I can send you some screen shots of before and after so you can see what was achieved.

Jon

>Hello,
>
>I am interested in converting some SPRs to Visual Forms. Is there a conversion program I can run?
>
>Thank you,
>Bob