Call this member function to run the query defined by the querydef object.
An integer that determines the characteristics of the query. For related information, see the topic "Execute Method" in DAO Help. You can use the bitwise-OR operator (|) to combine the following constants for this argument:
dbDenyWrite Deny write permission to other users.
dbInconsistent Inconsistent updates.
dbConsistent Consistent updates.
dbSQLPassThrough SQL pass-through. Causes the SQL statement to be passed to an ODBC database for processing.
dbFailOnError Default value. Roll back updates if an error occurs and report the error to the user.
dbSeeChanges Generate a run-time error if another user is changing data you are editing.
For an explanation of the terms "inconsistent" and "consistent," see the topic "Execute Method" in DAO Help.
Querydef objects used for execution in this manner can only represent one of the following query types:
SQL pass-through queries
Execute does not work for queries that return records, such as select queries. Execute is commonly used for bulk operation queries, such as UPDATE, INSERT, or SELECT INTO, or for data definition language (DDL) operations.
The preferred way to work with ODBC data sources is to attach tables to a Microsoft Jet (.MDB) database. For more information, see the topic "Accessing External Databases with DAO" in DAO Help.
Call the GetRecordsAffected member function of the querydef object to determine the number of records affected by the most recent Execute call. For example, GetRecordsAffected returns information about the number of records deleted, updated, or inserted when executing an action query. The count returned will not reflect changes in related tables when cascade updates or deletes are in effect.
If you include both dbInconsistent and dbConsistent or if you include neither, the result is the default, dbInconsistent.
Execute does not return a recordset. Using Execute on a query that selects records causes MFC to throw an exception of type CDaoException.