HOWTO: Determine if RDO Restartable Property is Set to False

 Last reviewed: July 14, 1997
Article ID: Q154757
The information in this article applies to:
  • Enterprise Edition of Microsoft Visual Basic for Windows, 32-bit only, version 4.0

SUMMARY

Remote Data Objects (RDO) provided with Visual Basic give the programmer the ability to Requery an rdoResultset. The Requery method ensures that the rdoResultset contains the most recent data or enables the user to return different results for a prepared statement whose parameters have been changed.

The Online Help suggests checking the Restartable property to determine if the rdoResultset supports requerying.

MORE INFORMATION

The Online Documentation has the following advice: 

   Check the Restartable property before using the Requery method on an
   rdoResultset. If the object's Restartable property is set to False, use
   the OpenResultset method on the underlying rdoPreparedStatement to re-
   execute the query.

   You can use the Requery method to update an rdoResultset object's
   underlying parameter query after the parameter values have been changed.
   If the rdoPreparedStatement does not contain parameters, the Restartable
   property is always True.
In practice, however, the Restartable property of an rdoResultset is always True unless the Connection or the Statement handle is invalid. The Statement Handle will be invalid after closing the rdoResultset.

This article does not apply to the Restartable property of a DAO Recordset.

REFERENCES

Online Help Restartable, ReQuery.

Keywords : vb432 vb4win kbhowto
Version : 4.0
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.