Karen said:
I am still looking for a solution of passing an ADODB
Recordset back from a remote script call - any help or
direction would be appreciated.
Karen
Karen,
The Remote Scripting plumbing *is* able to send back objects
- typically custom objects where it populates the properties and
puts in empty functions for the methods. This would definitely
not work for a connected ADODB.Recordset since it cannot be
"serialized" to the client. Unfortunately Remote Scripting is
only able to "serialize" ECMAScript objects not COM objects
so even a disconnected recordset would still not be possible.
The approach I have seen used to do this in the past is to have
a function that converts the ADODB.Recordset into a
multidimensional array and then pass that back via Remote
Scripting. If I remember correctly it will flatten the array
into a single dimension when it gets back to the client so you
will need to work with it a little.
Here is a great article by the venerable Dino Esposito which
covers your exact question and even gives the code for the
Recordset2Array function!
http://www.microsoft.com/mind/0100/cutting/cutting0100.asp
Mentioned in the "News from the Real World" section.
Regards,
Jonathan Cogley
For a server side implementation of Remote Scripting in .NET
http://www.thycotic.com/dotnet_remotescripting.html
For a non applet based Remote Scripting client
http://www.thycotic.com/dotnet_remotescripting_client.html