OLE DB doesn't show up as a DSN because a DSN is an ODBC thing. Now, when using OLE DB, you can specify a DSN as part of the connection string, but then OLE DB will go through ODBC to access the data. Rule of thumb: when using OLE DB, don't include a DSN in the connection string.


>OK I think i figured it out. When I was in the control panel trying to create the DSN, it was only listing ODBC data sources, not OLEDB. When I used the SQL Server Data import/export wizard, the OLEDB sources where listed there for the source data source. That seems to work. Sorry for the confusion.