Pass recordset out of process
From: Mark Guerrieri (mguerrieri_at_nospam_cmsgrp.com)
Date: 02/22/05
- Next message: rgutter_at_bctf.ca: "Re: Why do attributes (e.g adFldIsNullable) get cleared when opening a contsructed Recordset?"
- Previous message: rgutter_at_bctf.ca: "Re: ADO GetRows array to XML?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Feb 2005 22:19:00 -0500
I have an out-of-process server that implements an object with a 'Recordset'
property. It is implemented as an IDispatch* [out, retval] property. I
have also tried VARIANT* [out, retval]. When a client such as VbScript uses
this property, it appears that a copy of the internal recordset is
marshalled to the client, and no changes made in the client are visible to
the underlying recordset stored in the OOP server.
So how can I pass a recordset out of the OOP server and allow VBScript to
edit it and have the underlying recordset in the server update as well?
I am trying to allow a web page to use RDS and data binding to edit the
fields of the recordset, which works fine, except that only a local copy of
the recordset is ever modified.
I also tried adding a GetRecordset method with a VARIANT* [in, out]
parameter, but that showed the same behavior.
Can I pass a REFERENCE of my recordset out of process, or only a COPY?
Mark
- Next message: rgutter_at_bctf.ca: "Re: Why do attributes (e.g adFldIsNullable) get cleared when opening a contsructed Recordset?"
- Previous message: rgutter_at_bctf.ca: "Re: ADO GetRows array to XML?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
