It seems security issue to me. Where is your DBC? Your SQL Server service runs under different account and your DSN imporsonates logged in users. If your DBC is on the network, this may cause and issue.

>(Sorry for the cross-post, just thought additional eyes might be able to see this and offer some advice.)
>
>I'm having a couple of problems related to this topic and was wondering if someone could assist.
>
>If I try to set up a linked server via ODBC to data that is on another server, I get an error stating that the server is unable to open the DBC file. However, if I try to simply execute a DSN-less query against that remote data from the same source server, I can select data without a problem.
>
>So, I thought I would try the OLEDB provider. Well, that one produces an error message stating that a registry entry couldn't be found for the provider, thinking it's not registered. However, the class exists in the registry and (like the ODBC situation) I am able to execute an ADO query using the provider without a problem.
>
>Any ideas??
>
>Laterness,
>Jon