PBSearch is written in PowerBuilder and works equally well with versions 8 and above as well as PocketBuilder. This is possible because it uses the ORCA interface of the version it is working on, not the one it is built with.
There are two installs to choose from, one compiled with PowerBuilder 10 and one with PowerBuilder 10.5. You should use the version that is different than the PB version you are using it with. This is to avoid build number issues.
The installation includes a few PowerBuilder runtime .dll files. Your system path or PBSearch AppPath registry entry must contain the path to runtime files for the version(s) of PowerBuilder you intend to use PBSearch with.
In addition to the PowerBuilder runtime, the following files are also included:
|
Pbsearch.exe |
Main executable |
|
Pbmain.pbd |
Remaining PB objects |
|
Pbeditor.exe |
Custom text editor program |
|
SciLexer.dll |
Text editor control |
|
Pborcapi.dll |
Custom ORCA interface (ANSI) |
|
Pborcapiu.dll |
Custom ORCA interface (Unicode) |
|
Pbcontext.dll |
Performs context search |
|
Zlibwapi.dll |
ZLIB compression library |
|
Pbsearch.chm |
This help file |
|
Pbsearch.doc |
This help file converted to Word format |
|
Dwquery.txt |
Sample Datawindow query |
I recommend that you add an icon for PBSearch to your PowerBuilder
toolbar. I use the
icon on my toolbar.
PBSearch has a command line argument to tell it which version of PowerBuilder to work with. If this argument isn't given, a window will pop up asking which version to use. This choice is stored in the registry so the next time it won't need to ask. The command line argument will override the value in the registry.
Example: C:\Program Files\TopWiz\PBSearch\pbsearch.exe /pb9
The valid values are: /pb8, /pb9, /pb10, /pb105, /pb11, /pk15 and /pk20.