Re: Help! Adodb.recordset.update vs Execute SQL statement?

From: smushran <smushran_at_nospam.us.oracle.com>
Date: Fri, 17 Dec 1999 19:54:09 GMT
Message-ID: <385a93a7.779929921@newshost.us.oracle.com>

ADODB.Command.Execute should be the more efficient option if all you are looking to do is populate the data in the database. Recordset has the overhead of maintaining the data in the local cache. However, if you are looking to read the inserted data back from the server, a recordset should be the better option.... as the data will already be in the local cache.

Sunil

On Wed, 15 Dec 1999 11:21:07 -0500, "Dana Jian" <djian_at_trasa.com> wrote:

>Hi,
>
>Now there're some choices for add new/ update record in Oracle database from
>front-end program like VB, we can use ADODB.recordset to add new/update
>record or we can use Execute to run a SQL statement directly against the
>Oracle database connection.
>
>But what's the best solution--when talk about the performance and efficiency
>??
>
>Any help/comments would be appreciated!!
>
>Dana
>dan_jian_at_hotmail.com
>
>
Received on Fri Dec 17 1999 - 13:54:09 CST