I have severals windows with "C" @code command@ invoked in default prompt in Arev 3.11 and it work very well.

Example: @C @ANS=XLATE('CUSTOMERS',{CUST_NO},'CUST_NAME','X')@

I upgraded to Arev 3.12 and I get default values equal to nulls.

Has any body a idea of what is happening?

Thanks for any help, VB.

Notice that you have three @'s in your code? I think what's happening is that the first two are being used to delimit the code and command giving you a code of "C" and a null command.

I stay away from the C code anyway because it has problems with memory managment. If I recall correctly, it allocates memory but does not deallocate it again properly. Use "S" or "L" and compile a program. It will run faster because it doesn't have to be compiled.

Actually, the problem with the C code/cmd, as was partially covered in the previous msg, is that not only does it not unload from memory, it keeps all symbolics on the stack and then loads a new set (like whenever you SAVE, DELETE or REFRESH a screen.) I found this by decompiling AREV because Alan Humphrey, the head of tech support at the time, kept saying it wasn't their problem - but I knew it was.

Their 'solution' as to disable the C code/cmd and have it return nulls. While this effectively prevents someone from using it, I seriously doubt whether the root problem, in the ASM code of the AREV engine, was ever fixed. The bottom line is, don't use C code/cmd; it doesn't work and it'll break your app.

However, the good news is that in 3.12, JA FINALLY fixed the SELECT problem that has existed in ALL versions of AREV until 3.12 (by their own admission). So, those of you using anything except 3.12; why?

[email protected] (new e-mail)

http://www.bigfoot.com/~tardis-systems (new web site pointer as I'm leaving Earthstink (err… Earthlink.)

View this thread on the forum...