Powerbuilder

Google Search Terms

Blank ScreenPBL Null Object Invalid Row/Column

Google AD:Powerbuilder App Changes

The Review and Changes will all be done remotely by logging into requester machine.
Required:The application must have .PBLs (powerbuilder library files) and the Powerbuilder (IDE)Development Environment
for changes to be made. The IDE 'may' be found by looking for the Powerbuilder Executable - c:\program files\sybase\powerbuilder x.x\pbxx.exe
where xx is the PB version. Should the only files found be of type PBD and/or EXE, I will not be able to help.
Depending on number of developers, experience has taught that the Powerbuilder EXE may only be on a Single machine.

Purpose for Your Search

An application was recently discovered or has been being used for an extended period of time.
It may have been in use for 10 years+, and now needs updates or resurrection. My current assignment, the original script was written in ’91.

  1. An associated product, perhaps a database upgrade has rendered portions of the application useless.
  2. Infinite loops are now a part of the application. Found this after an Oracle upgrade.
  3. A screen which had successfully delivered data reliably is now a

    Suggestions:look at the database(DB) joins, a key field may be your culprit. A field in the database has changed datatypes, a field removed or renamed. A stored procedure with an obsolete call which no longer returns results. If the original PB script did not do an InsertRow when no data found or test return codes from the DB this could also be an issue.
    Blank Window
  4. An object which does not exist NULL OBJECT
    Suggestion:The line number in the error message may direct you. Look for a


    most often associated with a datawindow object, e.g. dw_ or d_. It may
    be followed by a GetItem... or a SetItem. Should the THIS reference be in
    a window and not a datawindow script, it may be causing the issue.

    THIS

    not used correctly. An application I updated did not have an object defined before a GetItem.
    It worked previously as scripted but then started to fail after an enhancement. It will work if the object from the
    GetItem has focus(bad technique) but it is a fragile technique at best and the GetItem (or other) should
    be fully qualified.


  5. Suggestion:look at the database(DB) joins, a key field may be your culprit.
    A field in the database has changed datatypes, a field removed or renamed.
    A stored procedure with an obsolete call which no longer returns results.

    Invalid Row/Column
  6. Found may have been files of type:PBL(Powerbuilder Library) contains Source Code, PBD(dynamic link library), EXE(application), INI. However, before beginning any review, updates or enhancements it is important to check that the POWERBUILDER IDE(Interactive Development Environment) is available somewhere within the organization.
    Suggestion: look for the Powerbuilder Executable - c:\program files\sybase\powerbuilder x.x\pbxx.exe where xx is the PB version
    Should the only files found be of type PBD and/or EXE, I will not be able to help. It has been mentioned that a Chinese company has reverse engineered PBD's but I do not have experience working with this product or comments on its reliability.
    Without the Powerbuilder software rebuilding a PBD and/or EXE will not be possible. Changes would not be available for release.

Database Driven

Example, Should the request be ‘change a Report Title’ and the Report Titles are stored in the Database. It would be possible to make
the database change and see it reflected in the Powerbuilder application. However, those results are very limited.

Stored Procedures, if they are executed from the Powerbuilder code. You may be able to update the Stored Procedure on the database
side and see results in the application. This would not include changes to a result set. Adding or removing columns for the result set columns would cause an error.