Re: ADO vs. Progress Bar
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Sep 2005 12:18:37 +0100
Hatim wrote on Sun, 25 Sep 2005 02:09:02 -0700:
> It seems that your suggestion in the first reply is satisfying my
> requirements. I mean:
>> Is it using an ADO object like a Recordset?
>> If so, you want the FetchProgress event.
> So let us focus on the FetchProgress event for a recordset object. I feel
> that it is my need.
> Thus, consider these lines of code:
> 1 Dim Conn As New ADODB.Connection
> 2 Dim rs As New ADODB.Recordset
> 3 Conn.Open "A Connection string"
> 4 rs.Open "A SQL Statement", Conn
>
> My problem here is that when the program reaches line 4, the application
> become very heavy. It takes a lot of time for the application to wake up
> (from 15 to 60 minutes depending on the network connection, the SQL
> statement, Server status, etc.).
> So my need here is to show the progressing status of data retrieving to
> the end user. I hope it is clear now.
>
You need to set the option for asynchronous record retrieval. Look in the
help for references to
adAsyncExecute
adAsyncFetch
adAsyncFetchNonBlocking
along with the FetchProgress event.
Dan
Dan
.
- References:
- Re: ADO vs. Progress Bar
- From: Stephen Howe
- Re: ADO vs. Progress Bar
- From: Stephen Howe
- Re: ADO vs. Progress Bar
- Prev by Date: Re: ActualSize returns -1 for Text fields
- Next by Date: How to see if database/table contents have changed? (more inside)
- Previous by thread: Re: ADO vs. Progress Bar
- Next by thread: ADOX copy database
- Index(es):
Relevant Pages
|
|