Marshaling Disconnected Recordset Changes Back to the Business Layer

Marshaling Disconnected Recordset Changes Back to the Business Layer

A Recordset without a live connection to a database server is called a disconnected Recordset. After the client machine receives the disconnected Recordset, it can use ADOR Recordset to manipulate data. After the changes are made to the Recordset, the client can choose to marshal the whole Recordset back or only the changed data. The MarshalOptions property of the ADO Recordset is designed for this purpose. You can set MarshalOptions to adMarshalAll, in which case all rows are returned to the server, or to adMarshalModified, which indicates that only modified rows are returned to the server. Setting the MarshalOptions property can improve performance when modified remote data is marshaled for updating back to the middle-tier or Web server.

See also  5 Ways to Improve Customer Experience

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist