The problem is not connecting, that's easy with the correct drivers. The
problem is getting the data out. An AS400 doesn't understand VB(a). If
anyone can write queries in the a programming language that the AS400
understands they shouldn't have any trouble doing this. With the excel
connections that I use IBM provided an module to install in excel to convert
the queries for me. If I knew enough about C++ I could write my own for
AutoCAD or hack into the one for excel but I'm not that far into knowing it
just yet. Also all my VB.net,C#, C++, VS.net compilers are on my personnel
workstation at home, the AS400 is at work. There is a free site that I can
use to connect to an AS400 to practice with, but my time is limited right
now and the status of our AS400, at work, is up in the air right now.
Murph
"Norman Yuan" wrote in message
news:4202c04d_3@newsprd01...
> It has nothing to do with AutoCAD/VBA. As long as you have correct OLEDB
> provider/ODBC driver installed, there is no problem to access it. If you
> can
> transfer data to Excel, there is no reason you could not get the same data
> from VB/VBA.
>
> Say, With Excel, you click menu "Import Data...", the Wizard will lead you
> to select a ODBC DNS if it has been created on the computer before, or
> lead
> you to create one. If the ODBC data source name can connect to AS400, your
> ADO connection object in VB/VBA Code surely can be opened against the DSN.
>
> Personally, I never worked with AS400, But I know there are so many VB/VBA
> programs work with AS400 as data source.
>
> "Murph" wrote in message news:42026403$1_2@newsprd01...
>>
>> "DanLandrum" <> wrote in message ...
>> > I searched on this and seen some OLD topics but I was wondering if
> anyone
>> has tried puling info from AS400 using AutoCAD VBA and got it to work?
>> >
>> > Any info would be appreciated...
>>
>> Yes, tried and tried and tried again.
>>
>> NO I can't get it to work all the time the way it should (or the way I
> think
>> it should)
>>
>> A lot of it is the security issues on the AS400 and the data type we use
>> here. Client Access works Ok but that's about it. What I ended up doing
>> is
>> transfer the data to excel then connect that to AutoCAD.
>>
>> Murph
>>
>>
>
>
