I'd like to sound out the list's views on what goes on with scratch files: As you all know, I've had endless problems with R:Base crashing since changing from Dos to Windows 2 years ago.
You also all know that a couple of things have recently made significant differences to the crashes, namely: 1) Changing a file extension from .DAT to .$$$. 2) Removing the SET SCRATCH C:\TEMP setting. Currently, I still get a few crashes but nowhere near as many. However, I noticed today that CrashGuard - yes, I'm still using it - notified a problem with a .$$$ scratch file in a directory where I didn't think there should be a scratch file. I have 5 databases in 5 sub-directories of D:\DBFiles. My start-up procedure goes to one of the sub-directories and opens its database and a form. (This is my controlling database that contains details of the other 4 DBs and backups, maintenance, etc., etc..) The form, basically, has buttons that allow access to the other 4 databases. The app that is running uses QUIT TO to change to apps that run the other 4 DBs. Generally, this all works perfectly well - except for the crashes... Before I removed the scratch setting of C:\TEMP I assumed that all the scratch files would always be in C:\TEMP. Having removed it I assumed that the scratch files would be in the respective directories for each database as and when a database is opened. CrashGuard had a problem with the .$$$ in D:\DBFiles - not one of the sub-directories. My short-cut has its start-in directory as D:\DBFiles but a database is not opened until the app changes directory to one of the sub-directories. It was set that way originally because I often opened R:Base to work on apps rather than to _run_ the apps. If anybody has had any similar experiences or problems with sub-directories I'd be very interested to hear how they were overcome. Thanks & regards, Alastair. ---------------------------------- A D B Burr, St. Albans, UK. ---------------------------------- [EMAIL PROTECTED] ----------------------------------
