I hate it when the cut paste does screwy things. Retry. CLEAR VAR iv%, RBTI_%, r% CLEAR VAR v% EXCEPT vmode, vpuname, vpuid, vaccesslevel, vlogin RETURN
-----Original Message----- From: "jan johansen" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 16 Aug 2010 12:47:02 -0700 Subject: [RBASE-L] - Re: Assigning and Clearing variables John, I don't know if it's right or wrong but I still have a form action that is called before and after every procedure that has the following; CLEAR %,RBTI_ %,r% CLEAR VAR v % EXCEPT vmode,vpuname ,vpuid ,vaccesslevel , vlogin RETURN VAR iv Jan -----Original Message----- From: "John Engwer" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 16 Aug 2010 15:34:22 -0400 Subject: [RBASE-L] - Assigning and Clearing variables I am trying to resolve an intermittent hang problem with one of my applications. One practice that I have used in the past was to declare most of the common variables via procedure call while at the main menu (about 90 VARS). At the end of each process I “CLEAR ALL VAR EXCEPT RB%” and then call the procedure to set the variables for the next process to be run. I am wondering if this method may be contributing to my hangs. I am sure that SET and CLEAR VARS as you go is the best technique so I plan to revise my application. But what about clearing VARS using CLEAR ALL VAR EXCEPT RB%; is there a downside to that? That would save me a lot of time when I make the changes (the application is quite large). Does anyone have any thoughts on this method? John Engwer Engwer & Associates 2449 Scenic Ridge Drive North Huntingdon, PA 15642-2120 Phone: 412 751-2433 Email: [email protected]
