Powerbuilder 12.1 and DataWindow in Design vs Debug and Executable/Runtime -


I have a very strange situation with Powerbuilder 12.1. I have two issues that can be related - mainly because this is the exact same data window report.

Problem # 1: You can not see the contents of Detavindo any and went nowhere, lost the ability to debug and display content Detavindo at runtime during the debug and runtime.

But when you go into the data window in design mode, it prompts for the values ​​of those parameters, the content is only displayed, it is okay.

Edit: Solve. This is due to a powerbiller that uses an integer rather than a long variable. The identity identifier in the database exceeds the upper limit of a PowerBuilder 16-bit integer (32767). I updated the logic for longer use, and resolved this problem # 1.

ISSUE # 2:

When I run the report code using the same data window mentioned in issue # 1 above, in debug mode, to create a new report file, this work Done - only in DEBUG mode Runtime failure - I got an error -1 during the runtime for the exact same call.

Here is DATASTORE using data snippets (I try to see already Detavindo and he also failed):

  Datastore lds_blarney_report lds_blarney_report = CREATE datastore iw_main_sheet. recover wf_write_log ( "report data") lds_blarney_report.dataobject = as_datawindow lds_blarney_report.SetTransObject (sqlca) ll_ret = lds_blarney_report.retrieve (al_file_no, "%")  

in DEBUG mode: the last line some Returns positive non-zero values ​​and a report is generated in the mode in the mode: the last line returns 1 According to Ibes Get display went number of rows returned, rows in the primary buffer) if it succeeds and -1 if it fails. If Detavando the control or datastores not assigned any Detavindo object This method returns 1 return.)

Then why has worked in debug time to create a new report file, but the runtime Unsuccessful?

It looks like you are not compiled in the DW app trying to load at run time .

There are several possibilities how this will happen:

  1. Your PBR file no longer includes the runtime referenced datawindow object. It is important to add it again.
  2. The PBR file was never found in the context of DW, but there was a complete reference wherever it was included. This reference is now gone and DW has not been included in the XE.
  3. DW once was PBD in PWL, but now it is being compiled in the app. This means that any runtime assignment for datawindows in that PBD will work without applying in the PBR file or without clear assignment in the painters.

Hope this will be helpful.


Comments

Popular posts from this blog

java - org.apache.http.ProtocolException: Target host is not specified -

java - Gradle dependencies: compile project by relative path -

ruby on rails - Object doesn't support #inspect when used with .include -