Another example of .NET the vfp developers toolbox!
Seriously though it does show that to work with vfp these days seems to
be a much broader task than just being able to hammer out fox code. On
the plus side vfp developers seem more than capable of dealing with an
ever expanding environment, in fact we seem to see it as one of our
strengths! When did you last see a .Net developer jumping from product
to product to get the best possible result? It doesn't happen often and
yet we do it all the time, a bit of this here, a bit of that there all
glued together with vfp.
My sympathy lies with the Office developers who are stuck with access as
a database and, even with the better use of VB within the suite, a
cranky development environment that gets changed every year (more or
less) sometimes making their applications fail completely without major
re-development. We may talk forever about what is the next product
version and the weakening of our marketing position but compared to
those poor b******s we have it simple.
There is one thing you can say for them however. The very rarely sell
their products by saying what the database is. They say this is my app
that does this. It makes me ponder if we worry too much about stating
what we are developing in. If you don't labour the point, do the end
users care what the database actually is or are they more interested in
your businesses ability to deliver for the long term?
Ooops, Rambling!
--
Michael Hawksworth
Visual Fox Solutions
[EMAIL PROTECTED]
www.foxpro.co.uk
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
