With this feature, PowerBuilder developers can explore Datawindow DataSources and visualize their dependencies with the Database:
Table updated, Retrieve SQL, Stored Procedures called for Retrieve/Insert/Update/Delete, DW columns used for parameter passing etc.
This tutorial shows how to setup a Visual Expert Project including both PB + DB code (Oracle, SQL Server…).
With VE 2016 You can analyze several PB applications in a single VE project. You get a overall analysis of PB applications relying on the same ancestor libraries/framework.
VE 2016 now includes a new Oracle code parser that can analyse PL/SQL Code, as well as DDL statements (create tables, etc.).
Visual Expert 2016 also analyzes dependencies between the PB code and the database more deeply than in previous versions.
VE 2016 now includes a new Oracle code parser that can analyse PL/SQL Code, as well as DDL statements (create tables, etc.).
Visual Expert 2016 also analyzes dependencies between the PB code and the database more deeply than in previous versions.
Navigating very long pages of source code can be tedious, with Visual Expert you can now collapse parts of the Source Code to get a better overall view of your code.
This feature lists in the treeview all the Non-Visual Objects (NVO) declared as Instance Variables in a given PowerBuilder Object.
When creating a Datawindow, PowerBuilder developers specify which of the DW columns update the corresponding Database Column. This feature filters DW columns to display which of them do so.
While parsing your code, Visual Expert 2016 analyzes all accesses to tables and columns and categorizes them by type.
Visual Expert 2016 will include a new set of treeview features to review PowerBuilder Source Code. This includes both code review and code metrics tools.
