FILE: Rdsensub.exe with RDS Conflict Resolution Sample - Includes Binding, Addnew

ID: Q177720

The information in this article applies to:

SUMMARY

In version 1.5 of Remote Data Services (RDS), the SubmitChanges method returns that an update either failed or succeeded. In the future, RDS will support providing more information about failures. However, that feature is not available in the 1.5 release.

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.


MORE INFORMATION

The following file is available for download from the Microsoft Software Library:

Rdsensub.exe
Release Date: 10-23-97

For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:
Q119591 How to Obtain Microsoft Support Files from Online Services


Remote Data Services (RDS) does provide the 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:


    3. 
      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.


Additional query words: kbdse 


Keywords          : kbnokeyword kbRDS 
Version           : WINDOWS:1.0,1.1,1.5
Platform          : WINDOWS 
Issue type        : kbhowto

Last Reviewed: February 3, 1999