🚀 go-pugleaf

by the way, Bob, I have checked out the link you gave me, while being
very educational, it is not talking about how to solve the problem of
the dbExpress. You are assuming I have no experience in how to use
dbExpress, but as a metter of fact, I'm not a total noob about
dbExpress. I have been working in a software studio with C++Builder 6.0
Enterprise for 2 years. Now I have left that company but I still have
access to dbExpress in C++Builder 6.0 Pro, from my friend that I
mentioned earlier. That version of dbExpress (which uses dbexpmysql.dll
as it's library) is working fine with the MySQL version 4.0.20 which I
am using now.

I tried replace the SQL Library in TC++ Explorer, which is dbxmys30.dll
by copying the library files from my friend's PC, and replacing the
LibraryName property of the component. I could connect to the server and
display the table, do a query on the database tables with TSQLQuery, no
problem at all. Amazing isn't it? Now since the databasr opened with
TSQLQuery is unidirection, I have to use TSQLDataSet. This TSQLDataSet
will not work with the older dbexpmysql.dll. I give all sorts of error
such as Operation Not Supported and Invalid Data Translation.

If you are not aware of the problem, please do a search on Google with
the keywords "dbExpress, Invalid Data Translation", and you'll see how
serious this is. Or perhaps you could try downloading TC++ Explorer
(It's free and 650MB at most) and experience the buggy, non working
dbExpress first hand. You will understand why I think it is a bad joke
the first place.

I have done extensive research on this problem, I googled for answer, I
visited many discussion groups and I have been to Code Gears, and
Borland's support site, looked at their knowledgebase, checked their
pending problems at the customer support site. Nothing. Absolutely
nothing. The only viable solutions now are using 3rd party components
such as products from CoreLab or free solutions, or more precisely, a
huge detour, by using MySQL ODBC connector, which, I have to ask, what's
the point of using MySQL if I have to in the end resort back to BDE, an
already discontinued and almost obsolete component?

Borland is acting like this problem never exists. This is a major bug in
their release and so far, TC++ Explorer has been out almost one year and
they have been either still oblivious about such serious bug (MySQL
support is totally not working), or they are trying to act like they are
oblivious. That's why I have been reluctant to come to this Borland
Newsgroup for an answer, since I doubt the officials will give me an
answer. My posting here is a sign of I'm desperate and try to find
myself a last reason to stay with Borland's product, before I finally
jump to other IDE.

So, is there any way to solve this problem NOW, or any version of MySQL
that is confirmed working with this dbxmys30.dll(the one they actually
tested their dbExpress with and confirmed it is working before they
release TC++ Explorer....oh wait, could it be they have never tested
their new dbExpress library? They just changed the code and compile it
and release, WITHOUT ACTUALLY TESTING THE DLL???)? Or I have to wait for
Borland to finally wake up? I guess making the jump and learn to use a
new IDE and a whole new set of language and programming API is less
painful than to wait for Borland. C# looks nice and there is a free C#
IDE from a much more reliable and helpful company out there.

regards,
Anooyed-nimous.