Jeff Eckermann ha scritto:
> Not quite true: you could always use unbound forms
> etc, though that lets you in for a lot of extra work
> ;-)
> Your queries suggest that "CostoEffettivo" is a
> display field, i.e. it is not used in computations and
> will not be updated directly. If so, try casting it
> to text in your view definition, and have it displayed
> as text in your form. At least the value should agree
> that way, so your updates would succeed.
> As for controlling the way Access composes its SQL: I
> don't know whether that is possible, perhaps you could
> post the question to an Access NG/List.
>
Thanks I've solved in this way. The field "CostoEffettivo" is used in
the form only to do a calcul in VBA, I only had to place a Val() in that
piece of code.
Some note about the very stupid behaviour of Access. When I link an ODBC
table, if it has not a unique identifier such a primary key, Access asks
me for that. If I don't choose any field Access will refuse to make any
update or insert in the table. So, I think, if I choose the primary key
fields for the table, Access will use only that fields to do updates.
But, NO, Access will use practically all the fields of the table (really
not all the fields, don't know what criteria it uses to choose them), so
I ask: why it needs to know a unique identifier when it link tables? It
could simply use *always* all the fields of the table as unique identifier!
Anyway, thanks a lot for your answers.
Bye, Romaz