At 08:38 21.02.2003 +0000, you wrote:

>Perhaps you are right, but I would think "a DSQL statement for just
>the updated columns should be constructed and immediately executed"
>means skipping the prepare stage. For example, a table with many
>large fields, it will save traffic by only sending the changes
>instead of all data fields. If you use one prepared update statement,
>you will send all data fields.

Well, I think this is what PreparedEdits is all about. If PreparedEdits is
true, then as you say all data are sent for each update. If it is false,
then a new DSQL statement is constructed every time with only the changed
fields (and the PK) sent to the server. But this ad-hoc DSQL still has to
be prepared before being executed.

Set