One area I can think of that my area of code doesn't cover is to actually make it's own directory. I have wondered if this would be needed, but I have had such good luck with the code, that I haven't pursued it. It would be a good idea that when it gets down to the part where it is just going to use the same directory rbase resides in to change it to create the c:\temp directory, check for it's existence and then use it. I have always thought in the back of my mind that this would be better, but alas, I hate to fool with code when I know it's working.. Too many other projects on the table.
Jim
Alastair Burr wrote:
Jim & Mike,
Jim, I've not had time to peruse your code yet but thanks, I'll check it out tomorrow. Mike, we've been there & discussed that already. I still find that CrashGuard saves me more than it causes problems - at least with R:Base. More often than not, I can save an R:Base session with CrashGuard, at least, enough to save and exit and re-start. That said, it's _very_ rare for anything else to crash.
If v7 ever materialises I'll try it without C/G first...
Regards, Alastair.
----- Original Message ----- From: "MikeB" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, July 22, 2003 6:56 PM
Subject: [RBASE-L] - Re: Setting Scratch, scratch files and R:Base crashes
----- Original Message ----- From: "Jim Limburg" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, July 22, 2003 7:41 PM
Subject: [RBASE-L] - Re: Setting Scratch, scratch files and R:Base crashes
