At 12:50 AM 10/04/2007, Jerry Sands wrote:

>I have been trying to track down a problem for almost a week now and don't
>seem to be getting anywhere. I have a program that has run fine complied
>with Delphi 2006 and Firebird 1.5.2 using IBObjects 4.6.A that is broken
>with IBObjects 4.7.16. It uses a TIB_Query and a select from a selectable
>stored procedure. The Insert, Update, and Delete SQL are set to make this
>live data to a single table. The update and delete work just fine but the
>insert is giving me problems. When posting the new row to the dataset
>IBObjects appear to be using the data from the current row just prior to the
>insert. The exact same code works fine compiled with IBObjects 4.6 and in
>both cases I am connected to the exact same database. As a side issue since
>I wanted to determine what SQL was actually being passed, using the
>IBObjects SQL Monitor when posting the inserted record returns an
>EAccessViolation at address 00000000 read of address 00000000. I look at
>the data to be inserted in the before post event and it is indeed the data I
>want to insert but after that point IBObjects appears to be using the
>previously selected data row to feed the Insert SQL statement.
>
> I have tried very hard to come up with a small example of this but have not
>been successful. I will continue to try to come up with a good example but
>I understand with all the changes to Firebird 2.0, etc maybe this will ring
>a bell with Jason or someone else that is more familiar with the IBO
>internals.

I'm not seeing this at all, so I suggest there might be something
wonky in your SQL. IBO has had a lot of tightening to comply with
the corrections in SQL in Firebird 2. This is going to show up a lot
of off-beam SQL in client apps that used to be forgiven.

Let's see the following:

-- The SELECT statement
-- The InsertSQL statement
-- The KeyLinks for the set

Helen