I used to use RDS quite a bit on a company intranet, it's a bit passé now but can be made to work.
One aspect that has tightened up in the last few years is security, now servers won't accept RDS connections unless specifically configured to. See this link to make sure your server is set up correctly.
http://msdn.microsoft.com/library/de...asp?frame=true
One way to test is to use scripting and try the folloing in your browser to see whether it's your DSN that's a problem:
Code:
<OBJECT ID="RDS1" WIDTH=1 HEIGHT=1
CLASSID="CLSID:BD96C556-65A3-11D0-983A-00C04FC29E36">
</OBJECT>
<script>
function testRDS()
{
var oDF = document.getElementById("RDS1").CreateObject("RDSServer.DataFactory", <server name here>);
var sConn = "Provider='sqloledb';Initial Catalog='<database name here>'; User ID='read'; Password="
var sSql = "<some select statement here>";
var oRS = oDF.Query(sConn, sSql);
alert(oRS.Fields(0).value);
oRS.Close();
}
</script>
Make sure that errors are notified in you page by checking the box in Tools|Internet options|Advanced.
I would have thought that the DSN would need to be on the server, a system one not a user one.
--
Joe (
Microsoft MVP - XML)