🚀 go-pugleaf

Max schreef:
> Hello,
> 
> I'm encountering a problem in the combination of MySQL and dbexpress in 
> Borland C++Builder 6.
> With one TSQLConnection and a couple of TSQLClientDataSets I've made an 
> application. The TSQLClientDataSets are from the CommandType ctTable and 
> the MySQL tablenames are loaded at runtime just before the datasets are 
> opened. In fact the initial tables exist already in the database and 
> their names have been put in the datasets at designtime already.
> The idea is that I want to copy the database tables to new tables (in 
> fact saving the old tables for later reference) and from then on use the 
> new tables with the datasets.
> The new tables are created using a TSQLQuery with the exact create SQL 
> query MySql generates with a mysqldump.
> I open a dataset with the old table and I use a separate destination 
> dataset for the new table. This way I copy the data from the old table 
> to the new copy.
> 
> So far so good.
> 
> The new tables have the same size and the same record count as the old 
> ones and all seem well.
> 
> When the new tablenames get loaded in the datasets, these datasets 
> behave differently than they did with the old tables! This changes when 
> I enter the new tablenames at designtime in the IDE.
> There is something that happens to the dataset if you define it at 
> design time using a database table, what I couldn't duplicate by just 
> putting the database tablename in the dataset.
> 
> What am I missing?
> 
> Regards,
> Max

Suddenly it started to work. Although I'm not too confident about it.
What worries me really is the non-activity of this newsgroup. Doesn't 
Borland believe in it's dbexpress? Most questions here stay un-answered. 
If you compare the responses with cpp or vcl you could call this group 
dead. Can somebody of Borland comment on this?

-- 
Max

C++U2