That's because the file is open and hasn't been written to disk. It can't
be found in that state.
----- Original Message -----
From: <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, September 23, 2010 10:26 AM
Subject: [RBASE-L] - Re: Autochk messages
I don't see how this could work. Unless a "load from file" control acts
different than the way RBase in general does, if you go on one session and
type "output test.txt",
and then on a second session try to "type test.txt" you get a "file not
found" message until that first session has done an "output screen"
Karen
Larry iam with you. Two windows and besides a bonus backup to boot. Not
like it harms the world to have those. :/
Paul Dewey - CEO
New Horizon Safety Diagnostics
New Horizon Interlock Inc.
InterlockInfo.com
Sent by Verizon Incredible.
----- Reply message -----
From: "Lawrence Lustig" <[email protected]>
Date: Thu, Sep 23, 2010 10:09
Subject: [RBASE-L] - Re: Autochk messages
To: <[email protected]>
<<
Mike: Yeah, the first thing I thought of was the load_from_file,
wondering if I did the autochk to an output file if I could show it
somehow, but
realized quickly that you can't show the file while it is in process of
being
created...
>>
Karen:
Try kicking off a separate copy of R:Base to run the autocheck. That
copy
will run and create the file over time. While it's running, your
original
copy could use a timer to load the autocheck output file every 5 to 10
seconds.
For this to work, the autocheck will have to write the file in such a way
that it's readable by a second process while still open in the
autocheck-running copy of R:Base. If that isn't how it works, you could
use the XCOPY
command (from inside the first R:Base process) to make a copy of the
autocheck file and read from that.
This would produce somewhat choppy output, but at least it would give you
an up-to-date set of output from autocheck.
--
Larry
