Re: PFCSIG PFC/PFE Library Reuse

[Peter Brawley]

That's exactly how we use common .pbls. It works splendidly for us with 5.0.04 and with 6.5. Peter Brawley ------ Daniel Coppersmith wrote: Hi! If anyone has ever encountered any type of problem with the following scenario, please let me know. I have 3 products that are <very similar> in functionality.  In fact, only about 3-5 objects are unique to the individual products.  These objects (including the application object) are placed in their own pbl (let's call them prod1.pbl, prod2.pbl and prod3.pbl).  All the other .pbls are shared (there are about 14, including the PFC and PFE). I set up three applications each with their own library list that looks something like this: prod1.pbl, common1.pbl, common2.pbl...pfe*.pbl, pfc*.pblprod2.pbl, common1.pbl, common2.pbl...pfe*.pbl, pfc*.pblprod3.pbl, common1.pbl, common2.pbl...pfe*.pbl, pfc*.pbl If I make a change to any of the objects in a common library (or the PFC), the intent is to have it affect all applications. I know that recompiling one will require the others to be recomplied because the pbl is modified when you compile, but I don't care.  No user will have more than 1 of these applications on their machine ever.  When I deploy an update to one, I will deploy an update to all three.  Multi-developer issues are not a concern. Does anyone see any potential problems with this?  For both production release or any problems I might find when I develop (e.g. disappearing scripts when a pbl is modified by two different applications).... Thanks, Daniel