ProDiff is designed to highlight the differences between versions of Application development source code. ProDiff improves on standard diff tools by parsing and pretty printing source code files before comparing the individual sections of the program or source code files.

This approach removes many of the false positives created when files are reorganised but not syntactically changed. ProDiff displays the results of the parsed/pretty printed source code in a hierarchical manner making the changes between the versions easier to locate and understand.

PBL Peeper (does this, but it also lets people read PBLs without the PowerBuilder IDE in a much more readable form than export files. It's been used by people like testers who needed to read the code, but didn't have the IDE.

Good luck, Terry and Sequel the techno-kitten On 22 Dec 2010 11:31:41 -0800, in sybase.public.powerbuilder.general wrote: >We are trying to provide the customer the PowerBuilder >source code for review. The problem the customer does not >have a copy of PowerBuilder. Is there any other tool to >export the source code in a text file without having to >address each object within PowerBuilder. ********************************* Build your vocabulary while feeding the hungry ********************************* Newsgroup User Manual ===================== TeamSybase Sybase employee Forums = Peer-to-peer Forums Communication with Sybase IsNull (AnswerTo (Posting)) can return TRUE Forums.Moderated = TRUE, so behave or be deleted ********************************* Sequel's Sandbox: Home of PBL Peeper, a free PowerBuilder Developer's Toolkit. Version 4.0.4 now available at the Sandbox PB Futures updated June 25/2008 See the PB Troubleshooting & Migration Guides at the Sandbox ^ ^ o o =*=. To export (dump) source. Hth Arnd On 22 Dec 2010 11:53:23 -0800, 'Terry Voth [TeamSybase]' wrote: >PBL Peeper (does this, but >it also lets people read PBLs without the PowerBuilder IDE in a much more >readable form than export files.

Mar 25, 2015 - Hi. I am bit new to powerbuilder. There is an application build in powerbuilder now I have to look to which data source its pointing to. The only file I have.pbd file. But when I open it with notepad++ it show data in some wired manner. Is there a way I can see the actual code in.pbd file? Mar 21, 2017 - These are the files containing the definition of each object used in the application. There is two ways to do this task using tool developed by our team or do it manually from PowerBuilder. One more benefit of using PBExtractor is collecting information about lines of code for each type of file and total amount. Sybase PowerBuilder is capable of opening the file types listed below. Sybase PowerBuilder Source Code Library.pbd. Sybase PowerBuilder Runtime Library.pbx.

It's been used by people like testers who >needed to read the code, but didn't have the IDE. >>Good luck, >>Terry and Sequel the techno-kitten >>On 22 Dec 2010 11:31:41 -0800, >in sybase.public.powerbuilder.general >wrote: >>>We are trying to provide the customer the PowerBuilder >>source code for review. Chivalry And Sorcery 5th Edition here.

The problem the customer does not >>have a copy of PowerBuilder. Is there any other tool to >>export the source code in a text file without having to >>address each object within PowerBuilder. >********************************* >Build your vocabulary while feeding the hungry >>********************************* >Newsgroup User Manual >===================== >TeamSybase Sybase employee >Forums = Peer-to-peer >Forums Communication with Sybase >IsNull (AnswerTo (Posting)) can return TRUE >Forums.Moderated = TRUE, so behave or be deleted >********************************* >>Sequel's Sandbox: >Home of PBL Peeper, a free PowerBuilder Developer's Toolkit.

>Version 4.0.4 now available at the Sandbox >PB Futures updated June 25/2008 >See the PB Troubleshooting & Migration Guides at the Sandbox >^ ^ >o o >=*=. I also find the PBLDump tool a great one! Here's a sample batch file to export one PBL-file in a subfolder: @echo off if '%1' == ' goto help @echo - Exporting%1 if not exist%1 goto not_found @md 'PBLEXP -%1' @cd 'PBLEXP -%1' if not exist.%1 goto delete_directory for%%1 in ('*.*') do del%%1 @pbldump -es.%1 *.* >NUL @cd. @echo - Exporting%1.