..Before I set sail..Active .EXE / .DLL

[longyp]

..Before I embark on a new route to improve the performance of my code.(actually, get it working)..need some advice.

I have a INPROC DLL which essentially scans a number of different Access MDBs and executes a query on the dbs and returns comma delim. results.

Big issue..large MDBs..Query takes a long time and locks out the app. using the DLL.

Reading about Active .EXE it sounds possible to place the database querying code into a seperate EXE app. which will perform asynchronously notifying my client when the query has finished so the client can go about refreshing his display etc etc. without any hang ups.

Am I on the right track here..if so..any recommendations where I can read up on Atcive EXE, how to implement, running this stuff across more than one PC, etc etc etc.

Thank you in advance.

[jim mcnamara]

Most db rs requests complete synchronously. You have to get around that.

In other words, you have to implement an asynchronous design.
Then an out of process server will do what you want. This will not help other processes being locked out for long times. You may want to reduce transactions to singles. Get a lock, mess with one transaction, then commit it. Iterate over the recordset.
MTS excels at this. MTS is a freebie from MS.

Also, - try reading VB COM from Wrox Press - there is a lot about setting up MTS, ActiveX EXE from a VB point of view.