RE: Using File Transfer Add-in in Excel with a macro

["Chris Payne" <CPayne@xxxxxxxxxxxxxxx>]

It records both but some things are un-recordable for whatever reason.
Chris

-----Original Message-----
From: midrange-l-bounces+cpayne=thecrowngrp.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+cpayne=thecrowngrp.com@xxxxxxxxxxxx] On
Behalf Of Booth Martin
Sent: Tuesday, January 24, 2006 4:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: Using File Transfer Add-in in Excel with a macro

Doesn't a macro record key strokes, not mouse moves?


Ken Slaugh wrote:
> I'm willing to bet that the CA/400 Excel add-on doesn't code the macro
> for you. Instead try using ODBC, I know that does code the macro for
> you.
> 
> Hth, Ken 
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Landess
> Sent: Tuesday, January 24, 2006 12:07 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Using File Transfer Add-in in Excel with a macro
> 
> All -
> I am by no means an Excel expert, but I'm trying to learn...
> 
> Is there a trick necessary to use the iSeries Access file transfer
> add-in within an Excel macro?  
> As a test:
> 
> 1) I created a new macro named "Macro1" by selecting Tools -> Macro ->
> Record New Macro from the Excel Toolbar 
> 
> 2) Then I selected Data -> Transfer Data from iSeries, and selected
and
> ran the file transfer to pull the data into the spreadsheet.
> 
> 3) Then I stopped macro recording.  
> 
> However when I try to run it nothing happens, and I went into the
Visual
> Basic Editor for the module this is all that i find:
> 
> Sub Macro1()
> '
> ' Macro1 Macro
> ' Macro recorded 1/24/2006 by Steve Landess '
> 
> '
> End Sub
> 
> Regards,
> Steve Landess
> Austin, Texas
> (512) 423-0935
> --
> 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.
> 
>