Razzak, I turned the SCRATCH off because we have many connections through terminal services using a thin client. I was ruling out that there was a problem with their configuration. I haven't seemed to have gotten as many reports from users that they are having resource issues. It hasn't been long enough for me to state categorically that this has solved the problem. It does seem to have helped.
Thank you for your suggestions for trying to resolve the issues. Any possibility that those blues clues will ever make their way into your help files. Thanks, Dee -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Tuesday, April 06, 2010 8:49 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Resource Errors At 11:15 AM 4/6/2010, Dee Georgeson wrote: >We turned SCRATCH off last week. Dee, Is there a particular reason to turn the important R:BASE SCRATCH setting to OFF? FWIW, by default, R:BASE configuration files include the TMP for SCRATCH setting. This default will allow R:BASE or Oterro sessions to use the user's TMP environment settings for SCRATCH files on startup and eliminate all issues related to setting the SCRATCH directory and related files. To take advantage of this setting, use the option "SCRATCH TMP" in the appropriate R:BASE and Oterro configuration files or use the "SET SCRATCH TMP" command in your application startup files. SET SCRATCH sets the drive and directory location for temporary (.$$$) files created when working with TEMPORARY Tables/Views, and SORTing data. * SET SCRATCH ON to store temporary sort files on the database drive and directory. * SET SCRATCH TMP to store temporary files in the Windows TEMP directory. * SET SCRATCH <path> provides the path to the location where TEMP files are stored. You can use the SCRATCH command in the configuration file so that the setting is made prior to launching R:BASE. Having said, here are my suggestions regarding your original post asking for suggestions and help: . 235 -ERROR- Insufficient space to process command Revisit that specific routine for missing ENDIF, ENDWHILE, ENDSW. . 2110 Resources required by command are not available. Revisit that specific routine for using DECLARE, DROP, UPDATE, or DELETE commands. . 2440 -WARNING- Unavailable resource encountered during command. Revisit that specific routine for using DECLARE, DROP, UPDATE, or DELETE commands. If using Server (SATTACHed) tables with R:BASE, re-assess the user access/privileges. That should certainly give you some blue's clues ... Very Best R:egards, Razzak.
