system xtod on sco file size limit?

[Kenneth Brody]

scott at logicdatasystems.com wrote:
> 
> I am using xtod with the system command to change a filepro export
> to dos, then copy to a winderz pc.
> 
> The ending file size is smaller than the original.  Of course, this
> works fine from the command line.  Thinking it may be a timeing issue,
> I tried sleep "10000" after, to no avail.  Small files are ok, but
> the file testing starts as 19195 bytes and ends as 18618, and the data
> is cut off.
> 
> Is there a buffer limitation not documented?

If there is a limitation, I doubt it's as low as 19K.

You say that this is an export file.  Have you CLOSEd the file before
issuing the SYSTEM command?  If not, filePro may still have the last
part of the file buffered.

Also, "xtod" should _increase_ the file size, as it is adding a CR
for every line in the file.

> Is there a way to wait for a response from the system call
> to proceed?

filePro already waits for the program to end before continuing.  Adding
a SLEEP will have no effect on this.

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody/at\spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+
Don't e-mail me at: <mailto:ThisIsASpamTrap at gmail.com>