Hi
a couple of things I see
> IF vDCT = vLCT THEN
I was taught that you need the dot on the right expression
IF vDCT = .vLCT THEN
also what is the status of these vars prior to the while
are they null or due the exist at all
add these lines above the while
set v vDCT integer
set v vLCT integer
also
> SET VAR vDCT = 0
the if statement is using vDCT and vLCT but your sets are vTCT and vDCT
what about vLCT?
also
> FETCH movload into vMOVLC
doesn't have an indicator variable
ie. FETCH movload into vMOVLC i1
Ben Johansen
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Ken Godee
Sent: Thursday, April 26, 2001 1:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Infamous I> prompt
It's pretty simple stuff usually easy to find what's causing it
but I too am mystified
WHILE SQLCODE <> 100 THEN
IF vDCT = vLCT THEN
SET VAR vTCT = (.vTCT + 1)
SET VAR vDCT = 0
ENDIF
SET VAR vDCT = (.vDCT + 1)
FETCH movload into vMOVLC
ENDWHILE
> I'm stuck with an "I>" prompt problem.
> The program I'm writing has two while statements, one nested and
> within the nested while there's an IF Then that compares two vars.
> It's this IFThen that keeps blowing out to the "I>" prompt.
> I've ran into the "I>" prompt before, usally it's a syntax problem, well
> I've tried every variation that I can and still have problems. If I run
> the program under "trace/debugger" it runs fine. So you would thing
> that using the "SET WHILEOPT OFF" might help but it does not.
> I've tried using a WHILE instead of a IF THEN but then it blows out
> to a "w>" prompt.
> This happens under dos or win 6.1, if anyone has any ideas it
> would be great before I give up and just start the program over.
>
>
The Perfect Image Graphics Co.
2429 W. 12th St.
Tempe, AZ 85281
800-533-8732
