Hi Jim!.....

>Hi Mike,
>

-snip-

>
>Hold on, let me straighten the nail, line up the hammer, move fingers out of the wayyyyy, and WHAMO!! Seems someone has hit the nail on the head. That is exactly what we're seeing in the majority of the people in our VFP training classes. We're training them to maintain legacy apps.
>

In the past 2 years, I've been doing some new and legacy stuff in VFP......

In some of the places I've been, they tried to 'upgrade' to VB 6, but the new app would either not work, due to problems with drivers on the network, or else it would be too slow for them... so they would jump back to VFP (the systems were Windows 98 and 2000 PC's, and Windows SQL 7.0 on Windows NT 2000).

What are other people's experiences with upgrading 'legacy' FoxPro (FP and VFP) to VB and VB.NET and C#.NET? Be honest now.... successes or sorrows???

(Mine has been that at the places it has been attempted, they stayed with the Fox.)

Thanks

Tommy