Problem editing datasets after upgrading to sdac 4
Posted: Thu 05 Apr 2007 08:12
Hi,
after upgrading from sdac3 to 4 I've problems editing TMsQuery-datasets. A query like Select tbl1.*, tbl2.name from tbl1 left outer join tbl2 on tbl1.id_tbl2 = tbl2.id order by tbl1.name reports a 'ambiguous field'-msg when setting the dataset in editmode. Looking the Sql in profiler an 'where id=&P1' is added. (id is the primary key). RefreshSQL and UpdateTable are both nil. Only setting the RefreshSQL the problem could be resolved. With sdac3 this problem wasn't there. Now I'll have to set the RefreshSQL for all queries containing joins with same names for primary keys (in all my tables the primary key is named ID). Could you resolve this adding the first tablename in the runtime-addes RefreshSQL if no updatetable is specified, otherwise the name of the UpdateTable?
best regards
Toni
after upgrading from sdac3 to 4 I've problems editing TMsQuery-datasets. A query like Select tbl1.*, tbl2.name from tbl1 left outer join tbl2 on tbl1.id_tbl2 = tbl2.id order by tbl1.name reports a 'ambiguous field'-msg when setting the dataset in editmode. Looking the Sql in profiler an 'where id=&P1' is added. (id is the primary key). RefreshSQL and UpdateTable are both nil. Only setting the RefreshSQL the problem could be resolved. With sdac3 this problem wasn't there. Now I'll have to set the RefreshSQL for all queries containing joins with same names for primary keys (in all my tables the primary key is named ID). Could you resolve this adding the first tablename in the runtime-addes RefreshSQL if no updatetable is specified, otherwise the name of the UpdateTable?
best regards
Toni