Tracy
As an "early adopter" with VFP we rolled out own login security, baseclasses, interface... you name it. Actually we released one of the first 32bitUI apps in the world in August 1995 on the day VFP3 was officially released- New Zealand is GMT+12 so we released while most of you were still in bed. < g > So we won that race... and to this day we still maintain some of that hideous, early-learning spaghetti.
This time we're waiting for the framework. Why should I maintain thousands of lines of generic code that does not specifically target my customer's business need, when people like KM will do it for me for a fraction of the cost, and open up a whole market of potential contractors who already know the framework and can focus on tasks rather than trying to understand my variant of every little thing.
In the meantime we stay productive with VFP and have already decided to stick with VFP for some server needs. As you note, VFP *can* interface with dotNET, so why not?
Go KM!
Regards
JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
