Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Should dotNet become VFP?
Message
From
29/06/2004 17:10:39
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00917121
Message ID:
00918694
Views:
25
Kevin,

Wasn't VFP3 a bit different? My company released the first production VFP3 app in the world- from memory VFP3 was released on 1 August and NZ is 12 hours ahead of GMT, so armed with my free copy from finding bugs in the beta we had completed and released our very first clinical coding application at 1 minute past midnight. i think it was the first app built with an approved 32-bit tool as well, since from memory VFP was the first of those.

Most of it still works today and has not had to be rewritten except as a conversion to C/S which was easy since we used dreaded VFP views. Not bad for a 9-year-old application.

In contrast, the arrival of beans in Java 1.1 almost forced a rewrite for efficiency and GUI. In dotNET, methods we used in 1.0 had to be rewritten in 1.1, and our winforms will be a kludge on Longhorn unless we rewrite, no matter how it is disguised. And if we had moved to VB and/or ADO when advocated by "certain people" in this forum, that would be yet another rewrite along the way.

So as I said, some people are opposed not to the concept of "jumping" but to the timing and purpose of it. The trouble is that the insults start flying at the first opportunity and adult argument is blocked every time.

Regards

j.R
"... 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
Previous
Reply
Map
View

Click here to load this message in the networking platform