Daniel, We have tried that before with PB 50 and without pfc. It kind of worked. But then our top pbl started to grow as we added more and more objects to it, objects started to get out of sync and finally we could not wait to recompile the whole library and make top pbl empty again. Stella ____________________Reply Separator____________________ Subject: PFCSIG Someone shoot this idea down Author: [EMAIL PROTECTED] Date: 10/26/99 2:27 PM I have 18 PBDs (including PFC). When I make changes (fixes, new features), I end up needing to distribute up to 10 of my PBDs in order to make fixes cumulative. What I was thinking of doing for the next major release was to have a library called V3UPDATE.PBL that is in the top of the library list. Then, when I need to do interum updates, I will have the new objects copied into V3UPDATE.PBL as well as their regular pbls. That way, I only need to distribute the one PBD for updates. Does this seem like it would work? Will I have a problem with two same named objects out there? The users would have the new object at the top of the list so it <should> ignore the old object in the pbl lower in the list. Let me know if you can find fault with this idea... Thanks, Daniel
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.2314.1000" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV>I have 18 PBDs (including PFC). When I make changes (fixes, new features), I end up needing to distribute up to 10 of my PBDs in order to make fixes cumulative.</DIV> <DIV> </DIV> <DIV>What I was thinking of doing for the next major release was to have a library called V3UPDATE.PBL that is in the top of the library list.</DIV> <DIV> </DIV> <DIV>Then, when I need to do interum updates, I will have the new objects copied into V3UPDATE.PBL as well as their regular pbls. That way, I only need to distribute the one PBD for updates.</DIV> <DIV> </DIV> <DIV>Does this seem like it would work? Will I have a problem with two same named objects out there? The users would have the new object at the top of the list so it <should> ignore the old object in the pbl lower in the list.</DIV> <DIV> </DIV> <DIV>Let me know if you can find fault with this idea...</DIV> <DIV> </DIV> <DIV>Thanks,</DIV> <DIV> </DIV> <DIV>Daniel</DIV> <DIV> </DIV> <DIV> </DIV></BODY></HTML>
