Compiled Program location (OpenInsight Specific)
At 07 JAN 2002 03:38:57PM Mark Ford wrote:
I copied, corrected and compiled an AREV program in OI. The compile was sucessful. I now wish to use it as the commuter program for an OI form.
I defined a form with one field. Specified a "click" event for the field and then attempted to define a link to my commuter program. I was unable to do this as the program was not included in the Procdure list popup.
What do I need to do to ensure my copied/converted AREV programs are included in the list?
Thanks,
Mark
At 07 JAN 2002 03:47PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
It should be in the procedure list as then name given after subroutine/function. In other words
Function MarkFord(Branch, Param2)
compiled in account SurveyIt would showup in the stored procedures list as
SURVEYIT*STPROCEXEMARKFORD so if you procedure was ] R the strong chances are it wouldn't show in OI16 as the list truncates. The Sprezzatura Group World Leaders in all things RevSoft
</QUOTE> —- === At 07 JAN 2002 05:59PM Donald Bakke wrote: === <QUOTE>Mark, As Sprezz indicated, the list truncates. However, you can manually add the program name once you know the structure. We usually select a name from the list and then just change the actual routine name. This problem will also exist if you copied the program to an application that is inherited by your development system. We have several routines in SYSPROG that won't appear in this list when we are working within a client's system. dbakke@srpcs.com SRP Computer Solutions, Inc.
</QUOTE> —- === At 07 JAN 2002 06:04PM Mark Ford wrote: === <QUOTE>Andrew, Thanks for the reply. I am using OI 3.7.2 The program name is rp_sm_driver. I will rename the program to "rp" to determine if the length of the program name is the cause of the problem. Mark </QUOTE> —- === At 07 JAN 2002 07:56PM Robert Lee wrote: === <QUOTE>Hi Mark I assume you are in the quick event area and quite logically are choosing the Execute a Procedure option. To get a full list, you can use the General Option, then click on the upwards pointing arrow next to the left and vertically between the Accept and Close buttons. Then scroll down on the left hand side and Double Click on Stored Procedure Executables. This will give you a list of stored procedures that are not truncated. Robert Lee </QUOTE> —- === At 07 JAN 2002 08:32PM The Sprezzatura Group wrote: === <QUOTE>Mark, If your commuter routine has the same name as your form you can also specify a program in your quickevent as '@WINDOW' eg: If you have a TESTAPP application with a form called FORM1 you create a commuter routine called FORM1. Then in the quickevents, when you specify the procedure to call, use: TESTAPP*STPROCEXE@WINDOW
instead of
TESTAPP*STPROCEXEFORM1 When the quickevent executes, the system swaps out the literal '@WINDOW' in TESTAPP*STPROCEXE@WINDOW with the contents of the real @Window variable and calls the routine with that same name. Cool eh?
This also has the advantage that it appears at the top of the Stored Procedure list in the quickevent dialog too, so you don't need to search!
World leaders in all things RevSoft