>Can I use same set of pbds (framework PBDs) in two different applications.
This issue was flogged to death here not too long ago, but since you
asked...
Yes, it can be done. We have deployed many apps globally over the last year
using this method. The PFC/PFD/PFE PBDs are shared between all the
applications. Some of the applications also share application layer PBDs.
As you probably hope, it does allow very neat deployment. Applications
which would otherwise be deployed as a dozen or so PBDs and EXE are now
deployed as one or two PBDs and EXE. Since we also don`t use ini files, we
even have a few apps (small but non trivial) which deploy as a single
smallish EXE and nothing else, which is nice :-)
Hmm, I must dig out my notes to recall why we didn`t deploy the PFC/PFD/PFE
as DLLs rather than PBDs... I know there was a particular propblem.
I detested the old approach where people were copying the 'core' PBLs from
one app, renaming them, prehaps tweaking them slightly and making them
unique to the second app. Then you ended up with multiple copies of
libraries which were very similar but only worked when regenerated within
the correct app etc etc etc.
We had few problems with the PBD sharing approach (well so far at least).
You do have to be careful to have the same inheritance tree in all the
sharing applications, and no trying to copy ancestor objects out to
descendant level to make things behave differently in each app etc etc. But
then, you wouldn`t be coding like that anyway, would you? Also, if you make
mods to shared ancestor libraries you will obviously be wise to rebuild all
the dependant apps.
Regards,
Nigel
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
