ENG0015 line 0, illegal opcode 79 (OpenInsight Specific)
At 07 JUL 2000 07:55:09PM John Yanik wrote:
I am receiving a fatal runtime message on a program that was running fine last week. The error is ENG0015 program name, line0. illegal opcode:79.
I have tried creating a new stored procedure, copied in the source code lines from just above the declarations in the program that is failing and I still receive the same error even though the program compiles fine.
I am running version 3.2 of Open Insight for workgroups. Any suggestions on how to go about correcting the problem.
At 09 JUL 2000 12:59AM Richard Hunt wrote:
the error message you got was interesting. i am not clearly sure what caused it exactly. i do know a good reason why i happened.
see if you were to have a statement in your program like this…
REMOVE STRING FROM STRINGS SETTING MORE
should be...REMOVE STRING FROM STRINGS AT POS SETTING MORE
it would cause an error ENG0015 line x, illegal opcode 221.
so your problem is similar. see one line in your code is compilable. the compiler accepted it. and yet when you run it, it causes the error message.
try to look for an error in the sytax of one of your sentences in your code. thats the best i can tell ya.
At 09 JUL 2000 08:11AM [email protected] onmouseover=window.status=why not click here to send us email?;return(true)" wrote:
Are you using UnAssigned?
World Leaders in all things RevSoft
At 09 JUL 2000 10:52AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Opcode 79 does not exist in OpenInsight, as you've no doubt determined by now. Either this is old ARev code running in OI, which does use this opcode, there are errors suffucient enought to cause bad compilation, but not enought to fall over on syntax errors, or something is corrupting the record on the read or write.
My bet is that the compiler is not catching the particular error in the code and is generating invalid opcodes for output.
Is the code small enough to post?
[/i]World leaders in all things RevSoft[/i]
At 10 JUL 2000 08:15AM John Yanik wrote:
Thanks for your help, a section of code had been added to the program from our old Arev system. Sure enough it was a problem, found it as soon as I knew what to look for.