Type Mismatch

[CooterBrown]

My program works fine on any win2000 or 98 machines but I loaded it to a few XP boxes and on one only, I get a fatal run time error 13 type mismatch. Any ideas? Something with the latest MDAC? Why only the one XP machine? Please help...

TIA

 

[VBrit]

Thats a bit odd. Apply Service Pack 2 to XP and then reinstall MDAC.

 

[CooterBrown]

Will MDAC install with OFFICE?

 

[chiph]

Yes -- Office installs a copy of the MDAC.
The question is: which version of the MDAC does it install?

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[VBrit]

go to:

http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&DisplayLang=en

And download MDAC 2.8

Ideally you should always use the latest version of MDAC.

 

[kainite]

Sounds like you are barking up the wrong tree here but first - a hint on finding out which MDAC a machine has

Go to C:\Program Files\Common Files\System\ado and look at the file properties for msado15.dll - if this is e.g 2.71 then you have MDAC 2.7 etc

However back to orginal type mismatch problem - your post could do with more detailof the error - obviously there is some data access involved as otherwise you wouldn't be worried about MDAC - chance is error is related to the data itself rather than the MDAC version - and this may be different for the users on different machines - some of the things that can cause this are e.g date conversions and a nasty one that can catch out quite easily is if database field is e.g varchar(80) and you try to write a string of longer that 80 chars into it etc etc - how about posting full text of error message

 

[CooterBrown]

I don't "think" it is a problem with the data definition. This database for this software has been virtually unchanged for about 3 years. This is a fresh install on a new machine and before the user even gets to do any data entry, he's getting a type mismatch error. I've gone as far as removing all objects associated with the software and unregistering it to ensure no dirty data was entered after it was shipped...