🚀 go-pugleaf

You are wrong, at least what concerning MS Access and ADO (or Client Cursor
Engine in OLEDB). MS Access does not support batch updates, they could be
done only on ClientCursor. I will citate "Optimistic Remote Updating in the
Client Cursor Engine" article from "Microsoft Data Access Technical
Articles" help file:

"In optimistic remote updating, the key to the complexity is that the CCE
does not "own" the data it is ultimately updating. Instead, the data is
owned by some specific provider, and the CCE must submit update requests in
the form of SQL commands. (This is also sometimes referred to as query-based
updating, or QBU.) "

So, data are not updated directly, but by executing SQL commands. Parsing
SQL command takes much more time then just updating data and batch updatings
on ClientCursor could be 100-1000 times slower then inserting rows on server
cursor.

"David Barnes" <david@kalos-inc.com> ???????/???????? ? ???????? ?????????:
news:3C34767A.1060706@kalos-inc.com...
> Plz correct me if I am wrong, but when you append to a table, isn't the
> table being refreashed after every append?! This would make it slower.
>
> If you are posting this way, maybe set cachedUpdates to true first. This
> will allow you to make all appends on your machine in memory(stored
> client side) then when all post have been made, you can write all
> transactions in a single post. I would think that might be abit faster.
>