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

Sorry guys.  I thought I had mentioned that before, but I traced back
through my messages and found that was not the case.  I was trying to pare
down the problem.  I figured that, once I got the data into the Access
database, I was fairly home free.

Here's why.  What we do now is update the Access database in a "local"
location, then we FTP that file to the web site.  FTP is a POC.

So, then, based on what you said about linking, I would have to change the
transfer to leave the .mdb file on the web site, and FTP the .csv (or
other?) files, that the Access tables link to, to the same system (folder)
as the Access table resides on.  I will have to talk to our webmaster about
setting up something like that.

Bottom line: Still not directly linking to the AS/400.  If I can get past
that error message ("You cannot use ODBC to import from, export to, or link
an external Microsoft Jet or ISAM database table to your database") that
Access threw at me, and keep the table definition so that it doesn't lose
it's column names, I should be all set.

Whatcha think?

db

> -----Original Message-----
> From: pctech-bounces@xxxxxxxxxxxx / Michael Naughton
> Sent: Wednesday, October 20, 2004 4:55 PM
>
> 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,