Posted by Tom Fulton on May 13, 2004 at 06:32:10:
Hi All,
This problem continues from the post below concerning DOSFC. I've discovered a problem that occurs with all versions of Comet2004 GT
version 332, namely 334, 335 and 336. The problem does not occur in
332 and I'm assuming lower version numbers. Neither does the problem
occur in Comet2003.
Problem:
I have a simple program, attached, that designates a Path and a filename and attempts a DOSFC file erase as per IB documentation.
Under Comet2003 and Comet2004 thru version 332 this program works -
if I have Windows Explorer up, the file displays. When I run Comet
and run program WORK2 the program returns to QMONITOR. Windows Explorer no longer shows the file. Under C2K4 334, 335 & 336 program
WORK2 runs, displays the proper path & filename & returns to QMONITOR.
However, the file still exists! It shows in Windows Explorer and it
can be opened up in Wordpad.
Additional Info: I have only tested this with .TXT text files. I have tested files both on an 'L' directory ( TMP ) and on an 'S' type
directory with identical results. My Emailing program that is grabbing the HTM file built with HTMLNOL and building an Email file,
builds the file as a TXT file on TMP, with a filename including TERM$.
The file is closed, nobody else can have the file in Comet as the Terminal number is unique, and the file is not open in an editor. As
I erase & re-create the work Email file I am now getting an exception
13 on the erase and a hard error 12 on the create because the file
is not gone. Ouch!
Thanks in advance for looking into this, Tom.