Re: Nz Problem in ADO execute
- From: "John Spencer" <spencer@xxxxxxxxx>
- Date: Tue, 21 Mar 2006 08:24:38 -0500
I have seen NZ in queries return a string value instead of a numeric value.
It is especially apparent in Crosstab queries.
You can usually spot it by looking at the data*** view of a query. The
solution is to force the datatype using one of the numeric functions such as
CLng, Cint, CDbl, or Val.
"TC" <aatcbbtccctc@xxxxxxxxx> wrote in message
news:1142945232.088428.315190@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I still say you should query the value (before you update it) to see
what it is from the "Access end" of the process. It seems you have not
done that yet.
Are you certain that the sql is being processed locally (by
Access/Jet), and not as a passthrough query (ie. on the Oracle end)?
Personally, I'd have to see very compelling evidence, before I'd accept
that the Access NZ function was not working.
Cheers,
TC (MVP Access)
http://tc2.atspace.com
.
- Follow-Ups:
- Re: Nz Problem in ADO execute
- From: TC
- Re: Nz Problem in ADO execute
- References:
- Nz Problem in ADO execute
- From: Random
- Re: Nz Problem in ADO execute
- From: TC
- Re: Nz Problem in ADO execute
- From: Random
- Re: Nz Problem in ADO execute
- From: TC
- Nz Problem in ADO execute
- Prev by Date: Re: Get Data Type
- Next by Date: Re: Nz Problem in ADO execute
- Previous by thread: Re: Nz Problem in ADO execute
- Next by thread: Re: Nz Problem in ADO execute
- Index(es):