If you think your project is still referencing the DAO object library, there is a possibility that you still have the DAO object library included in the references to your project. Go to Project > Preferences and uncheck the Microsoft DAO 3.51 Object Library from the window.

The problem arises because the DAO and the ADO use the same object naming terminology. A recordset is called a Recordset in both DAO and ADO.

If you still want to reference both the libraries sothat you can completely test the code and then migrate totally to ADO, you can put the word 'ADODB' before any ADO data objects you are using. For e.g.

[code]
Dim rsDAO As RecordSet ' Declares a DAO Recordset Object Reference

Dim rsADO As ADODB.RecordSet 'Declares a DAO Recordset Object Reference

[\code]


Whenever you are using ADO objects, prefix their types with "ADODB."


I think that should take care of your problem. If you are still getting the same error, you need to check the ADO code being used, as ADO is a little more complicated to understand and program than DAO.