[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Repository Compile bug (OpenInsight 32-bit Specific) ====
=== At 27 JAN 2004 11:24:35AM Colin Rule wrote: ===
 
{{tag>"OpenInsight 32-bit Specific"}}
 
<QUOTE>
I have a form which I use to recompile all the entities in my application.  This is useful when I change a COMMON or Insert code etc.



I copied a Stored Procedure XXX for backup purposes to XXX_ORIG.

I then busily changed XXX to do all the stuff I wanted to, and have been doing this for months.

I recompiled the Stored Procedures, and when you call XXX, the program XXX_ORIG is in fact called.... Oh dear oh dear.



Took me ages to find this, as when you put a debug in XXX and compile to check, it of course runs the proper code again.  It was not until I put a debug in XXX_ORIG, compiled, and then ran the code that I found that the source displayed was XXX, but the line numbers were aligned to XXX_ORIG.



I think it may be to do with the first line of the SProc containing

  COMPILE SUBROUTINE XXX



Still a nasty bug, but I can work around for now by changing the first line to XXX_ORIG, so that it wont overwrite the compiled code.

Please check and fix in OI7 if possible.

I am posting here in case other users search for this and need a solution.



Colin
</QUOTE>
----

=== At 27 JAN 2004 12:03PM [url=http://www.sprezzatura.com" onMouseOver=window.status= Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>FWIW We actually rely on this behaviour - we don't bother with "New Stored Procedure" we just create and compile relying on the system to name the subroutine accurately.



[url=http://www.sprezzatura.com" onMouseOver=window.status= Click here to visit our web site?';return(true)]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>

----

=== At 27 JAN 2004 01:31PM Richard Hunt wrote:  ===

<QUOTE>Colin,



I caught that a while ago. What was happening to me was that I copied the stored proceedure from EVENTS_ENTER_EXINV TO EVENTS_ENTER_EXINV_OLD. Although I did not change the "SUBROUTINE" statement. That was the issue. My "SUBROUTINE" statement was as follows...



SUBROUTINE EVENTS_ENTER_EXINV(SUCCESS,RESULT,ARG3,ARG4,ARG5,ARG6,ARG7,ARG8,ARG9,ARG10,ARG11)



Once I changed the "SUBROUTINE" statement to...



SUBROUTINE EVENTS_ENTER_EXINV_OLD(SUCCESS,RESULT,ARG3,ARG4,ARG5,ARG6,ARG7,ARG8,ARG9,ARG10,ARG11)



It compiled correctly. Hope this helps.

</QUOTE>

----

=== At 28 JAN 2004 03:41AM Colin Rule wrote:  ===

<QUOTE>I do this too sometimes, bit it wont compile unless the filename and the COMPILE statement match.... in the System Editor.

It does however compile in the Respository compile, which I find strange that a procedure with syntax (or not) errors still compiles.



Colin

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=184352B1EB28384D85256E28005A2479|View this thread on the  forum...]]