** Hot News **
Web Service Structure Generator
Software Tool & Die Inc. is pleased to announce the release of its new Structure Generator (v2.0.0.1) application built from the STD Foundation Classes Integrated Framework. The Structure Generator is a development productivity aid that automatically builds corresponding parent & child structures based on any current DataWindow configuration. The resulting structures can then be directly populated from the DataWindow's primary buffer. The data filled structures can then used as a local work area or to build a Web Service result set. 
Using the Structure Generator, STD Web Service Framework and
PowerBuilder Classic's powerful DataWindow technology will have you
building effective .Net Web Services 5x faster than other development
tools in no time!For those who will be attending the 2015 PowerBuilder Convention in Charlotte, NC, USA on Thursday May 7, 2015 - the Structure Generator will be featured in the STD Foundation Classes Web Services course training session!
To download this free productivity utility, please visit its home located on the SourceForge website. Click here to download!
Regards ... Chris
Hi Chris, I couldn't find your blog on this where I can send you question I am trying to find. Sorry to write over here. My question is In powerbuilder, making incremental build of patch library (In my application we have a upatch.pbl) where we put the changed object we made and run the incremental build and create pbd file and send only this update.pbd file to client. This way we avoid to send all pbd to client. Now the problem is we get most of the time Bad Runtime Object Reference error 21. I don't understand why Powerbuilder have this issue. The solution which I know to copy all the reference objects in update library but this will increase the library size. Even we can not tell what reference would be missing until we test the whole application thoroughly. What is the best way to avoid this issue without adding reference object in upatch library. I would be really thankful to you. I had asked so many question and got respond to. I forget where I had post those question. Please send me the link where I can send you my PB issue question directly.
ReplyDeleteThanks,
Vipin 469-3058208
Hi Vipin;
ReplyDeleteYou can get away with a PBD build for one PBL if the objects inside are concrete (working) level components. If the classes in the PBL are ancestors to working level descendants then this WILL create an unstable build. The reason for this problem is when new or revised instance or shared variables are added or revised. PB then compiles a work area for these variable pools. The ancestor variable pool definition is then genetically passed done to the descendants. However, these descendants must then be recompiled in their respective PBL/PBD's. If not, there then becomes a memory mapping disconnect between the ancestor & descent. Once that happens, your application will become unstable. The only way around this is to do a full build/compile of all your PBL/PBD's in order to have PB sort out this variable memory mapping issue.
HTH
Regards ... Chris