× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: csv output from cpytoimpf
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Mon, 15 May 2000 12:31:30 -0600

Lance,

You have to set the code page for the output file before you run your 
CPYTOIMPF.  Look 
at the MOV and CPY commands.  I use a base file like ASCII.CHR which has a code 
page of 
367 and CPY this file to my CPYTOIMPF target.

David Morris

>>> Gwecnal@aol.com 05/15/00 10:19AM >>>
> It's not a matter of life and death for me, but it's bizarre how cpytoimpf
> seems to follow its own path for the comma delimited format.  I'm belaboring
> the obvious here, but CSV is _supposed_ to be a standard for file exchange.

Amen, brother.  As long as we are on the topic - in order to get an exterally 
described file into a comma delimited ASCII format that Excel can read, I 
have to do a CPYTOIMPF followed by a CPYTOSTMF.  If I do the COPTOIMPF direct 
to a stream file (which is an option) I get garbage because there is no place 
for the CVTDTA table.  Am I the only one who has to do this?  TIA, Lance  

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.