Re: odbc

There are several approachs you could take to accomplish this.  Using Client
Access you could download directly to an Excel file, then import the Excel
file to Access.  A shorter path would be to import the file directly into
Access, but there is a bit more work involved in the initial setup.
    Open the Access database that you will import the file to.  Select the
tables tab and then click on the new button.  From the "New Table" window,
click on the "Import Table" button, then on the "OK" button.  In the bottom
portion of the dialog box, locate the "File of Type" drop list.  Drop the
list, scroll all the way to the bottom and select "ODBC databases".  This
will open a dialog box titled "Select Data Source".  If you do not have a
data source created, click on the "Machine Data Source" tab, then click on
the new button.  From the dialog box that opens ("Create New Data Source"),
click the radio button labeled "System Data Source".  Find the Client Access
ODBC driver (32 bit) , select it, then click on next.  In the next dialog
box, click "Finish".
    You will now have a window with a number of tabs titled "Client Access
ODBC setup".  In the "General" area, enter a name for the data source.  If
you connect to multiple systems, be sure the correct one is selected and
enter a user profile.  Click on the "Server" tab and enter the libraries you
will need to access.  Multiple libraries can be entered by placing a comma
between each library name.
    Click on the translation tab and the select the radio button labeled
"Translate CCSID 65535".  This will convert the data so you do not download
al hex. You may want to click on the "Other" tab and select the radio buttom
labeled "Read Only".  If you do not do this you have a two way gate to the
400 (more on this in a minute).  Click on OK.  Your data source has now been
created.
    Be sure your new data source is selected, then click on the "OK" button.
Your should be presented with a small signon dialog box.  Enter the profile
and password or just the password if the profile is already displayed.
Click "OK".
    You will be presented with the "Import Objects" window.  Listed will be
all the libraries (with their files).  Select the file(s) you wish to import
and click OK.  the file will show up in the table window.
    Sorry to be so long winded.  it isn't as complicated as it seems and the
data source only needs to be created once.
    A word of caution.  You can also use the data source to link to AS400
tables.  While this is convenient, it is also dangerous.  While linked to a
400 table, changing the data in the displayed Access table will also change
the 400 data !!  Be very careful if you choose to use this method.
    I hope this has helped.  Again, it sounds more complicated than it
really is.

Regards,
Steve Haessler
STRATTEC Security Corporation

----- Original Message -----
From: <Imaginor@aol.com>
To: <RPG400-L@midrange.com>
Sent: Saturday, May 06, 2000 11:18 AM
Subject: odbc


> I would like to download a '400 physical file to a microsoft access data
base
> file. An associate of mine informed me that when using client access, it
will
> take 2 or 3 steps (1. transfer data to a text file...2. map to an excel
> file...3. import to access). Using an odbc connection and definition, can
I
> map and download directly into access? if so, please explain the steps.
Thank
> you.
>
> Richard Deutsch
> Kiss Products, NY
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

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