DLL, package, or just plain units?

[JediDan]

Hello!

I have several database utilities that I have written, with many more to come... they all share the same logon screen, and several other functions/procedures. Right now, all of the "shared" code is duplicated in a unit in each project.

Does it make sense to put this stuff in a DLL? Or a package?

Thanks,

Dan

 

[colttaylor]

I wouldn't get too fancy with this kind of thing. Just move all of the common code to a single unit and put it in new directory. Then compile the new unit to a tbu and add it to each project.
The result is a single point of code maintenance but without the extra baggage of a seperate DLL file.

If the compiled code is comparitively small, I'm not bothered by duplicating it across several utilities. The only time I resort to using DLL's is when the compiled code is of significant size and size matters (got to fit everything on a floppy/zip/cd, got to minimize download time, etc.)

Hope this helps...
Peace,
Colt