COMMON variables and Windows (AREV Specific)
At 03 OCT 2001 11:13:13AM Daniel Rebich wrote:
How can we set up our own set of global variables that are loaded when a window is started and are available to any program that is called from a Pre or Post process on that specific window. We have set up a record in SYSINCLUDE and declared the variables as COMMON. How do we get the window to load them?
Thank You
Daniel Rebich
At 03 OCT 2001 11:47AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Why not just use the various global register variables declared in Window_Common%?
World Leaders in all things RevSoft
At 03 OCT 2001 01:01PM Daniel Rebich wrote:
Doesn't the Windows interpreter expect specific values to be stored in those variables? I am looking to create some system wide global variables that are always available to programmers as they write programs or create windows. That is, we would always know the global variable tdn$_today_d4 would be equal to 10/03/2001, etc. Programs would not have to create a variable for this date. All that would have to be done is $INSERT SYSINCLUDE, recordname or something to that effect.
Thanks
Daniel
At 03 OCT 2001 01:09PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
The registers (5 per prompt 10 per window) are there for your own use - see http://www.sprezzatura.com/revmedia/v3i8a20.htm and http://www.sprezzatura.com/revmedia.htm.
World Leaders in all things RevSoft
At 03 OCT 2001 04:51PM Jonathan Bird wrote:
As I read it, you need to use labelled common. For instance, I set up this labelled common in the very first programme that my users run, as they log in to Arev:
common /%SYSTEM_STUFF%/ COMPANY.NO,USERNAME
The two variable, COMPANY.NO and USERNAME are then avaialble all through the system, wherever a programme or subroutine has the line of code included in it.
Jonathan
At 04 OCT 2001 09:51AM Todd Meuth wrote:
Hi Daniel
I use the system @USER variables quite often when I need to access something system wide.
Todd Meuth
Illinois Lottery
At 04 OCT 2001 10:30AM Dave Harmacek (Harmacek Database Systems) wrote:
The window registers are for your own use. The Revelation programmers promised not to use them! I use them if I want data to automically dissolve when the window is closed, and, if the data is useful only within that instance of the window. They are not exposed to programs at another EXECUTE level.
Labeled Common Variables remain in memory for the entire session. I use them for data like Who is logged in, what privileges do they have, and so on. Suggest you use this. Remember that the number of variables is significant, not the actual variable names in the common. Also, you cannot add a new variable without having everyone leave ARev and restart. So, just reserve a few extra variables for expansion. Finally, note that Labeled Common Variables have nothing to do with any window. Unlabeled Common is taken over by each instance of any window.