>Hi, Jess.
>>
>>Maybe it will be a good idea if VFP Team would include in SEDNA a tool to convert VFP app programs into C# programs. And a lot of VFPers who are not yet jumping to .Net bandwagon will immediately jump without thingking. And MS will instantly win the heart of VFPers. This is a serious suggestion not a funny one whom some think that it is.
>
>If you are a UT Magazine subscriber, you may look at:
>http://www.utmag.com/wconnect/wc.dll?9,7,10,,594
>
>In this article, Pablo van Diest presents a basic translator from VFP to C#. But of course, it just translates domain logic. You can't really translate things like USE/SEEK/SCAN constructions and other typical VFP features. And assuming you use a lot of complex transformations to do it, you'll end up with a flawed model for a .NET application.
>
>Have in mind that not even VB6 can be converted straigth to VB.NET. Just ask any fellow VB developer around you. ;-)
>
>Regards,

Hi Martin,

Actually we are already in the last part of converting our VFP app into C#.Net program and I noticed something obvious: VFP is a lot smarter when it comes to data manipulation.

We still use 9.0 but just to maximize its reporting features which is extremely important in adding some good features that adds value to our current application.