>I wouldn't waste time or money on it. I see how coworkers struggle with C++ Builder. Borland's ADO libraries flat out don't work...we found that out the hard way...and are now using Microsofts. There are lots of other issues that we have to deal with.

Several years ago, I was hide to convert a COBAL database to Access. In addition, they had me develop a application in C++ Builder to manage the converted data. I sruggled for a month with the it, until a co-worker noticed my difficults. He email me a set of C++ library that he had modified. He told me to stop tring to use the libraries that came with Borland C++ builder for they were too buggy, and have always have been. Once I started using the modified libraries most of the problems went away.

Also.

Even after nearly a year in working Borland development language, I still could not completely understand the Borland Database Engine (BDE). It seem to require that the database object be linked to the table object. Even though I managed to get it to work, it never seem to be the correct way of do it.

>
>We're already working with one "dead" language...you want to pick up another?

Look at the TIOBE chart. Delphi is #9, and FoxPro is #16.

>
>>With this all in mind, I am wondering if I should be investing in Borland, and their competitive development suite. Personally, since Turbo-Pascal, I have had little interest, or experience, with any of the Borland products. But money is money. And this may be a good investment. Ideas?