I also omitted the quotes around C:\TEMP in my example. I do not believe they are required.
Thanks Emmitt,
As I read your reply I was saying to myself: "but I copied & pasted that code from R:Syntax"... so I looked at R:Syntax before writing this reply:
You're right, of course, so I must have added the "=" sign when I added my "if...else". On the other hand, my PC does have a "C:\Temp" directory and the ENVVAL does exist (both TEMP & TMP) so R:Base _should_ only ever use the first option which is written correctly.
Nevertheless, I'll correct & trace it and try the section of code again for a few days...
Regards, Alastair.
----- Original Message ----- From: "Emmitt Dove" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, July 14, 2003 10:13 PM Subject: [RBASE-L] - Re: RBw65.exe has caused an exception
> Alistair, > > In your code below, you have: > > SET SCRATCH = 'C:\TEMP' > > I would have written that: > > SET SCRATCH C:\TEMP > > Note the differences. You could be having problems because R:Base has not > correctly interpreted the SET SCRATCH. > > > >I've been using the code below for ages but I remmed it out a few days ago > >following Emmitt's message. > >Definitely many less crashes since doing so. > > > >SET VAR vTemp TEXT = NULL > >SET VAR vTemp = (ENVVAL('TEMP')) > >IF vTemp IS NOT NULL THEN > > SET SCRATCH .vTemp > > ELSE > > MKDIR C:\TEMP > > SET SCRATCH = 'C:\TEMP' > >ENDIF > > > >It causes more problems because the $$$ files now reside in with the > >databases which I don't like and they don't _always_ get deleted. > > > >I had been trying to keep my C: drive for programs and working files with > >the D: drive for real data. D: gets backed up regularly, C: only when > >changes require it. When I back up now I get the unwanted/undeleted $$$ > >files. > > > >Regards, > >Alastair. > > > > > > > > > >----- Original Message ----- > >From: "Emmitt Dove" <[EMAIL PROTECTED]> > >To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > >Sent: Thursday, July 10, 2003 1:11 PM > >Subject: [RBASE-L] - Re: RBw65.exe has caused an exception > > > > > > > It may not be the only explanation, but we have found that such errors > > > often relate to issues with the location where R:Base is attempting to > > > write scratch files. Sometimes when we have SET SCRATCH set to a temp > > > folder the third click in a forms-based menu system will result in the > > > error; undo the SET SCRATCH and the problem stops. > > > > > > >I have a client that has the latest version of 6.5++. They are > >experiencing > > > >a great increase in the number of time rbase crashes with the above > >error. > > > >When looking at the Dr Waqtson log it is always an access violation. The > > > >machine is a new 1.7gz with 2 gig of memory running win2000 professional. > > > >The problem seems to occur when a command file is selected off of a APP > >pull > > > >down. The comand file starts executes a few lines of code then crashed. > >When > > > >I trace the command file it runs without a problem. > > > > > > > >Any ideas? > > > > > > > >rich > > > > > > Emmitt Dove > > > Manager, DairyPak Business Systems > > > Blue Ridge Paper Products, Inc. > > > 40 Lindeman Drive > > > Trumbull, CT 06611 > > > (203) 673-2231 > > > [EMAIL PROTECTED] > > > [EMAIL PROTECTED] > > > > > Emmitt Dove > Manager, DairyPak Business Systems > Blue Ridge Paper Products, Inc. > 40 Lindeman Drive > Trumbull, CT 06611 > (203) 673-2231 > [EMAIL PROTECTED] > [EMAIL PROTECTED] >
Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT 06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED]
