This page requires general cleanup in formatting or text to better fit the UA Wiki Guidelines

Related Content:
    Error Codes TOC

When you are developing VBA code and suddenly begin to get Type Mismatch errors in sections of your code that previously compiled without a problem, a possible cause of the error is that you have begun to use a mixture of DAO and ADO references. There is a Microsoft Knowledge Base Article dealing with some of the issues here. The article suggests that changing the priority of the DAO reference so that it is higher than the ADO reference will solve the problem.

While it is true that changing the priority of the references will solve the problem, a preferable solution is to fully qualify recorset and other data related declarations. So instead of declaring

write the declaration by prefixing the relevant object library name to the object name you are using

To duplicate the problem, try this

Make sure that you have set the ADO reference higher in priority than the DAO refence and compile the code. The compile should fail with a "Type Mismatch" error on the For Each FldName in Fields statement.

Now modified the fld declaration to make it qualified.

Now, even though the reference priority has not changed, the code will now compile and run (providing that the active screen form is bound to a recordset.

Conclusion: always use fully qualified dao or ado references. The libraries have many identical object names. Qualifying the declaration ensures you are using the object you want and not a similarily named object in the 'wrong' library.

original article by agreedblu