Re: connect to SQL Server without a DSN

[CAW]

Thanks for the opinion.  I agree that using a DSN has many advantages,
but it is my customer's requirement that the connection be made
without using a DSN.

Allen

Re: connect to SQL Server without a DSN

[Russ @ GE]

I won't say you have a problem with the connection string, but using a
connection defined in ODBC Administrator (thus creating a DSN) makes
the LABView code cleaner and more flexible.  It should also allow you
to verify the DB connection outside of LABView.  Once the connection
to the DB is verified, if you include the UID and PWD in the ODBC
config, you simply pass the DSN to the LV connection VI.  I connect to
DB's under a variety of DB drivers and have very reliable connections.
If the app doesn't connect, it's easy to go back to the ODBC Admin and
check what's happening.  Rarely is the problem LV related -- something
changed for the DB connection.

Happy wiring!

Russ

connect to SQL Server without a DSN

[CAW]

Can I connect to a SQL Server database without using a DSN?  I am
using the following connection string:
Provider=MSDASQL.1;Extended
Properties="DRIVER={SQL
Server};SERVER=AT-CAL\SQL1A;READONLY=0;DATABASE=Calib"
as an input to DB Tools Open Connec (String).vi.
It produces the following error:
DB Tools Open Connec (String).vi->Untitled 2Exception occured in
Microsoft OLE DB Provider for ODBC Drivers, [Microsoft][ODBC Driver
Manager] Data source name not found and no default driver specified.
in DB Tools Open Connec (String).vi->Untitled 2
Is there something wrong with this connection string?