Hi John,

Why're you and Mike always in the interesting discussions? <g>

As far as a methodology and migration path, take a longer look at COMCodebook - you'll see where things like ADO+, Biztalk, etc., are all slated to fit in. We're facing the same issues you talk about, and we're planning on a method migration - beginning 6 months ago with our use of the framework...

yag
>>
>>
>Now, as far as something that actually takes a VFP application and converts it to C# or VB.Net code goes, I don't think there would be much value in one. Sure, you could convert the forms to WinForms, but the code would be a different issue. It could be done, but the typical VFP application doesn't really fit the .NET architecture and changing all of the DML code to use ADO+ instead would be a big undertaking. It'd probably be just as easy to write a CLR compiler for VFP. ;-)
><
>
>I was talking more about a methodology and migration path as opposed to some tool that in all liklihood - could not be built....
>
>< jvp >