You could see the writing on the wall when Alan Schwartz and Andy Neil left MicroMega a few years ago. Chick Bornheim was the marketing brains behind MicroMega and Alan and Andy were the technical architects. There were some terrific developers under them but they were the visionaries.

And even at that, I think they took a cautious approach to VFP. They decided to maintain a single code base which would support both VFP 3.0 and FoxPro 2.x. I can understand that from both a maintenance and marketing POV -- by no means all the FP 2.x community moved to VFP -- but it precluded them from using nifty VFP-only features like database containers, rules, and triggers. When I evaluated a beta version of FF 3.0 for a review for one of the FoxPro magazines (which got pulled when a new editor came in) I was taken aback that there were no DBCs or VCXs to be found. Andy Neil explained in an email the decision they had made and why they made it, not without regret that he couldn't put the new VFP features to use. Again, I'm not necessarily disagreeing with their decision. But I think FoxFire's downfall *as a VFP product" began right then.

Mike