Hi Rakesh

Well designed VFP is completely different from well designed FPD. The converters do what all meat grinders do. If you put in fantastic FPD t-bone, you will not get fantastic Prime Rib VFP. You will get hamburger. :)

If you've chosen VFP because you used to use FPD2.6 you have over-estimated the amount of code you can reuse. VFP is sufficiently different from FPD that you should already have been considering other tools.

>Hi,
>
>Just a few months back I have been learing VFP for rewriting our Accounting software in VFP. We have not released any software yet. ( it's long way off target, due to minor improvements/features in DOS app. ) After reading all the messages about no new VFP core development from Microsoft, we have to decide if we should continue with VFP or choose some other platform.
>
>Some of our concerns are :
>
>If an OS is relased in 2016, will VFP core be modified. Similar to SP2 being released for Vista ? or will virtualization solve the problem.
>
>We have lot of code which can just be used in VFP like Inventory updation, accounts updation, year end processing, reports ( about 400 FRX's, which print to a DMP ).
>
>You viewpoints will hightly appreciated.
>
>Rakesh