Rdsensub.exe with RDS Conflict Resolution sample - Includes Binding, Addnew (177720)


The information in this article applies to:

  • Remote Data Service for ADO 1.5
  • Remote Data Service for ADO 2.0
  • Remote Data Service for ADO 2.1 SP2
  • Remote Data Service for ADO 2.5
  • Remote Data Service for ADO 2.6
  • Remote Data Service for ADO 2.7
This article was previously published under Q177720

SUMMARY

The RDS Enhanced Submit sample creates a custom business object, which when changes are submitted, generates and returns a recordset with each record that failed to be submitted.

Note that starting with RDS 2.0, you can also extend the functionality of the default RDS business object, the DataFactory object. To do this, you write a custom handler object that implements a specific interface called IDataFactoryHandler. For more information, please see the article listed below.

MORE INFORMATION

The following file is available for download from the Microsoft Download Center:

RDSENSUB.exe

Remote Data Services (RDS) provides an architecture by which a developer could implement an update status mechanism through the use of custom business objects. This sample provides an example of how this functionality would be implemented by a developer.

Server installation

The following steps are to be followed for a server-side installation of Rdsensub.dll:
  1. Copy Rdsensub.dll and Launchsafe.reg to a folder on your RDS server.
  2. Register Rdsensub using Regsvr32.exe using the following command line syntax:

          regsvr32 Rdsensub.dll

  3. Make Rdsensub.dll Launch Safe by double-clicking Launchsafe.reg in Windows Explorer.
  4. Test Rdsensub.dll by using Testconflict.htm or Testconflict.exe.
  5. Review the VBScript code in Testconflict.htm.

Running the HTML sample

  1. Copy Testconflict.htm to a folder on your RDS client or a folder on your Internet Information Server (IIS) accessible by your Web browsers.
  2. Open the Testconflict.htm page. Running multiple instances of Testconflict.htm is a way to reproduce an actual conflict situation.
  3. Review the VBScript code in Testconflict.htm.

Running the Visual Basic sample

  1. Copy Testconflict.exe, Testconflict.vbp, and Testconflict.frm to your RDS Client computer.
  2. Run Testconflict.exe. Running multiple instances of Testconflict.exe is a way to reproduce an actual conflict situation.
  3. Review the Visual Basic for Applications (VBA) code in Testconflict.frm.
Modification Type:MinorLast Reviewed:7/12/2006
Keywords:kbdownload kbDatabase kbhowto KB177720
©2004 Microsoft Corporation. All rights reserved.