In my experience, Packages work fine as long as you compile and distribute
your entire software system together. Packages fall down if you want to be
able to distribute a *part* of your system independantly of the main
portion.
Translation: If you've found a bug in your invoicing package, you can't just
resend the package, you'll have to recompile and resend everything.
Kerry S
>Rohit commented:
>
>> We did think of that. The problem is that the package loader is just
>> too smart. Units that werent referenced in the app when it was
>> compiled are unavailable at runtime even if the package contains them.
>
>Have a look at the ftp://ftp.delphi.org.nz/DUG/pkgdemo.zip (12KB) as it
>contains some sample code from Inprise that show how you can dynamically
>load and unload forms and other components from a package at runtime. The
>demo application loads from from a package into an MDI window and handles
>all of the issues surrounding this area.
>
>Once I had found this and looked at how they managed things life because a
>lot easier 8-)
>
>Cheers, Max.
>
>---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
