"Dick Kusleika" wrote ...

The problem is that the Workspace object is falling out of scope

In ADO, Recordset is a top level object, so you don't need to
preserve the connection.

That's right. The Recordset has an ActiveConnection property which
retains a reference to the Connection object.

If you switch to ADO, you'll have to mess with some of the properties of rs
in the function to mirror the dbOpenDynaset that you use now.

The 'dynaset' is known to the non-DAO world as a keyset cursor e.g.
CursorType=adOpenKeyset in ADO.

I think
you'll need to change the CursorLocation property, but I'm not sure about
that.

To use a keyset cursor in ADO, the cursor location must be server
side.

Jamie.

--