I've been trying to connect to an Access database on a W2K on the network (not a local file, but mapped on the V: drive), via ODBC.All I got is this message: Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path. Additional Info: 64-bit version of SQL Enterprise Edition On Windows 2003 Server Another reason this might happen (just happened to me) ... I didn't realize this until I tried to remote into the actual server and was prompted to change my password.I guess that you have possibly 2 simultaneous conditions for this failure to happen: I had this issue for a server instance on my local machine and found that it was because I was pointing to 127.0.0.1 with something other than "localhost" in my hosts file.It cannot access a Access database via a mapped drive.
This sample includes source and binary for a simple XML Destination pipeline component.
You cannot make a system DSN with a UNC (\Server\resource), so you must map the drive Cute isn't it? I quit on ODBC and went via ADO, this is the code that works:=== CODE ===$db = '\\server\resource\db.mdb';$conn = new COM('ADODB.
on Windows lets you create DSNs, check driver installation, and configure ODBC functions such as tracing (used for debugging) and connection pooling.
Project Description Microsoft SQL Server Integration Services (SSIS) makes it possible to build high performance data integration solutions, including the extraction, transformation, and loading (ETL) of data for data warehousing and as well as Data Transformation Services (DTS) backward compatible support.
This project contains Integration Services samples created by the product team.