In computing, Microsoft's ActiveX Data Objects (ADO) comprises a set of Component Object Model (COM) objects for accessing data sources. A part of MDAC (Microsoft Data Access Components), it provides a middleware layer between programming languages and OLE DB (a means of accessing data stores, whether databases or not, in a uniform manner). ADO allows a developer to write programs that.

ADO uses several different methods to notify an application of errors that occur. This chapter discusses the types of errors that can occur when you are using ADO and how your application is notified. It concludes by making suggestions about how to handle those errors.

1. After you install this update, Visual Basic automatically displays the Microsoft ActiveX Data Objects 6.1 Library in the Available References list when you try to add references to the current project. To manually locate the ADO 6.0 type library (Msado60.tlb) in this situation, browse to the following location.
2. Download ActiveX Data Objects (ADO) 1.5/2.0/2.1 SP2 and Visual Basic Sample: Using ADO with an MTS Component via DCOM (Adomts.exe) for Windows to learn how to use and connect Standard.exe client.

How Does ADO Report Errors?

ADO notifies you about errors in several ways:

• ADO errors generate a run-time error. Handle an ADO error the same way you would any other run-time error, such as using an On Error statement in Visual Basic.
• Your program can receive errors from OLE DB. An OLE DB error generates a run-time error as well.
• If the error is specific to your data provider, one or more Error objects are placed in the Errors collection of the Connection object that was used to access the data store when the error occurred.
• If the process that raised an event also produced an error, error information is placed in an Error object and passed as a parameter to the event. See Chapter 7: Handling ADO Events for more information about events.
• Problems that occur when processing batch updates or other bulk operations involving a Recordset can be indicated by the Status property of the Recordset. For example, schema constraint violations or insufficient permissions can be specified by RecordStatusEnum values.
• Problems that occur involving a particular Field in the current record are also indicated by the Status property of each Field in the Fields collection of the Record or Recordset. For example, updates that could not be completed or incompatible data types can be specified by FieldStatusEnum values.

The following sections describe each of these notification methods in more detail.

Errors related to msado15.dll can arise for a few different different reasons. For instance, a faulty application, msado15.dll has been deleted or misplaced, corrupted by malicious software present on your PC or a damaged Windows registry.

Ami bios rom file download. The most commonly occurring error messages are:

Missing Microsoft Activex Data Objects 6.1 Library Download

• The program can't start because msado15.dll is missing from your computer. Try reinstalling the program to fix this problem.
• There was a problem starting msado15.dll. The specified module could not be found.
• Error loading msado15.dll. The specified module could not be found.
• The code execution cannot proceed because msado15.dll was not found. Reinstalling the program may fix this problem.
• msado15.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vender for support.

Activex Object Download

In the vast majority of cases, the solution is to properly reinstall msado15.dll on your PC, to the Windows system folder. Alternatively, some programs, notably PC games, require that the DLL file is placed in the game/application installation folder.

Microsoft Activex Data Objects 6.1

For detailed installation instructions, see our FAQ.