Re: Import Excel file -- MIDRANGE-L

× 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: Import Excel file
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 17 Jan 2022 09:30:26 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Mon, Jan 17, 2022 at 9:27 AM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Mon, Jan 17, 2022 at 10:57 AM Jack Woehr via MIDRANGE-L
<midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Like I said, Vern, it's a bear

FWIW, the DTF(X)-FDF(X)-DTT(X) dance has always been exactly the steps
you describe since Client Access for the AS/400.

Thanks, John Yeung.

I got very good at this process, until eventually I decided it was
worth writing a script for it (in AutoHotkey).

I agree with your earlier comment that Python is the way to go here.

My motto of the month: "IBM is not kidding you when they tell you open
source is the only path forward on the IBM i."

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.