>>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.

Being stuck with the decisions of previous developers is exactly why I promote mdot. I have seen way too many systems where you cannot tell if it's a replace or an assignment deep in the code, long after the private variable was declared, with the same name as a field elsewhere. That is the real world.

Walter is unwilling to recognize science trumps opinion. No one is calling him out. That is my reason for my recent rants. There are several pretenders in this community who are given a pass.