Jump to content


Photo
- - - - -

Binding PROIV file variable into SQL statement


No replies to this topic

#1 DARREN

DARREN

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 396 posts
  • Gender:Male
  • Location:Florida,USA

Posted 08 August 2013 - 02:14 PM

Just a heads up that I encountered this problem yesterday. It only affects screens from what one of my lead developers told me as they came across it before and diagnosed it. It is now in our list of hints and tips. Posted Image

Problems have been found in screens when comparing a previously read file variable against a file variable in an SQL statement if the variable has not been flagged as Auto Repeat.

E.g.

SQL

SELECT FROM WVSL700 WHERE WVSL700.DEALER_CODE = :DEALER_CODE

ENDSQL



If the file variable DEALER_CODE has been read in a previous characteristic but is either not used on the screen or not flagged as Auto Repeat then there is the chance that :DEALER_CODE will send a Null value to Oracle (Even though UMSGing it will report a value for DEALER_CODE).


The solution is to set a scratch variable to DEALER_CODE.
Things should be made as simple as possible, but not simpler



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users