On our 3.1 system, @C @ANS=XLATE( … )@ pasted a default into a window prompt. Now we've upgraded to 3.12, it does not work. Any ideas of an alternative?

It doesn't work because way back when, I found and documented that the 'C' code was what was causing so many screens to crash with an 'out of variables' error. What happens is that if you use a 'C' code, every time you save, delete, refresh, etc. the screen loads NEW copies of all symbolics on top of the old ones. For some reason, the 'C' code causes AREV to 'forget' it already loaded them. RTI's 'solution' was to do away with the 'C' code in windows.

You can accompish the same thing either by writing a program that calls RTP5 and compiles the code like the ! item in a !file and then execute it, or you can write a subroutine and pass it parameters and execute off of them. (call it as a subroutine or a conversion - doesn't matter.)

Larry Wilson

tardis@earthlink.net

Andrew,

I happening exactly the same, I had to change all

my default prompts, I made a subroutine that evaluates a

expresion that I write in the prompts register.

Default prompt @S CALC_REGISTER,3@

Prompt register 3 is XLATE(…)

SUBROUTINE CALC_REGISTER(BRANCH)

…

…

EXPRESION=WC_SI%

…

…

@ANS=XLATE(….)

RETURN

Victor Borbolla

vborbolla@gfiora.spin.com.mx

I remember checking on this and calcalyst, the function in question, creates an expendable subroutine.

However, C was not taken out of windows. It works using other structrues, but fails when @ANS is in place. I'd wager that someone put in code looking for the next occurance of @ instead of taking from pos 2 to the end so the code is incomplete and @ANS never set, therefore it fails.

akaplan@sprezzatura.com

Sprezzatura, Inc.

test@test

View this thread on the forum...