>Fact: ADO is SLOOOOOW compared to the dedicated mechanisms in tools like VFP, Delphi and increasingly Java. If you use ADO everywhere, you'd better have a better explanation for the cost you are imposing on clients than the "fact that it is generic" and therefore necessarily better.
>>

Java is SLOW as molases if you use it for the wrong job. Case in point. We recently upgraded from PVCS Version Manager 5.x to 6.x. The new front end is way cool, it matches the i-net interface, supports multi platforms, great stuff.

However, the developer interface, which I use in VFP so my project is under shource control was obviously much slower. I went from opening a project instantly with the 5.x interface to it taking 30-45 seconds to open with the 6.x interface.

Well, I called PVCS and they said they had rewritten the development interface in Java, where it was originally in C++. A HA! No wonder its a dog. Oh yes, said the rep, but now we can provide the interface on multiple platforms with the same code source.

Well, that's great for them, the developer, but for me the customer, it SUCKS!

So, does Java (read VFP here too) have advantages for the developer? Sure, espesially if it is your favorite, or only, or most well known environment. Does that mean it is the best for the customer?

So, why did I write this? I don't know, I just wanted to bitch about PVCS using something that is better for them, and worse for me!!

Bob