Master-Detail-Problem after query's sql change
Posted: Thu 16 Dec 2010 20:58
Hi,
it happened the second time now that a TIBCQuery doesn't work correctly after a - minor - change in the SQL statement.
When inserting a new record now, it complaints about a missing foreign key value, but that field should be filled by the master-details mechanism.
It worked before the SQL change, and I can't restore the functionality even when changing back the SQL statement.
Last time (with another query in the same project) I had to rebuild the whole query from scratch (with lots of persistent fields), I'd really like to avoid that!
Any ideas?
I use version 3.50.0.18 due to unicode problems in 3.50.0.19 described in another topic (http://www.devart.com/forums/viewtopic.php?t=19480).
Please help to solve that issues!
BR,
Martin
it happened the second time now that a TIBCQuery doesn't work correctly after a - minor - change in the SQL statement.
When inserting a new record now, it complaints about a missing foreign key value, but that field should be filled by the master-details mechanism.
It worked before the SQL change, and I can't restore the functionality even when changing back the SQL statement.
Last time (with another query in the same project) I had to rebuild the whole query from scratch (with lots of persistent fields), I'd really like to avoid that!
Any ideas?
I use version 3.50.0.18 due to unicode problems in 3.50.0.19 described in another topic (http://www.devart.com/forums/viewtopic.php?t=19480).
Please help to solve that issues!
BR,
Martin