Hi,

Let's start by stating I am stuck with an Access back-end. I am stuck with a
large, unwieldy and poorly designed access back end. SQL Server is not an
option.

The large, unwieldy, poorly designed back-end I have inherited is beginning to
show its true nature, clogging up the network/server (I've yet to workout if the
bottleneck is in the network or in the processor).

I've been reading up on disconnected recordsets in ADO and using DCOM. A
possible solution could be to trigger an ActiveX exe/dll on the server which
accesses the data and passes it over the network to the client app. 

I have only seen examples of this using SQL Server. Would this work well with
the Jet engine? I am concerned about leaving too many loose ends on the server
or just making a mess. I don't really know enough about the low-level
functioning of the DB Engine to predict what it would do.

Any ideas welcome.

Charles