Variable assignment problem (OpenInsight Specific)
At 29 JUN 1999 10:25:28AM Gene Sorbo wrote:
Has anyone seen the following problem in OI?
I have in a stored procedure the following:
HLTH_ACCT_STATUS_CODE=Get_Property(@window:".HLTH_ACCT_STATUS", "DEFPROP")
Value of HLTH_ACCT_STATUS_CODE should be 'A', but instead is returning null. However, if I substitute ZZZ for HLTH_ACCT_STATUS_CODE (variable name change only), I get the appropriate variable value of 'A' returned.
???
OI 3.61.
Gene
At 30 JUN 1999 08:30AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
So, in other words, your saying
Var1=Func( f1 )
gives a value but
Var2=Func( f1 )
returns null?
At 30 JUN 1999 11:49AM Gene Sorbo wrote:
Yes!
Gene
At 30 JUN 1999 12:06PM Tony Marler @ Prosolve wrote:
Gene
Sounds wierd ! I think your code must be changing this somewhere. I have actually cut your example and works fine for me using either variable name.
Or are you actually putting some text on the control (assuming it is an editline) on each example to actually give DEFPROP a value.
Tony.
At 30 JUN 1999 01:01PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
There are no real variable names in Basic+. It's sort of a trick. The compiler finds each variable in order used and defines them as Var1, Var2, Var3. Commons and labeled commons are treated similarly. The @record in SYSOBJ (the *record in ARev) holds the mapping the debugger uses to turn Var1 into MyMeaningfulVar. Thus, the variable name has no real meaning and changing it should not have any effect on the program.
It would be interesting to see this demonstrated live.
At 30 JUN 1999 01:33PM Gene Sorbo wrote:
I know this sounds weird - but it actually happens!
I have started to suspect system memory usage, and possibly a 'bad' control on a form, but have not had a lot of time to play with it yet. I also want to call the debugger and check out the variable assignments reflected there.
I'll let you know what I find.
Thanks.
Gene