Access 97 vs Access 2002, incompatibility

[eyemgod]

Hi have not use Acces for a while, now I'm trying to work on a project.
I took my old code out, but it does not work with Access 2002.

This is an example... what do I need to change to make it compatible with Access 2002

Thanks

--------------------------------
Option Compare Database
Option Explicit

Dim rstSearchColor As Recordset
Dim dbDL As Database


Private Sub Form_Load()

Set dbDL = CurrentDb

End Sub

Private Sub txtColorCode_Exit(Cancel As Integer)

If Not (txtColorCode = "") Then

Set rstSearchColor = dbDL.openrecordset("SELECT [ColorName] FROM [Colors] WHERE [ColorCode] = " + txtColorCode, dbOpenDynaset)

If rstSearchColor.RecordCount = 0 Then
MsgBox "You entered a wrong Color Code. Please try again.", vbOKOnly, "Search Failed"
Else
rstSearchColor.MoveFirst
txtColorName = rstSearchColor![ColorName]
End If
End If

End Sub

 

[Dugantrain]

You're using DAO. By default, Access 2000 and above does not set a Reference to DAO, so you must do so manually in order to use it. Open a Module, go to Tools, References, and check the DAO 3.6 Object Library and see how far that gets you. Also, make sure to move it in priority above Microsoft ActiveX Data Objects 2.1 Library.

*edit* since you now have a choice between using DAO and ADO and because the Object Models are similar, it is good practice to explicitly declare:

dim dbDL as DAO.Database
dim rstSearchColor as DAO.Recordset

in order to avoid any further compilation confusion.

 

[eyemgod]

THANKS A LOT !!!!!

You saved me a huge headache.

 

[Gates Is Antichrist]

Also, make sure to move it in priority above Microsoft ActiveX Data Objects 2.1 Library.

Or just uncheck ADO when checking DAO. Remember to make the one finger salute to Redmond while doing so.

This ADO nightmare is Y. A. fine example of the Antichrist's self-consumed self-appointed-gods' deeming that they know what's best for the user - and screw what the user thinks, or really wants. But in the most AMAZING fluke of nature in the history of data processing, MS Keystone quality control failed to close the loopholes Dugantrain points out!!

Dugantrain gave you a high quality answer, and the rant reflects my sympathies with you, the victim. How many millions of dollars have and continue to be wasted from that simple pompous action chosen by the developers at Microsoft...