Hello all,

I am using Visual Basic to open a saved query and then save
information in the query to an array for later use.  The problem is
that the same query shows different results when opened directly vs.
when opened by Visual Basic.  It is as if Visual Basic is not letting
the query fully evaluate before processing records.

The query is a subtotal query that contains several criteria set up as
"where" in the group-by box.  Most of the criteria are based on one
table, one criteria is based on a second joined table.  When the query
is opened directly this last criteria is correctly evaluated and the
proper records are shown.  When opened in VB it is as if this criteria
did not exist.  The query otherwise shows correct information except
it includes records that should not be there based on the last
criteria.

Is there a way to force visual basic to wait until a query is fully
opened before executing code that uses the resulting records.  Or is
there something else that I am missing.

Any help would be greatly appreciated.

Thanks,

Vince

Partial code Follows---------------------------------
Public aWork(10) as Integar

Sub LoadWorkArray(WorkQuery as string)  'WorkQuery = query name
Dim WorkLastRecord as Integar
Dim X as Integar

Set SLWork = New ADODB.Recordset

SLWork.Open WorkQuery, CurrentProject.Connection, adOpenKeyset,
adLockOptimistic

WorkLastRecord = SLWork.RecordCount

ReDim aWork(WorkLastRecord + 1)

With SLWork
   .MoveFirst
   For X = 1 To WorkLastRecord
       aWork(X) = ![Attending Number]
      .MoveNext
   Next X
   .Close
End With

End sub