Ed,

This is a problem of Delphi, not IBO. I had this problem some time ago.
There is a problem of difference in the precision de datetime values used in
delphi and the values stored on database. So, when IBO try locate a record
in Interbase GDB, this values don't match due the precision on time portion.
The workaround is to use a surrogate key as Jason well said. This was your
advice to me when I had this problem.

Luiz.

----- Original Message -----
From: <edc@...>
To: <IBObjects@egroups.com>
Sent: Sunday, December 31, 2000 11:39 AM
Subject: RE: [IBO] row update problem


> I have a unique generated key already in the table..
> posting using this as a key link works... however..
> i consider the inablility to have a key structure with
> a tdatefield used as a key link to be a big bug....
>
> happy new year
> ed croxford
> edc@...
>
> -----Original Message-----
> From: Jason Wharton [mailto:jwharton@...]
> Sent: Sunday, December 31, 2000 3:07 AM
> To: IBObjects@egroups.com
> Subject: Re: [IBO] row update problem
>
>
> It very likely has to do with using a date column. Try to figure out a way
> to omit the date and see if it works. Use a single surrogate key is what I
> suggest you do.
>
> Maintain it with the GeneratorLinks property and a trigger that checks for
> NULL and assigns a value if it is so.
>
> Regards,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: <edc@...>
> To: <IBObjects@egroups.com>
> Sent: Saturday, December 30, 2000 2:47 PM
> Subject: [IBO] row update problem
>
>
> > When making a change to a certain table i get 'RECORD was not located
> > to update' when i try to post the change...
> > this is the output from the monitor..
> [snip]
>
>
>
>
>
>
>
>
>
>