Bill often had a very high number of bug counts in VFP betas because he would report every incorrect spelling, grammar error, etc. They became known and "nits" from the term "nit picky" to the Fox team and beta testers because they didn't affect the functionality. Many of the nits were fixed, but not all. I'll be in the LA area this fall, but just passing through and unfortunately, won't have time to visit with Bill and others there. I'm speaking at Silicon Valley Code Camp Oct 8-9, then San Luis Obispo .NET User Group on Oct 10, and Inland Empire .NET User Group (San Bernadino) on Oct. 11.

VFP 3.0 was my first Fox beta. I still remember opening the box and the stack of 3.5" diskettes that were inside. I was working for Plum Creek Timber in Kalispell, MT at the time. They were an AS400 shop and hired me to setup a PC development group there. A local consultant had dome some FoxPro work for them, so they had decided to go that way. I use GenScrnX alot there and had some of my own code that would work cross-platform with no changes. I remember the first time a coworker used my message box routine in DOS instead of Windows. He said, "It's works! You're a genius!"


>BTW, when I worked at JPL, Bill Anderson who sat next to me use to get new versions of FoxPro 2.x and VFP 3.0 betas, when there was only about 25 people on the early beta cycle including a few of us at JPL, and he'd run MODIFY FILE vfp.exe, then use the FoxPro text editor to scan the FoxPro and VFP binary file EXE looking for strings. An early build of VFP 3.0 had a string "Object Basic". I once brought it up to the Fox team, and for a while they thought they had a major leak within the team at Microsoft when they were experimenting with some Visual Basic code embedded within Visual FoxPro. :)