Hello Geoff,

> I am not sure what your concern is over updating the entire row. The
> only impact of any significance this has is that server based defaults
> will not be applied during an insert (so use the TIB_Query
> DefaultValues property). There will be almost no difference in either
> network or server performance in updating a single field versus the
> entire row.

Yes, mormally over a fast network it doesn't make much of a diffenerce.
However, it sure does when you have blobs in your tables. Like I
mentioned, I'm converting a complex TravelBureau management system
I wrote 5 years ago, from BDE to IBO as a conversion test and the
RichEdit travel/tour descriptions can be huge. Don't want to rewrite the
program using IB_xxx, just convert showing how easy it is to do such.

I must admit, simple little one form, one table, one grid application
convert easily. But I've run into many questions, a few posted here and
had to change quite a bit of program logic, since TIBO slightly works or
behaves different than BDE. Keeping a list :)

Used to AstaServer/Client software, which goes into great depth
to minimize Server/Client data exchange. Which makes sense if
you use a slower internet connect.

Best Regards,
Hans
=================================================================

Geoff Worboys wrote:

>
> > Does this mean a single field update, results in an
> > update of the entire Row? For some reason I thought
> > TIB_Query only issued an update for Field A in
> > prior versions.
> >
> > How can I force the internal generation of a SQL
> > update for the changed/updated fields only ?
>
> Hans,
>
> When you do this:
> SELECT * FROM ATABLE
>
> and set RequestLive to true then IBO will generate insert/edit SQL
> that updates ALL updatable fields returned from the select.
>
> To only update changed fields IBO would have to prepare new statements
> with every insert/update - and it is prepares where the performance
> hits are experienced.
>
> If you only want certain fields to be updated then you can...
>
> * Change your select to only return the
> needed fields (recommended anyway)
> OR
> * Set all other fields to ReadOnly
> OR
> * Write your own EditSQL statement
>
> I am not sure what your concern is over updating the entire row. The
> only impact of any significance this has is that server based defaults
> will not be applied during an insert (so use the TIB_Query
> DefaultValues property). There will be almost no difference in either
> network or server performance in updating a single field versus the
> entire row.
>
> HTH
>
> Geoff Worboys
> Telesis Computing
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/