I have no problem getting Database Manager, Reporter, or Editor to run once via script from a button in my main window. However, when I push that button or either of the other "utility" buttons, nothing happens - as if something was not cleaned up after the last RUNWIN execution. If I execute one of my stored procedures, which exeucte fine after the utility, then I can "reexecute" one of my utillity buttons. What do I need to do so that I can execute - say editor twice- or editor then reporter, etc.??????????????

David,

Using OI 3.7, I was able to create a form with two buttons. One button lauched Report Designer, the other System Editor (both not available in a runtime engine). They both launched fine for this window.

Here's the code, for example, that I put on one of the button's CLICK event to launch reporter:

<code>
declare function utility
yes=utility("RUNWIN", "c:\revsoft\oinsight\reporter.exe /AP=COPYF /UN=COPYF")
RETURN 0

</code>

Shutting down Reporter, then clicking on the button again launched Reporter again. It would not, however, launch two Reporter's at once, as expected.

Let me know if I'm misunderstanding you here and if you could post your code, it may help as well.

-Stephen

Here is the entire and exact contents of my click script for the EDITOR button. Remember this button is on my main application window! As I said, the button executes the first time only unless I execute a non-RUNWIN process in between.

DECLARE SUBROUTINE UTILITY

DECLARE FUNCTION Set_Status

EQU SETSTAT_OK$ TO 0

UTILITY("RUNWIN","DWB.EXE /AP=:@APPID:" /UN=:@USERNAME:" /PW='")

Stat=Set_Status(SETSTAT_OK$,,);

RETURN 0

[notag]Stephen

Why do you say you can't use the DWB on a runtime?

[<A HREF="mailto:amcauley@sprezzatura.com" onMouseOver="window.status='Why not click here to send me Email?';return(true)">Andrew McAuley</A>]

[<A HREF="http://www.sprezzatura.com" onMouseOver="window.status='Why not click here to visit our web site?';return(true)">Sprezzatura Group</A>]

[<I>World Leaders in all things RevSoft</I>]

[<img src="http://www.sprezzatura.com/zz.gif">]

[<script language="javascript">function openNewPage () {window.location.href=(document.TOCNavigator.pageToGoTo.options[document.TOCNavigator.pageToGoTo.selectedIndex].value);document.TOCNavigator.pageToGoTo.selectedIndex="0";}end hiding from non-JS browsers –></script>] [<FORM ACTION "" METHOD=GET NAME="TOCNavigator" <SELECT NAME="pageToGoTo" SIZE=1 onChange="openNewPage()"> <OPTION>Why not check out some of Sprezzatura's sample apps on-line now? <OPTION VALUE="http://www.sprezzatura.com/Sample.htm">Sample Applications <OPTION VALUE="http://www.sprezzatura.com">Home Page <OPTION VALUE="http://www.sprezzatura.com/whatsnew.htm">What's New <OPTION VALUE="http://www.sprezzatura.com/senl.htm">SENL <OPTION VALUE="http://www.sprezzatura.com/patches.htm">Download S/LIST <OPTION VALUE="mailto:support@sprezzatura.com">Send mail to support at Sprezzatura <OPTION VALUE="mailto:sales@sprezzatura.com">Send mail to sales at Sprezzatura </SELECT> </FORM>][/notag] </QUOTE> —- === At 12 AUG 1999 03:19PM Kurt Baker wrote: === <QUOTE>Re: Why can't you launch DWB in a Runtime. Well, the System Editor is most commonly used for writing and compiling scripts - which you can't do in a Runtime. That is what Stephen is refering to. Kurt </QUOTE> —- === At 12 AUG 1999 03:38PM David McGehee wrote: === <QUOTE>I have this BOTH on my development environment and on my deployed app. The problem is the same. Also, I have duplicated the problem with a secondary window initiated from the main window. I am sure that there is something basic (no pun intended) that I am missing but I haven't been able to find anyone who can point it out! </QUOTE> —- === At 12 AUG 1999 04:08PM David McGehee wrote: === <QUOTE>The editor is also used to execute RDKINSTALL, ATTACH_TABLE, ALIAS_TABLE, etc. </QUOTE> —- === At 12 AUG 1999 07:06PM Stephen Revelation wrote: === <QUOTE>David, I may be misunderstanding you a bit but here's what I did: 1) Created a blank form (my MAIN application window) 2) Put two buttons on it (one to launch Reporter, the other System Editor) 3) I took you exact code, placed it on both buttons' CLICK event and witnessed the same behavior as my previous response. I even had a third button, which lauched a second form I made, which had another utility (Reporter) button. From the main form, I launched System Editor from the button noted earlier, opened the second form from it's button, then on this second form launched System Editor from the button I created on it using your exact code. Everything is working as expected. Is there more you could tell us? -Stephen </QUOTE> —- === At 13 AUG 1999 10:34AM David McGehee wrote: === <QUOTE>I don't know what else to tell you except that I am running the development environment @ version 3.7.2. My window is not a child window nor is there any MDI Frame, my initial window is a regular window. I am not using the "c:\………….\reporter.exe", for example, because the environment exists on an NT Server, not my workstation. Since it executes the first time, it obviously is finding it. Did you change the function vs. subroutine for UTILITY? Did you change the event script return 0 line? I am at a loss but I know there has to be something different, since yours works and mine doesn't. </QUOTE> —- === At 13 AUG 1999 03:46PM Stephen Revelation wrote: === <QUOTE>David, Again, I used your exact code (copy and paste). I really don't know what else to do except for you to try the same in a new application and new window (your pseudo Main application window) and try for yourself. I suspect there are other processes, events, etc. particular to your application interfering so I am at a loss as well. Perhaps deleting the entities (buttons and associated events in the SYSREPOSEVENTS and SYSREPOSEVENTEXES tables) as well as the controls themselves, exiting OI (to be extra safe), reopening the application and recreating the buttons and events with the same code you posted may help. I really don't have much else to offer, as the problem has not been reproducible. Good luck, Stephen </QUOTE> —- === At 13 AUG 1999 04:16PM David McGehee wrote: === <QUOTE>What operating system are you using? I am under NT4.0. I have replicated the situation under the same development environment with the examples sample application. I will try later with a fresh install off of the CD. </QUOTE> —- === At 13 AUG 1999 04:36PM Stephen Revelation wrote: === <QUOTE>David, Originally, I had tested this on Win98. I just completed testing and the behavior is identical on WinNT40 as I witnessed on Win98. -Stephen </QUOTE> —- === At 14 AUG 1999 02:48PM akaplan@sprezzatura.com - Sprezzatura Group wrote: === <QUOTE>Are you running in a seperate session? What happens if you switch that setting and try again? No NT here, but I just duplicated in 3.7.2 on Win98 and it all worked fine. akaplan@sprezzatura.com Sprezzatura Group </QUOTE> —- === At 16 AUG 1999 09:04AM David McGehee wrote: === <QUOTE>I am running NT4.0 workstation. I am only running one instance of the development environment. The actual .exe is on a separate NT 4.0 Server. The situation is exactly the same whether I am running the development environment or the deployed runtime application which is on another NT Server. The runtime is 6 user and the development is 2 user. We are set up for NT Service but are not using it because our through-put drops to about 20% of the straight product. </QUOTE> —- === At 16 AUG 1999 09:55AM akaplan@sprezzatura.com - Sprezzatura Group wrote: === <QUOTE>What I meant was there is a check-box on the shortcut that tells NT to create a new memory session for this application. Run in seperate memory space, or something like that. Not that I've seen this cause real problems, though I tend to have it checked anyway. Anyway, that wouldn't have been the problem because I duplicated it. All you really need is the one button called DWB. Had a second button that just did a qe to a msg so the editor would display again. Checked the return value from Utility and got some interesting results. First time, utility returned D:\OPENIN~1\LATEST\DWB.EXE /AP=SYSPROG /UN=SYSPROG /PW=' 8702 9503 9255 Second time, when it wouldn't work, utility returned DWB.EXE /AP=SYSPROG /UN=SYSPROG /PW=' 2 0 0 After running the other button, clicking back on the editor button displayed the editor and returned these values D:\OPENIN~1\LATEST\DWB.EXE /AP=SYSPROG /UN=SYSPROG /PW=' 9198 9255 12159 According to my copy of BRFHELP, field 1 should be the fully qualified path name of the called app, field 2 is an instance handle, field 3 is a module handle and field 4 is a task handle. Seems to me that these values can not be loaded. However, what I found even more interesting is that when this worked, field 1 contained the full drive/path for DWB while when it didn't, it just started off with DWB without any drive or path. So, I went and chanced the code and added Drive() : "\" in front of the call giving <code> RetVal=Utility( "RUNWIN", Drive() : "\DWB.EXE /AP= : @AppID : " /UN= : @UserName : " /PW=' " ) </code> and sure enought it loaded every time. So, I'll leave it to the kind folks at Revelation to explain why this happened, but at least now you have a work-around. akaplan@sprezzatura.com Sprezzatura Group </QUOTE> —- === At 16 AUG 1999 03:21PM David McGehee wrote: === <QUOTE>THANK YOU, VERY MUCH!!! IT WORKS!!!! I was beginning to wonder if I was going to get anyone to say anything but, "Mine works". I had run out of things to say to describe the situation so that it could be duplicated. Thank you, again, I appreciate it very much. </QUOTE> View this thread on the Works forum...