I was having similar problems and I called Intersolve. They informed me
that I needed a server version of their intersolve database drivers.
($2,000 to $5,000). I solved the problem by using Microsoft access as a
front end database and SQL server as my backend database. This did correct
the problem. To do this open up Microsoft access (I used version in Office
2000) and create a new database file. I then added a database link to my
SQL server files. I then created a Microsoft ODBC link to this new
Microsoft access file. Presto... It worked.
--
===================================
From: John Harmon
Work Email: harmon-j@gouldis.com
Personal Email: harmonj@bright.net
Home LandLine: 330-848-0460
Work Land Line: 216-328-7113
"Chris Burgess" wrote in message
news:38df6477@newsgroups.ni.com...
>
> I am experiencing problems accessing an SQL Server 7.0 database with LV
5.1f1
> using SQL Toolkit 5.0.
>
> Everything works fine when using Access to link to the tables in the SQL
> Server DB, then accessing the linked tables from labVIEW. I can also
access
> the tables from Test Stand with no difficulties. The errors I see when
trying
> to access SQL Server directly from labVIW are as follows:
>
> When using the Microsoft SQL Server Driver (3.70.06.23) I recieve the
following
> error: "[Microsoft][ODBC Driver Manager] Program type out of range". With
> this driver, I can connect to the database, but cannot Perform a fetch on
> it. When using the LV database browser, I can see the table in the db,
but
> can see neither the attributes nor the contents of the tables.
>
> When using the SQL Toolkit SQLServer Driver (1.12.00.00), I recieve the
following
> error: "[INTERSOLV][ODBC SQL Server Driver][SQL Server]Login failed for
user
> '*******'", where "*******" is my user name. I cannot find a
> place in the Intersolve drivers setup that will allow me to enter a
assword.
> If there were a place to put a connection string, I could set the
Integrated
> Security = SSPI, and hopefully be allowed to login. But I can find no
where
> to enter such a string, even though an "Initialization String" field is
mentioned
> in the
> intersolve "Advanced" set up tab help.
>
> My preference is to use the Microsoft SQL Server Driver, since using
intersolve
> will involve additional licensing.
>
> Do you know what is causing the "Program type out of range" error that I
> am recieving?
>
> Thank you for you help.
>
> C Burgess