Subject | Firebird Generated Keys as Master / Slave Links and IBO Controls |
---|---|
Author | George |
Post date | 2006-12-01T18:17:25Z |
We have converted an old BDE App to Firebird using IBO components.
We now want to optimise the app to get the benefit of the combined
Firebird / IBO functionality.
Our problem concerns generators - specifically, having gone to
primary keys having no logic in the real world but being generated by
a Firebird Generator, we now have linking problems.
From what we understand, for a field to be populated by a generator
it must be left out of the IBO query SQL statement. If this is so
then the query doesn't have it and cannot use it as a linking field
in a master/slave relationship.
Can anyone point us to a document that will enlighten us on Master /
Slave relationships using generator populated fields as the key?
The samples are in Delphi and we are using C++ so can't access them.
Many thanks
George
We now want to optimise the app to get the benefit of the combined
Firebird / IBO functionality.
Our problem concerns generators - specifically, having gone to
primary keys having no logic in the real world but being generated by
a Firebird Generator, we now have linking problems.
From what we understand, for a field to be populated by a generator
it must be left out of the IBO query SQL statement. If this is so
then the query doesn't have it and cannot use it as a linking field
in a master/slave relationship.
Can anyone point us to a document that will enlighten us on Master /
Slave relationships using generator populated fields as the key?
The samples are in Delphi and we are using C++ so can't access them.
Many thanks
George