>>>The application is stuck in vfp6 - because the previous developer kept making bad choices.
>>
>>I truly feel sorry for you, Mike. Being stuck in VFP6 when there's the excellent VFP9 swan song must be very difficult. I was at MS when we released VFP6 and that was like two or three dog's lives ago. In fact, I barely remember back that far.
>>
>>At one job I worked the code was in VFP7 and VFP9 had been out of a few years. I proposed going straight to VFP9 and skipping VFP8 and was questioned by the CIO. I had lost a lot of stupid arguments to him about coding in Fox which he dabbled in and was very poor at. Anyway, we made the jump to VFP9 and everything was good.
>
>I helped one of our old buddies here at the time to make the jump from seven to nine. The app was something I was just barely acquainted with. Took about two evenings - the only real caveat (apart from local array declarations, where the syntax changed, but compiler catches that) was the changed behavior when a select into array with aggregate function now returned at least one row containing nulls instead of no rows. So check for null, not for _tally - and that was all.

This app, like many I have seen grew like weeds for 30 years. It's not that easy, yet somehow this behavior is tolerated. It's really stupid. Those changes you mention are not even worthwhile. There are no SQL Server transactions, multiple copies of the same routine, and numerous other mistakes. Hell, these people never had a FoxPro magazine nor attended a user group meeting. No interest in improving.