|
John,
Try to save it to an Excel file first.
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
On Thu, Oct 15, 2009 at 3:41 PM, jmmckee <jmmckee@xxxxxxxxxxxxxx> wrote:
OK, this is just getting weird. I am looking at the imported file in Excel. Nicely separated into columns. When I click the icon for "Transfer data to Iseries", I get a box stating"There must be an active worksheet to perform this function". Looks active to me. I guess there is another definition for what constitutes an active worksheet. Any idea what that might be?
John
-----Original message-----
From: Luis Rodriguez luisro58@xxxxxxxxx
Date: Thu, 15 Oct 2009 14:31:55 -0500
To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
Subject: Re: CPYFRMIMPF error 98
John,--
In this particular case, if you can open it with Excel, could you upload it
to the iSeries using the Client Access Excel add-in?
Regards,
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
On Thu, Oct 15, 2009 at 2:50 PM, jmmckee <jmmckee@xxxxxxxxxxxxxx> wrote:
I have received a file from an outside agency that chokes CPYFRMIMPF. The--
fields are pipe delimited. I have looked at the raw file and don't see
anything REALLY obvious - the file is several hundred lines long. I can
open this thing in Excel just fine, but there is no option to save it with
pipe delimiters. There is a free text portion, which, I suspect, prompted
the need to use the pipe as a delimiter.
The agency has converted this file multiple times, and the results are the
same. Other files are just fine. When I attempted to use an error file, I
got nothing in the created member.
Is this why some of you loathe CPYFRMIMPF? Any suggestions on how to
isolate and fix the error(s) causing CPYFRMIMPF to choke? Not sure I have
the time to write the program to split this thing apart. Can SQL be used in
some way to identify or clean up the file?
John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.