>Hi Gang!
>
>Well, I was asked to see what we (as the the Company I work for) need to do to convert over our VFP programs to dotNET.
>
>I was specifically asked to see if there was anything out there that would AUTOMATICALLY convert all or part of the code over to .NET and then we could convert the rest over by hand......
>
>'Thanks for the info....
>
>Tommy
Just did this for a HUGE app over the past 3 years. My recommendation would be to recode it in .Net manually and only convert the reports (you will still need to touch-up each report afterwards) using vfp2net reports:
http://www.vfpconversion.com/products.aspxYou can customize the converter.
That way you can design it smart from the get-go. The initial architecture design and decisions are the most important (pattern to use, layers, data access design, etc).
There are numerous resources out there now for coding existing vfp apps in .Net. Get some real world advice (it's worth paying for) from others who have done it and have a productive working app in place.
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"