Why cant I have this variable? (OpenInsight 32-bit Specific)
At 27 NOV 2003 11:58:43AM Colin Rule wrote:
I am trying to use a variable called SC_VISIBLE in a stored procedure.
I get the following message when it compiles
Suspected mistyped syscom vars SC_VISIBLE
It was OK for me to have this variable in an event, but I have now moved this code to a procedure, and it does not like it.
Any ideas?
Colin
At 27 NOV 2003 08:04PM Steve Smith wrote:
Can you alter the variable name? There is an obvious conflict with OI's internal naming of system common variables.
At 28 NOV 2003 03:50AM Colin Rule wrote:
Yes, I can rename the variable, and have done so.
I have not included any system equates in my procedure.
If you have a procedure with just SC_VISIBLE=1 it fails.
I was allowed to have this variable in an event, so I doubt it clashes with any system variable.
I think I need a better explanation.
Makes me scared that there is some flakey goings on behind the scenes.
Colin
At 28 NOV 2003 08:06AM Oystein Reigem wrote:
Colin,
What is it that fails?
Tried what you did in my 4.1.2.
- Compilation doesn't fail, but there is a warning. (There is a similar warning Suspected mistyped equate that I get very often and have learned to ignore)
- Execution of a function that contains a line SC_VISIBLE=1 doesn't fail either.
- Oystein -
At 28 NOV 2003 10:29AM Colin Rule wrote:
Yes, it does compile, with the warning.
It does fail in my program however and does not do the function I require.
Changing the variable name has resolved, and I will live with it, but it is a pretty poor excuse that you cant use yur own variable in your own code. I can understand it if I used some OI equates, but I have not.
Colin