"Tom Spink" <th**********@ntlworld.com> wrote...
Could you provide a bit more information on what your app does?
I was searching around but nobody put it quite that clearly :-)
Basically the current setup includes an .EXE that is installed on the
database server. A client application (also .EXE) can reference a .DLL that
resides on the client also instantiating objects. Those objects can send
data to and receive data from the .EXE on the server via byte streams.
The .DLL would have a CreateObject() call with the name of the server and
object I need created and once I have the reference I can tell it to send me
the data I need.
Neither the client .EXE or the client-side .DLL knows about ADO or where and
how the data is stored. The data streams are reconstituted into objects on
the client side and that's all the client knows about.
Gosh I hope this isn't something they plan on adding in the future :-)
In case anybody asks, this isn't a web server, it isn't accessed by a
browser and I don't want HTML back. I might be able to work with XML but
that isn't as handy as the way it currently works.
Thanks,
Tom