Advanced PowerBuilder

HomePrevious Lesson: Breakpoint On a Variable Change
Next Lesson: Editing Breakpoints

Breakpoints in Embedded SQL

Embedded SQL has its own restrictions. For the purpose of Stop Points, PowerBuilder reads all declaration statements as no-go areas. It means that a SQL declaration statement, which might include cursor and/or procedure declaration is read the same way an integer declaration is read�no Stop Points allowed. PowerBuilder also has problems with embedded SQL statements that span multiple lines.

Clearly, due to the way the SQL is structured, it doesn't make sense to stop a program half-way through the SQL statement. You either need to read the SQL statement or none at all, and so PowerBuilder won't allow you to place a Stop Point between the first and the last lines of a multi-line embedded SQL statement. If you want to set such an SQL statement as a Stop Point, double click on the last line. For example, to set a Stop Point on the following SQL statement, you would double click on the line that contains the FROM clause, the line that has the SQL statement terminator:
SELECT "product_master"."product_no",
       "product_master"."product_balance" 
   INTO : lProductNo, :lBalance 
   FROM "Product_master" ;
HomePrevious Lesson: Breakpoint On a Variable Change
Next Lesson: Editing Breakpoints