Those are left behind when: 1. RBASE crashes (does not happen very often, it usually drops to the R>) 2. User clicks the closebox to down the RBASE session 3. User turns off the power (a UPS helps prevent inadvertent power drops) 4. User shuts down windows with RBASE open 5. Network connection is lost.
In other words, any abnormal termination of RBASE or the network connection will leave these behind because RBASE does not have opportunity to delete them. _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Martin Sent: Friday, January 19, 2007 1:43 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Orphaned scratch (.$$$) files We're using a legacy rbase system (5.5 DOS). Been trying to identify causes for scratch ($$$) files being left over (orphaned) during normal operation of the database. We know that abnormal termination of the application (i.e. End Task) will do it; excessive memory leaks on platforms prior to W2K... Curious about any internal file access time-outs (if network is slow and rbase thinks it's scratch files aren't there anymore) or maybe the NOS is closing files it doesn't think are being used... Does anyone have any ideas, experience, flash backs, etc.? Thanks, Steve Martin
