Hi Michael,

I don't read this statement the same way as you do. Everything has to be
prepared, there is no way you can escape that. The difference as I expect
it to be, is that with PreparedEdits set to true, the DSQL will be
constructed once, updating all columns in your query. This way, you only
have to prepare once and all subsequent edits will use that prepared DSQL.
With PreparedEdits set to false, I expect the query to make a new DSQL
statement (and prepare it) every time you make an update. The benefit of
this is that only updated columns are transferred (i.e. less network
traffic), the cost that a new statement has to be created and prepared
every time.

HTH and that I've understood things correctly,
Set

At 10:03 20.02.2003 +0000, you wrote:

>Dear all,
>
>Even though I set PreparedEdits to false, the Query still prepare the
>update statement before executing it. From the Help, it said:
>
>"This property determines whether all updates are performed through a
>prepared DSQL statement or whether a DSQL statement for just the
>updated columns should be constructed and immediately executed (the
>default)."