We have a DSN on server A that points to a DB on server B. We have a server C, that we want to be able to use that DSN on server A...but we don't want to create the DSN on server C.

Is there a way to use the System DSN on server A from server C?

link|improve this question
feedback

3 Answers

up vote 2 down vote accepted

A system DSN, by definition, is local to the computer it's configured on. You'll need to create it on the other server.

An alternative option is to use a DSN-less connect string, if possible.

link|improve this answer
Unfortunate. We're trying to avoid creating a DSN on that computer, and the connection string option is failing and we can't figure out why. (and the driver/db vendor is no help so far.) Thanks for the answer. – Beska Jun 23 '09 at 16:14
(Assuming I don't get an answer that contradicts this, or provides a great deal more detail, relatively soon, I'll mark this as accepted.) – Beska Jun 23 '09 at 16:18
feedback

No, the purpose of a DSN is a connection from one machine to one data source. It is not possible to the best of my knowledge to "proxy" a DSN connection from one machine to the other.

link|improve this answer
feedback

yes, you can... i know this answer don't bother you after several years of asking this question, but i think it might help other people looking out for it.

You can achieve this using DSN less approach

For Example : connection string for SQL server DSN

oConn.Open "Driver={SQL Server};" & _
           "Server=xxx.xxx.xxx.xxx;" & _
           "Address=xxx.xxx.xxx.xxx,1433;" & _
           "Network=DBMSSOCN;" & _
           "Database=myDatabaseName;" & _
           "Uid=myUsername;" & _
           "Pwd=myPassword"

I have already tried it myself, however you need to have sufficient access rights

More DSN connection strings can be found Here

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.