
Design Question: Call .dll from SQL Server VS MTS
I'm converting an Access 97 front/back to an Access 97 front/SQL Server
Back. In addition I've moved some functionality into a .dll which
resides on the server and which I am able to call from SQL Server using
sp_OACreate, sp_OAMethod etc.
Initially the functionality handled by the .dll required no user input
and was called on a timer from SQL Server. However there are some
functions I need to give the front end access to. I could simply have
the front end call a stored procedure which would call the function in
the .dll and return a pass/fail. Or I could set up MTS and have the
front end call the .dll on the server directly. Only I have no
experience with MTS. It appears I would have to spend considerable
time setting up each client computer to use DCOM. On the other hand
passing everything through SQL Server seems unorthodox and may not
scale well . . .
Does anyone out there with experience with these two methods of
accessing a VB .dll have any suggestions?
Thanks,
George
Sent via Deja.com http://www.*-*-*.com/
Before you buy.