LIST.2 is a variable inside your databasic code.  EXECUTE runs some TCL code
and is not privy to your databsic variables.

I presume you want to concatenate LIST.2 to the end of the execute command
and not include it in the string

-----Original Message-----
[] On Behalf Of Bill Brutzman
Sent: 29 July 2011 23:14
To: U2 Users List
Subject: [U2] UniBasic SELECT

In an inherited  legacy app, I have a few commands like

      LIST.1 = 1 
      LIST.2 = 2 
      LIST.3 = 3 
      LIST.4 = 4

        SELECT  F.ICC  to  LIST.2
        SELECT  F.ICC  to  LIST.3
        SELECT  F.ICC  to  LIST.4

And then LIST.2   LIST.3   and  LIST.4  show up in loops such as ...

         readnext CLASS.KEY from LIST.2 else EOP = 1 until EOP = 1 DO

         read R.ICC from F.ICC, CLASS.KEY else go Get.Next.Class.Key

The red warning marks on the right of the Rocket BDT IDE indicate...
"expecting INTEGER, found LIST.2"
Notwithstanding the red warnings, the program compiles and runs ok.

When I try to encapsulate these commands with

        Execute " SELECT  F.ICC  to  LIST.2"

The red warnings go away... the program runs ok but, I get a SQL+ prompt
after the report prints which can be resolved by just hitting <Enter>.

I do not want my end users to have to deal with (for them) an unusual SQL+

Suggested work-arounds to make the SQL+ prompt go away would be appreciated.

U2-Users mailing list
No virus found in this message.
Checked by AVG -
Version: 10.0.1390 / Virus Database: 1518/3793 - Release Date: 07/28/11

U2-Users mailing list

Reply via email to