A short, frank/honoust reply from my side...
Though my interest says "Yes, go for the VO solution!", my common
sense says "Don't use VO for this kind of applications, there is no
other VO-knowledge in your company!". Our company would become too
dependent on one person when using VO for large scale application
development. So, with tears in the eyes... I must admit that using VO
in our fully Microsoft based environment would not be the best
decision to be made for a company in which approx. 45000 FTE's are
working. For data conversions (for accounting packages, etc.) I will
always use VO. This because of the simple reason that I used Clipper
and Dbase in the past. In my opinion VO is the perfect programming
language for data manupulation. I will also remain using VO for small
applications but to use it for applications that are used by a large
number of our user committee would also be against our in-house
policies and standards. Instead the Microsoft development tools
(Microsoft Visual Studio, etc.) will always get the preference from my
Senior Management. Again, with tears in the eyes but, in my opinion,
with a realistic view on the topic.
Brgds,
Rob
|
