Run Impact Analyses in a Treeview for PowerBuilder

  1. First, you need a Visual Expert project up and running.
    If needed, you can find a getting starting guide here.
  2. In the treeview, select the item changed.
    For instance, a database column.
  3. In the navigation bar, click on “Impact Analysis”
  4. All the objects using this column are shown in a
    container hierarchy, to help find and edit them.
  5. Select 1 object: its code is displayed,
    and references to the column are highlighted
Check Impact Analysis for PowerBuilder Code Changes

How to Run Impact Analysis from Source Code?

  • Right click on an item in the source code.
  • Click on [Impact Analysis (Tree)].
    Impact Analysis from Source Code View
  • The results open in a new tab.
    Impact Analysis Result from Source Code

Where is a Column used in my PowerBuilder Code?

A column has changed: what's the impact on my code?

Find all references to a column or table.
Make sure your application never breaks when your Schema evolves.
Check PowerBuilder Code Impact Analysis

Which PowerBuilder Objects are Supported for Impact Analysis?

You can find references to any code item, as long as it belongs to a language supported by Visual Expert: objects, methods, variables, tables, columns, views, procedures, triggers, packages…

Below are some additional examples:

Where is a Stored Procedure called in PowerBuilder Code?

If I add a parameter to a method: which code should I update?

If the prototype of a PB or Database must change,
you can find instantly all the calls to this method - both in PB and DB code - and update them.
Impact Analysis for Stored Procedures in PB Code

Where is my variable referenced in PowerBuilder Code?

Impact Analysis for Variables in PowerBuilder Code

Where is a PowerBuilder Object referenced?

Impact Analysis for PowerBuilder Objects

How to review PowerBuilder Dependencies with DLLs?

Integrate with third party software.

Example: compiling your PB application to 64 bits require calling 64 bits dlls.
Track all dependencies to 32 bits dlls, and call 64 bits dlls instead.
Impact Analysis for PowerBuilder Dependencies with DLLs


Visual Expert 2021, PowerBuilder, Code Analysis, Impact Analysis