-
Because an ActiveX DLL runs in-process, would it be nearly as efficient as if I had the same code compiled within my application? I know you'd do a dll if you had common code that was lengthy, but I have a couple of snippets that are only 5 or 6 lines...I'd rather not cut-and-paste it every time, but I don't want to put a drag on the system either. Thanks for any direction. ;)
p.s. One of the dll's wouldn't receive any arguments and would pass back a string; the other dll would receive a dsn string and pass back an ado connection object.
-
Look at it from the point of view that if the code is re-usable across multiple projects, then a DLL is the way to go, although for two procs, it's probably overkill. Why not put it into a module that you can add to all your projects.
DLL's should generally encapsulate code that is related, so a series of functions to handle ADO connections would make a nice DLL - you can then spend a bit of time raise decent error messages, etc. But a whole series of unrealted code snippets is probably better suited to being used in a module (or even a class in you project if it requires that sort of instantiation)
- gaffa
-
That clears things up for me. Thanks gaffa ;)
