[RBASE-L] - Re: I/O problems

[Jim Belisle]

I use 7.6 latest update in multi user environment.
I AM STILL PLAYING WITH MY SCRATCH SETTINGS.
I ADDED THE SUGGESTED ROUTINE.
HERE IS THE CODE:

DISCONNECT
CLEAR VAR vChkFile
SET VAR vChkFile INTEGER = NULL
SET VAR vChkFile = (CHKFILE('C:\TEMP'))
IF vChkFile <> 1 THEN
   MD C:\TEMP
ENDIF
SET SCRATCH C:\TEMP
SET ERROR MESSAGE 2262 OFF
SET ERROR MESSAGE 2926 OFF
ERASE C:\TEMP\*.$$$
SET ERROR MESSAGE 2926 ON
SET ERROR MESSAGE 2262 ON
CONNECT Labor
CLS
EDIT USING xKayParkMainMenu10
DISCONNECT
EXIT
RETURN

I get an error "File not found 2077" on startup.
Any ideas what I am missing?

James Belisle
-----Original Message-----
From: rbase-l@rbase.com [mailto:rbase-l@rbase.com] On Behalf Of A.
Razzak Memon
Sent: Wednesday, April 06, 2011 2:16 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: I/O problems

At 02:00 PM 4/6/2011, Jim Belisle wrote:

>Razzak,
>
>I have plenty of storage memory on the LOCAL drive (C:) 13 GB.
>
>There are 46 processes in use when I bring up the Task Manager.
>
>I am very unfamiliar with how the temp files affect things.
>Since the settings I now have, C:\Doucuments and settings\Jim\Local
>Settings\Temp are on C: drive, how does going to C:\TEMP make a
>difference? Just wondering since they are both on C: drive.


******** Originally posted Wed, 27 Apr 2005 23:12:38 -0400 ********

Tip of the Day: Managing R:BASE Scratch Files

It is possible to see bogus data when you PRINT a report or
SELECT from a VIEW. It must be the second time you access the
VIEW, and you usually have a different sort condition on the
second query. The bogus data displays because of the combination
of the row width, number of rows selected by the view and how
the data is placed in the pages of the SCRATCH files. Sometimes
high order ASCII characters will display on the report, but
when you look at the data in the tables it is fine.

The simplest solution is to DISCONNect and CONNECT the database
between commands to remove the old R:BASE scratch files.

Here are a few tips to automate the cleaning process of R:BASE
scratch files in your application.

01. Use the following process in your application startup file:

     Example 01:

     SET ERROR MESSAGE 2262 OFF
     SET ERROR MESSAGE 2926 OFF
     ERASE *.$$$
     SET ERROR MESSAGE 2926 ON
     SET ERROR MESSAGE 2262 ON

02. You may also use the following technique to manage R:BASE
     scratch files your way!

     Example 02:

     -- AppStartupFile.DAT
     DISCONNECT
     CLEAR VAR vChkFile
     SET VAR vChkFile INTEGER = NULL
     SET VAR vChkFile = (CHKFILE('C:\TEMP'))
     IF vChkFile <> 1 THEN
        MD C:\TEMP
     ENDIF
     SET SCRATCH C:\TEMP
     SET ERROR MESSAGE 2262 OFF
     SET ERROR MESSAGE 2926 OFF
     ERASE C:\TEMP\*.$$$
     SET ERROR MESSAGE 2926 ON
     SET ERROR MESSAGE 2262 ON
     CONNECT dbname IDENTIFIED BY userid password
     QUIT TO YourAppMainMenu.RMD
     RETURN

This technique allows you to define your own R:BASE SCRATCH
directory as well as the freedom of reading, writing and
deleting scratch files on the local workstation without
being concerned about the user rights and allocated space
on the network or mapped drive, when working in a multi-user
environment. Using this technique, you are also aware of the
exact location of R:BASE Scratch files for manually cleaning
the TEMP directory on local hard drive.

Very Best R:egards,

Razzak.