Subject | Tables with PK AutoGen |
---|---|
Author | Daniel Jimenez |
Post date | 2004-12-07T02:56:26Z |
Hi,
I have notice that when dealing with tables that define the PK as an Auto
Generated integer value (through a trigger) the refresh action of IB_Query
is not respected, that is, if I set the IB_Query RefreshAction property to
raKeepDataPos and the primary key is non auto generated, after a post the
cursor remains in the correct position (the new record remains at the
position I inserted it on the grid), but when the table has a PK which is
auto generated, after a post the cursor is place at the first record and the
new record is displayed at the end.
What am I missing? As I do not want this behaviour, but I definitely need
the IB_Query property CacheUpdates to remain False.
Thanks
danieL.
____________________________
Comvision Pty. Ltd.
www.comvision.net.au
I have notice that when dealing with tables that define the PK as an Auto
Generated integer value (through a trigger) the refresh action of IB_Query
is not respected, that is, if I set the IB_Query RefreshAction property to
raKeepDataPos and the primary key is non auto generated, after a post the
cursor remains in the correct position (the new record remains at the
position I inserted it on the grid), but when the table has a PK which is
auto generated, after a post the cursor is place at the first record and the
new record is displayed at the end.
What am I missing? As I do not want this behaviour, but I definitely need
the IB_Query property CacheUpdates to remain False.
Thanks
danieL.
____________________________
Comvision Pty. Ltd.
www.comvision.net.au