Re: CursorLocation for Execute Method
- From: "Philip Siaw" <nospam@xxxxxxxxxxxx>
- Date: Sat, 18 Nov 2006 10:09:01 +0800
Dear Bob,
Thank you very much for your answer.
By the way, this is my first post.
"Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx> wrote in message
news:ed8DhBkCHHA.3524@xxxxxxxxxxxxxxxxxxxxxxx
Philip Siaw wrote:
I guess I do not fully understand the effect of setting the
CursorLocation to adUserServer or adUseClient when calling the
Execute method.
I was trying to call the Execute method for the following SQL
statements: 1) INSERT
2) UPDATE
3) DELETE
There is no cursor when calling these statements. So CursorLocation has
absolutely ZERO effect. This has been stated several times to you. Why do
you make us keep repeating it? (I hope i am not confusing you with another
person who was asking similar questions)
The ONLY time a cursor is involved is when using a SELECT statement.
The reason for using adExecuteNoRecords is that the default behavior for
the Execute statement is to construct a Recordset object in memory in
which it will place any records that are returned by the statement's
execution. Using adExecuteNoRecords saves cpu and resources when executing
a DML statement that does not return records.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- Follow-Ups:
- Re: CursorLocation for Execute Method
- From: Bob Barrows [MVP]
- Re: CursorLocation for Execute Method
- References:
- CursorLocation for Execute Method
- From: Philip Siaw
- Re: CursorLocation for Execute Method
- From: Bob Barrows [MVP]
- CursorLocation for Execute Method
- Prev by Date: ADO corrupts date time values in where clause
- Next by Date: Re: CursorLocation for Execute Method
- Previous by thread: Re: CursorLocation for Execute Method
- Next by thread: Re: CursorLocation for Execute Method
- Index(es):
Relevant Pages
|
|