Re: automagically import a .CSV into Access db table from CL?

I'm with Adam - what's the internet got to do with it? As I understand it,
and ODBC link is between the client (PC) and the host (AS/400). If you set
up a link  on one PC and then move the database to another PC, it won't
work unless you also set up the link on the second PC.

It's basically as secure as signing on to the AS/400 from your PC. The
biggest security hole, usually, is that ODBC (of course) bypasses any sort
of menu security, so if your files are wide open the person using the ODBC
connection could theoretically trash them. But you can set up connections
to be Read Only, and you can set up a user profile with very limited
access to use for the link (the ODBC link requires a user name and a
password, just like any other connection to the AS/400), so you can lock
it down pretty tight if you want to.

Setting it all up is really pretty simple. Obviously, if you''ve never
done it before, there's a learning curve, but it's a small one and you can
get all the help you need from this list. Unless you've come up with
something pretty simple already, I think it's worth considering.

jmho,

PC Technical Discussion for iSeries Users <pctech@xxxxxxxxxxxx> writes:
>Here's the deal.  It will be a cold day in h*ll before an internet user
>can
>directly touch our data on the iSeries.  So, the Access-->ODBC-->iSeries
>file link is out.  It may well be that this can be secured, but we do not
>have the expertise in-house to do it and know that we are secure.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx