- The FetchProgress and FetchComplete events only work properly in MDAC  2 . 5  or later
-Coding Requirements
When you open the recordset, you must specify adAsyncFetch as a Recordset 
Option.
You must use client-side cursors, because the FetchProgress and FetchComplete 
events are returned by the ActiveX Data Objects (ADO) client cursor engine.
In Visual Basic, you must declare the Recordset at module level using Dim with the 
WithEvents keyword
-There are two recordset properties that affect the asynchronous behavior of 
ADO. These properties should be set prior to opening the recordset. 
Initial Fetch Size determines how many records are fetched synchronously before 
the asynchronous thread is created. This allows for a small recordset to be 
created without the additional overhead of creating a thread. This is set to  50  by 
default. To guarantee that FetchProgress and FetchComplete are called, set this 
value to  0 .
Background Fetch Size determines how many records are fetched between calls to 
the FetchProgress event. This is set to  15  by default. 

SYMPTOMS
 -The FetchComplete event is never raised.
RESOLUTION
 -If you are using a dual processor you then also need to set the  "Background 
Fetch Size"  to a low value such as  1 .