Hi everyone
I'm busy working on a bit of a legacy application whose database tables get their unique values for thier primary key's via triggers and generators rather than using the "generator" property in the IBX query component.
I'm having the problem whereby I insert a record within my application yet it gives me an error that I have not inserted a value for my primary key... but I do have my trigger set up to insert a value into the primary key of the table before an insert(I've been through it a hundred times). What I do to get around it is I simply enter any old value into the primary key, I then post the record and any changes to the database (apply updates with cached updates activated). When I view my data grid it shows the bogus primary ID value I entered yet when I close the application and re-open it I see the intended value from the generator in the primary key. I thought it was simply a database refresh problem, but no amount of refreshing from database seems to help. The only thing that works is if I close my query and then re-open it, that seems to sort my problem out but then my table position is zonked.
Any ideas what the issue is? Shouldn't I see the value placed into the primary key as soon as I wish to insert a new record?
I'm busy working on a bit of a legacy application whose database tables get their unique values for thier primary key's via triggers and generators rather than using the "generator" property in the IBX query component.
I'm having the problem whereby I insert a record within my application yet it gives me an error that I have not inserted a value for my primary key... but I do have my trigger set up to insert a value into the primary key of the table before an insert(I've been through it a hundred times). What I do to get around it is I simply enter any old value into the primary key, I then post the record and any changes to the database (apply updates with cached updates activated). When I view my data grid it shows the bogus primary ID value I entered yet when I close the application and re-open it I see the intended value from the generator in the primary key. I thought it was simply a database refresh problem, but no amount of refreshing from database seems to help. The only thing that works is if I close my query and then re-open it, that seems to sort my problem out but then my table position is zonked.
Any ideas what the issue is? Shouldn't I see the value placed into the primary key as soon as I wish to insert a new record?