Bob,

I believe that this is sort of a "bug" in MS handling of remote views -- however the MSKB article, Q191343, that seems to deal with this says the behaviour is by design.

To avoid the connection busy error with remote views set maxrecords and FETCHSIZE to -1 (all). These can be set by modifying the query and going to the Query menu item --> Advanced Options page. Or by issuing things like:

=DBSetProp('ViewNameHere', 'View', 'FetchSize', -1)
=DBSetProp(ViewNameHere', 'View', 'MaxRecords', -1)

Hope this helps,

Kevin