OleDB Error: Data Type Mismatch

[Guest]

help

Deploying a .Net Application using ADO and MS Access (Jet 4.0) and MDAC 2.8.

Get error: OleDbError .... Data type mismatch in criteria expression ..

The application works fine in the development machine
- OS: Windows 2000 Pr
- Jet 4.0 (msjet40.dll Vers. 4.0.7328.0; odbcjt32.dll Vers. 4.00.6200.0
- MDAC 2.

The error occurs in the test machine
- OS: Windows X
- Jet 4.0(msjet40.dll Vers. 4.0.4431.0; odbcjt32.dll Vers. 4.00.6019.0

Is the error caused by the XP machine older Jet engine?? or something else?

If because of older Jet version, how do i distribute the newer Jet drivers since MDAC 2.6 and greater do not contain Jet engine updates anylonger?? I don't believe i can install/rollback to earlier MDAC's on XP (besides i wouldn't want to)

I was looking for a Merge Module (.msm) to do this, but to no avail

Has anybody encountered this problem?? Am I missing something?? Does anybody know a workaround?

I would really like for the deployment utility to handle this. You know, check the version and if older update

Thank
Alex

 

[Paul Clement]

¤ help.
¤
¤ Deploying a .Net Application using ADO and MS Access (Jet 4.0) and MDAC 2.8.
¤
¤ Get error: OleDbError .... Data type mismatch in criteria expression ...
¤
¤ The application works fine in the development machine:
¤ - OS: Windows 2000 Pro
¤ - Jet 4.0 (msjet40.dll Vers. 4.0.7328.0; odbcjt32.dll Vers. 4.00.6200.0)
¤ - MDAC 2.8
¤
¤ The error occurs in the test machine:
¤ - OS: Windows XP
¤ - Jet 4.0(msjet40.dll Vers. 4.0.4431.0; odbcjt32.dll Vers. 4.00.6019.0)
¤
¤ Is the error caused by the XP machine older Jet engine?? or something else??
¤
¤ If because of older Jet version, how do i distribute the newer Jet drivers since MDAC 2.6 and greater do not contain Jet engine updates anylonger?? I don't believe i can install/rollback to earlier MDAC's on XP (besides i wouldn't want to).
¤
¤ I was looking for a Merge Module (.msm) to do this, but to no avail.
¤
¤ Has anybody encountered this problem?? Am I missing something?? Does anybody know a workaround?
¤
¤ I would really like for the deployment utility to handle this. You know, check the version and if older update.


Are you certain that it isn't related to the data, for example attempting to insert a null value
when a value is required or a null value is not allowed?


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)