Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to deal with ADO operation errors". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn how to deal with ADO operation errors.

Use the Number property to determine which error occurred. The value of the ADO action attribute is the * number corresponding to the error condition. The Errors collection returns HRESULT in hexadecimal format (such as 0x80004005) or as a Long value (for example, 2147467259). These HRESULT are generated by basic components, such as OLE DB, or even OLE itself.

Use the Source property of the Error object to determine the name of the object or application that initially generated the error. It could be the class name of the object or the programming ID. For errors in ADO, the property value will be ADODB.ObjectName, and this ObjectName is the name of the object that triggered the error. For ADOX and ADOMD, the values will be ADOX.ObjectName and ADOMD.ObjectName, respectively. The ADO operation is based on the error documents in the Source, Number, and Description properties of the Error object, and you can write appropriate code to handle the errors. For Error objects, the Source property is read-only. SQLState property.

If an error occurs while processing the SQL statement, use the SQLState property to read the five-character error code returned by the provider. For example, when using Microsoft OLE DB Provider for ODBC and Microsoft SQL Server databases together, SQL status error codes are generated from ODBC based on ODBC-specific errors or Microsoft SQL Server-generated errors, and the error codes are mapped to ODBC errors. ADO operation these error codes are described in the ANSI SQL standard, ADO operation, but if the data source is different, its implementation will be different. The NativeError property indicates an error code specific to the provider of a given Error object.

Use the NativeError property to retrieve database-specific error information on an Error object. For example, when using Microsoft ODBC Provider for OLE DB and Microsoft SQL Server databases together, the native error code generated by the ADO operation from SQL Server is passed to the ADO NativeError property through ODBC and ODBC Provider. Use the Clear method of the Errors collection to delete all existing Error objects in the collection. When an error occurs, ADO automatically empties the Errors collection and populates the collection with Error objects based on the new error.

Some properties and methods return warnings that appear as Error objects in the collection of ADO operations, but do not terminate the execution of the program. Call the Clear method of the Errors collection before doing the following: call the Resync, UpdateBatch, or CancelBatch method of the Recordset object; call the Open method of the Connection object; or set the Filter property of the Recordset object. This allows you to read the Count property of the Errors collection to test the warnings returned.

Thank you for your reading, the above is the content of "how to deal with ADO operation errors". After the study of this article, I believe you have a deeper understanding of how to deal with ADO operation errors, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.