If you put 'Int(68.71*100)' into your SQL, is it interpreted
by JET or by VBA? In Access 97, SQL statements (except
for SQL pass through) are interpreted and optimised by
Access before they are passed to the JET engine, where
they are interpreted and optimised before they are passed
to whatever non-jet data source you are using. My impression
is that in A97 INT is being evaluated by
VBA rather than
JET, but that is based on the fact that JET SQL does not
in general support type coercion (ie Long(68.71*100)) and
INT is a data type, not a function, in SQL. Is this
different in JET 4.0?
Quote:
>The good news is that Jet 4.0 (in contrast to Jet 3.51)
>handles it OK.
It works for me in 3.51: I get 6870.0 Let me stress that there
is a legitimate use for INT and FIX, and
INT((68.71*100) + 0.1)
is one such use, but surely you would be better off using
CINT(68.71 * 100) if that is what you want?
You don't have to understand CINT to use it correctly.
Quote:
>Like I mentioned what I am really concered about is
>calculations like Int(68.71*100) in SQL Queries.
>The good news is that Jet 4.0 (in contrast to Jet 3.51)
>handles it OK.
>Tomasz Jastrzebski