Hmm. I'm not sure what to suggest... sorry! :(
> -Original Message-
> From: Dan Johansson [mailto:[EMAIL PROTECTED]]
> Sent: 05 September 2002 18:30
> To: Ben Joyce
> Cc: [EMAIL PROTECTED]
> Subject: Re: ado/mysql problem
>
>
> Yes, I have now. Do not
t;>To: Ben Joyce
>>Cc: [EMAIL PROTECTED]
>>Subject: Re: ado/mysql problem
>>
>>
>>I know the same issus exist on XP. One can't downgrade mdac on XP ??
>>So I really would like an other solution.
>>
>>/Dan
>>
>>Ben Joyce wr
ahhh, hmm, erk...
have you checked the MDAC site and MSKB for known bugs?
> -Original Message-
> From: Dan Johansson [mailto:[EMAIL PROTECTED]]
> Sent: 05 September 2002 15:19
> To: Ben Joyce
> Cc: [EMAIL PROTECTED]
> Subject: Re: ado/mysql problem
>
>
>
t;>From: Dan Johansson [mailto:[EMAIL PROTECTED]]
>>Sent: 05 September 2002 15:03
>>To: [EMAIL PROTECTED]
>>Subject: ado/mysql problem
>>
>>
>>Hi
>>After uppgrade mdac from 2.5 to 2.7 I get wrong types. An unsigned
>>integer column was previously rep
Yep, I had issues too... I've dropped back to MDAC2.5 and all is well.
.b
> -Original Message-
> From: Dan Johansson [mailto:[EMAIL PROTECTED]]
> Sent: 05 September 2002 15:03
> To: [EMAIL PROTECTED]
> Subject: ado/mysql problem
>
>
> Hi
> After upp
Hi
After uppgrade mdac from 2.5 to 2.7 I get wrong types. An unsigned
integer column was previously reported to be of type 3 (Integer) now it
is returned as type 5(double). This atleast happens when im using
getrows() in the recordset object.
Can anybody tell what is going on here ?
Im using m
