Re: Download Speed
From: Stephen Howe (stephenPOINThoweATtns-globalPOINTcom)
Date: 03/15/04
- Next message: Marcin Floryan: "Re: Using ADO in Access 2000"
- Previous message: Stephen Howe: "Re: MDAC error?"
- In reply to: Brock Rogers: "Re: Download Speed"
- Next in thread: Brock Rogers: "Re: Download Speed"
- Reply: Brock Rogers: "Re: Download Speed"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 22:09:22 -0000
> Thank you for your response. I verified that by setting the cursor
location to server and I call my select statement directly
(pRec->Open("SELECT * FROM XXXXX", conn, adOpenForwardOnly, adLockReadOnly,
adCmdUnknown))..
Don't give ADO adCmdUnknown. It takes longer. That should be adCmdText
.. it does indeed limit the amount downloaded. However, if I call a stored
procedure instead of a straight SELECT statement it returns all of the data
at once.
A few words.
The Connection "CursorLocation" is the default cursorlocation of a
RecordSet.
If you don't bother setting a "CursorLocation" for a RecordSet, then the
default location is whatever the Connection's is. The Recordset's
"CursorLocation" is so that you can override what is the Connection default
You don't say _HOW_ you are calling your Stored Procedure. I assume that
you have setup a Comamnd object and you are doing
rs = Command.Execute(...)
But in this case, what is the Connection CursorLocation? If it is
server-sided, I would you to get a limited number of records, same as
opening a Recordset. The fact that you are not puzzles me.
I would suggest debug printing out what the Recordset's CursorLocation,
LockType and CursorType after returning from SP.
SH
- Next message: Marcin Floryan: "Re: Using ADO in Access 2000"
- Previous message: Stephen Howe: "Re: MDAC error?"
- In reply to: Brock Rogers: "Re: Download Speed"
- Next in thread: Brock Rogers: "Re: Download Speed"
- Reply: Brock Rogers: "Re: Download Speed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|