>In my notes Devcon sessions, I give a fairly comprehensive demo of RDS in the context of COM and Automation. One thing to note that RDS really uses the ADO interface when it is all said and done. RDS actually makes use of a different local OLE-DB Provider, the MS Remote Provider. The MS Remote Provider in turn facilitates communication with a remote data provider. There are some configuration issues with RDS. I have found that at times, you need to totally reinstall things to get things working properly.
>
>In terms of using your own business object, could you elaborate on that a bit more?

I am using my own VB COM object to return a recordset to be used as the Source Recordset for the RDS Data Control instead of using the default RDSServer.DataFactory business object. I have been able to get RDS to work on my local development machine(Win 95/PWS), but when I try to use my custom business object from our IIS staging server, I get the error message. What, if any, security settings need to be in place on an IIS server to enable the client to create a proxy of a server side COM object?