system xtod on sco file size limit?

[Nancy Palmquist]

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?  
> 

Scott,

I have found on some systems it is a speed issue that the OS had not yet 
written all the records exported to the hard drive in time for the next 
function.

After Export make sure you CLOSE the export to get everthing written.

You might try a short SLEEP here maybe SLEEP 100.

Then do the SYSTEM xtod

But better yet - write the EXPORT so you don;t need to do xtod.

(I have found that if I do an EXPORT ASCII -x type export and just tack 
chr("13"){chr("10") to the end of the record, I can avoid this step.

SMALL NOTE:  I always format my EXPORTS to end with CR/LF - they always 
need to go to WINDOWS computers and it just saves time and trouble.

Then when you move this file to DISK, WINDOWS, etc, make sure you do not 
change the LF to CR/LF - some mechanisms do automatically.

Nancy



-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com