revdb_init

[K]

On a different note is there a error dialog I can use to pass the system execptions to (provide more user friendly messages) ?


Kevin


-==-=-=-=-=-=-==-=-=-=-=-=-=-=-==-=-=-=-=-=-
Disclaimer:

Any resemblance between the above views and those of my
employer, my terminal, or the view out my window are purely
coincidental. 
Any resemblance between the above and my own views is non-deterministic.

 The question of the existence of views in the absence of anyone to hold
them
is left as an exercise for the reader. The question of the existence of
the reader
 is left as an exercise for the second god coefficient. 
(A discussion of non-orthogonal, non-integral polytheism is beyond the
scope of this article.)



 --- On Wed 06/16, K < nnoydb at excite.com > wrote:
From: K [mailto: nnoydb at excite.com]
To: janschenkel at yahoo.com, nnoydb at excite.com, use-revolution at lists.runrev.com
Date: Wed, 16 Jun 2004 20:31:39 -0400 (EDT)
Subject: Re: revdb_init

<br><br>Actally, I contacted RR support attempted that exact fix and I still experence the same error (I already triesed this sine I found it ina posting). Here is my last respsonse to RR support.  They requested I send the stacksInUse to then and add that script to my preOpenStack.<br><br><br>RR Support response:<br><br>Yes, that is correct the sub-stack Reconciliation is invoked by using 'go' in turn the Reconciliation stack (in its proOpenStack) starts using secfilings.rev.<br><br>Executing stacksInUse from the preOpenStack of card 1 of stack DSMS reveals the following<br><br>DSMS<br>libBasics<br><br>(This means that the code in use never actually does anything)<br><br>libBasics is a set of very simple set coordination functions and DSMS is the startup/program stack.<br><br>Kevin<br><br>-==-=-=-=-=-=-==-=-=-=-=-=-=-=-==-=-=-=-=-=-<br>Disclaimer:<br><br>Any resemblance between the above views and those of my<br>employer, my terminal, or the view out my window are purely<br>coincidental. <br>Any resemblance between the above and my own views is non-deterministic.<br><br> The question of the existence of views in the absence of anyone to hold<br>them<br>is left as an exercise for the reader. The question of the existence of<br>the reader<br> is left as an exercise for the second god coefficient. <br>(A discussion of non-orthogonal, non-integral polytheism is beyond the<br>scope of this article.)<br><br><br><br> --- On Wed 06/16, Jan Schenkel < janschenkel at yahoo.com > wrote:<br>From: Jan Schenkel [mailto: janschenkel at yahoo.com]<br>To: nnoydb at excite.com, use-revolution at lists.runrev.com<br>Date: Wed, 16 Jun 2004 03:59:30 -0700 (PDT)<br>Subject: Re: revdb_init<br><br>--- K <nnoydb at excite.com> wrote:<br>> <br>> <br>> Is there a way to aquire the program/startup stack<br>> name when a library stack receives savingStandalone?<br>> If so I can just have my library stacks set a<br>> property "RevolutionLibraryModule" with it's short<br>> name then clear it when I receive savedStandalone.<br>> So I can execute a start using when necessary.<br>> <br>> <br>> My configuration is as listed below.<br>> <br>> <br>> Standalone stack DSMS.rev<br>> Sub stack Reconciliation card Enities<br>> Secfilings database interface (a main stack)<br>> secfilngs.rev<br>> <br>> <br>> The secfilings stack is encountering the error.<br>> <br>> K<br>> <br><br>Hi Kevin,<br><br>Your conclusion is correct, you are bumping into a<br>current design limitation in the engine. However, you<br>can apply the same approach Revolution uses to allow<br>all stacks access to the externals, by adding your<br>standalone mainstack to the stacksInUse.<br>To avoid message path conflicts, it is strongly<br>advised to move all unnecessary handlers out of the<br>standalone mainstack's stack-script (for example, by<br>moving a number of handlers to the script of the first<br>card).<br><br>After that, insert the following piece of code into<br>the script of the first card of the standalone<br>mainstack :<br>--<br>on preOpenStack<br>  if the short name of this stack is not among the<br>lines of the stacksInUse<br>  then start using stack (the short name of this<br>stack)<br>end preOpenStack<br>--<br><br>This way, all mainstacks opened from your standalone<br>application will have access to the externals that you<br>added to your standalone.<br><br>Hope this helped,<br><br>Jan Schenkel.<br><br>=====<br>"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)<br><br><br>		<br>__________________________________<br>Do you Yahoo!?<br>Yahoo! Mail Address AutoComplete - You start. We finish.<br>http://promotions.yahoo.com/new_mail <br><br><br>_______________________________________________<br>Join Excite! - http://www.excite.com<br>The most personalized portal on the Web!<br>

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!