Visual Basic: RDO Data Control
Contains all stored rdoError objects which pertain to a single operation involving Remote Data Objects (RDO).
Any operation involving remote data objects can generate one or more errors. As each error occurs, one or more rdoError objects are placed in the rdoErrors collection of the rdoEngine object. When another RDO operation generates an error, the rdoErrors collection is cleared, and the new set of rdoError objects is placed in the rdoErrors collection. RDO operations that don't generate an error have no effect on the rdoErrors collection.
- Use the Clear method on the rdoErrors collection to remove all rdoError objects. In most cases, it is not necessary to use the Clear method because the rdoErrors collection is cleared automatically when a new error occurs.
Members of the rdoErrors collection aren't appended as is typical with other collections. The most general errors are placed at the end of the collection (Count -1), and the most detailed errors are placed at index 0. Because of this implementation, you can determine the root cause of the failure by examining rdoErrors(0).
The set of rdoError objects in the rdoErrors collection describes one error. The first rdoError object is the lowest level error, the second is the next higher level, and so forth. For example, if an ODBC error occurs while the RemoteData control tries to create an rdoResultset object, the last rdoError object contains the RDO error indicating the object couldn't be opened. The first error object contains the lowest level ODBC error. Subsequent errors contain the ODBC errors returned by the various layers of ODBC. In this case, the driver manager, and possibly the driver itself, returns separate errors which generate rdoError objects.