Hey Steven,

>We've seen this movie before. It sucks. VFP 3 sucked. Customers I built applications for in VFP 3 are long gone, never too impressed with my abilities.

I had two clients a few years back running VFP3 apps, one that had been designed by IBM (!!) in 1995-6. Both sucked; mainly because the developers who had written them had not matured their VFP architectural styles.

Anyhow, when I was called in to rescue these apps, I was not allowed to upgrade them to VFP5 to take advantage of features they desperately needed. Since there were deep-rooted architectural flaws, anything I did to make these apps better was doomed to - at best - mediocrity.

So I suffered the same fate of being branded a poser because I had to work within a v1.0 architecture.

Disclaimer: This is not intended to support the contention that VFP 3.0 or any other MS tool sucked or sucks.

I am simply sympathetic to the idea that anything written on a brand-new platform tends to have some pretty big foundational flaws in it.