Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!sri-unix!BLC@jpl-vax
From: BLC%jpl-vax@sri-unix.UUCP
Newsgroups: net.micro.cpm
Subject: Use of dBase RESET function.
Message-ID: <15403@sri-arpa.UUCP>
Date: Thu, 12-Jan-84 18:55:00 EST
Article-I.D.: sri-arpa.15403
Posted: Thu Jan 12 18:55:00 1984
Date-Received: Mon, 16-Jan-84 01:06:20 EST
Lines: 28

From:  Bruce L. Conroy <BLC@jpl-vax>

     Although  there are some funny effects in dBase's RESET 
command I have found it to be 100% reliable under several 
versions of dBase if:

     a)   Any files on the disk to be changed are closed 
(this is merely good practice in any event,)

     b)   The disk is changed, then

     c)   The command RESET (not RESET B) is given.

     In particular, this sequence avoids the following 
anomolies:

     a)   RESET B or RESET B: or any similar command seems 
to have no effect whatever.

     b)   As long as a data file is open, there is an 
unpredicable amount of data in memory, which is not on disk. 
If the disk is changed at this point these data are lost, 
unless

     c)   There is a file of the same name on the new disk, 
in which case, the extra data are stuffed into that file,
resulting in the loss of the integrity of both data files.
------