You can remove the reference to DAO 3.6 in your project completely.
Still works.
You can change the reference from 3.6 to 3.51 in your project.
The new DC always uses DAO 3.6.
The only thing is that DAO 3.6 still needs to be on the system and your project needs to be using the new DC.
So, you could, for example, reference DAO 3.51 in your project, use a database object with that to connect to a '97 MDB, and also use the newer Data control to connect to a 2000 MDB or a '97 MDB.
If you do not reference the DAO 3.6 library in your project, you will need to add it to your set-up configuration when deploying your project.
This can be done with the Jet 4.0 Service pack.
So, again, it has to do with the DC being the wrong version.
Another way, for VB5 users when using the older control, is to set a reference to DAO 3.6 in your project and use recordset objects created with it, and the set the 3.51 data control's recordset object to your recordset objects created with DAO 3.6:
Set DataControl351.Recordset = rs36
>If you remove it from form and reload it, it will reference the new one
SSJpn:
I guess I assumed this, as it is a new control (VB5 vs. VB6).
CmPaiva's corrected statement in saying you need to remove it and add the new one manually, is right.
Or start a new project.
Or use the upgrade utility under:
\Programs\Microsoft Visual Studio\Common\Tools\ProjUpgd\PrjUpgd.exe.
I think this will do it also - it has been a while since I used it). [/b][/i][/u]*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!