Subject | DLL/BPL and app with lots of modules |
---|---|
Author | Steve Fields |
Post date | 2001-11-11T03:35:39Z |
I have been trying to research the methods and recommendations
for DLLs and BPLs but it always seems to me that the cons and the
pros even out and I am left where I was in the decision of which
to use. Perhaps someone or someones can recommend which:
What is the best way to handle an application where there may or
not be a Main module along with numerous other module that will need
to be changed from time to time. I have noticed that in IBO components
(connections, querys, etc) it is not recommended to put them in
DLLs/BPLs
but how would you handle it? Would it be feasable to place several
querys/grids/datasources in a module and when calling it pass only the
IBConnection, and maybe a keyfield value or other. I do not really wish
to have one large program (5-10 meg) but would rather have several
modules
that can be installed. (It just does not seem economical in sending out
10-20 modules that are 3meg plus for every fix/update).
In some cases I would need to distribute them on disk and sometimes
over
the internet. An initial install of several megs would be agreeable, but
the updates would need to be small. The version of Delphi would be
steady - D5E. And any updates would be exclusively by me.
Any ideas? TIA
Steve Fields
for DLLs and BPLs but it always seems to me that the cons and the
pros even out and I am left where I was in the decision of which
to use. Perhaps someone or someones can recommend which:
What is the best way to handle an application where there may or
not be a Main module along with numerous other module that will need
to be changed from time to time. I have noticed that in IBO components
(connections, querys, etc) it is not recommended to put them in
DLLs/BPLs
but how would you handle it? Would it be feasable to place several
querys/grids/datasources in a module and when calling it pass only the
IBConnection, and maybe a keyfield value or other. I do not really wish
to have one large program (5-10 meg) but would rather have several
modules
that can be installed. (It just does not seem economical in sending out
10-20 modules that are 3meg plus for every fix/update).
In some cases I would need to distribute them on disk and sometimes
over
the internet. An initial install of several megs would be agreeable, but
the updates would need to be small. The version of Delphi would be
steady - D5E. And any updates would be exclusively by me.
Any ideas? TIA
Steve Fields