ActiveX DLL called from ASP

[Vincent]

I have written an ActiveX DLL containg many function calls, each of which
generates a report from database queries and returns html. However, the
number of reports has grown significantly and now the DLL is nearly 1 meg
in size. While I am able to call the routines from my ASPs with no problem,
I do not fully understand how the server handles DLL calls, i.e. memory usage,
database connections etc.

I'm wondering if I should make each report it's own DLL in order to increase
server performance and efficiency. The server is performing well right now,
but use is only going to increase. There could be as many as 100 people
accessing reports at the same time, all looking for services from the same
DLL.

Any advice?

Vincent

[Darin]

Well, if you've got 100 people all creating those reports simultaneously,
you'll still have 100 reports getting created, whether or not you break em
down into seperate DLL's.

Worse, if you break em down, are you going to put all the shared code (I
assume you must have some code shared between all those reports) in it's own
DLL? If you don't, you'll end up with multiple copies of that code loaded,
one for each seperate dll you create.

I think your real issue is with the database connections. What you're
needing is object pooling. VB can't do it normally, but you can get ADO to
pool connections so long as you keep at least one CONNECTION object alive.
In this case, your VB objects will be created and destroyed but you can
reuse the ado connections as long as the connection string is EXACTLY the
same. Check for ADO connection pooling on MSDN for more.



"Vincent" <vgagliano@wkhs.com> wrote in message
news:3a86c94c$1@news.devx.com...
>
> I have written an ActiveX DLL containg many function calls, each of which
> generates a report from database queries and returns html. However, the
> number of reports has grown significantly and now the DLL is nearly 1 meg
> in size. While I am able to call the routines from my ASPs with no
problem,
> I do not fully understand how the server handles DLL calls, i.e. memory
usage,
> database connections etc.
>
> I'm wondering if I should make each report it's own DLL in order to
increase
> server performance and efficiency. The server is performing well right
now,
> but use is only going to increase. There could be as many as 100 people
> accessing reports at the same time, all looking for services from the same
> DLL.
>
> Any advice?
>
> Vincent
>