At 03:15 PM 12-03-02 +0100, you wrote:

>Helen,
>
> > Ah, OK, that's fine for when you only need to update/insert to/delete from
> > that KeyRelation table. But, of course, if you *need* to perform DML on
> > more than one of the tables, using the xxxxSQL properties is pretty cool
> > for making the joined dataset updateable...
> >
> > I don't think that an xxxSQL property like
> >
> > execute procedure UpdateMe(:param1, :param2, ....)
> >
> > is really *clumsy*, if the params have the same names as the columns of the
> > dataset and the KeyLinks are perfect.
>
>The *TUpdateSQL*. That was clumsy.

Who was talking about TUpdateSQL? Were you? Didn't you use the xxxSQL
properties, then?

>BTW, if the parameters names must
>match the fields names, how can I discern between old values and new
>values in update statements? With the BDE I have :OLD_FIELD_NAME and
>:NEW_FIELD_NAME.

You can in IBO, too; but why would you need to? All you need is for the
xxxSQL to automatically pick up the current value of the KeyLinks and any
other columns required. I guess that, if you used a TUpdateSQL instead of
the xxxSQL properties, you would have a *clumsy* time matching up
parameters, though...

>WRT multi-table update, I don't think I am going to need anything the
>BDE can not do, at least in the short term. My requirements now are
>pretty easy to meet. :-)

Oh, and I thought you were using IBO. How extraordinary.


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at
www.ibobjects.com