Thanks for the reply. I may just try doing this. Typically though the SQL
toolkit uses ODBC on your machine to talk to an Oracle client on your local
machine. That machine in turn talks to the database specified via a socket.
What the client does I don't know? Its a good point though, I have the IP,
I'll just fire an SQL off and see what happens.
What really is making me mad is that TestStand and CVI has no problem with
Oracle 8i, only the LabVIEW SQL Toolkit. So you wonder why NI just doesn't
creat the LabVIEW SQL toolkit out of a CVI dll? Baffling.
Jim
Johannes Niess wrote:
> James Morrison/Joan Lester writes:
>
> > Hello,
> >
> > We recently upgraded our databases from Oracle 7 to 8i (8.1.6).
> > Immediately fo
und out that LabVIEW SQL Toolkit is not compatible with
> > the shipping version of Oracle. If you have a VCHAR field over 255 the
> > toolkit reads garbage. NI admits to this and is working on an ADO
> > upgrade version due out ? that will fix all of these problems. In the
> > mean time I am wondering if anybody controls SQL through some other
> > application under the control of LabVIEW? Got any ideas or knowledge of
> > an alternate SQL method let me know.
> >
> > Regards,
> >
> > Jim Morrison
>
> Jim,
>
> My knowledge about SQL and Oracle is quite limited, but it should use
> a TCP/IP connection between Client and Server like (nearly) all
> services do. You just open a TCP connection to the right port, do the
> login procedure, fire off your SQL commands, wait for replies and
> close the connection.
>
> Commands are expected to be plain text, so the SQL Toolkit should not
> have any "black magic" in it. It's just a question of time and money
> to roll your own SQL Toolkit.
>
>
Johannes Niess
