Jess

FWIW I concur 100% with your decisions.

If I had my time with VFP over again I would "slow down" in 1995 and deliver nothing in VFP until the frameworks became available. We still have extensive bespoke code doing stuff that could be done in a few lines using framework tools maintained by others.

Secondly, I "shifted" the company to Java in 1997 because I perceived that VFP was in trouble. I fully understand some of your current pain! The migration to Java was a disaster because we went too soon and unlike dotCOMs we needed to make a profit. Really bad developers had a field day because they had a ready excuse for delivering nothing. The company turned into a "hobby club" with cool Java dudes turning up and doing whatever they felt like, calling it "research". This was before Beans and J2EE, you could not even do a decent printout in Java. We produced one web client app in Java, then MS produced IE3.01 with a buggy Java that gpf'ed. It really was a bad time.

IMHO Java was at a position where dotNET is at now. There are lots of people enthusing, quite a few bugs (e.g. in debugger sometimes the line numbers go haywire), nobody truly making $ out of it yet except enthusiastic authors, a few trophy apps coming out that will have cost more $ than doing it other ways or will be the result of abnormal commercial cues.

The true benefits come later. Later is where you want to be!

Regards

JR