Hi Tim,

> With queries, the only thing that a Prepare does is populate the data
> types for the parameters.  Assigning the SQL property will set up the
> parameters for a query, in contrast to a stored procedure or script, which
> both require that you need to Prepare them first before assigning the
> parameters.

Okay. It is just that I am used to use the prepare statement when using
parameters. And eventhough, as you stated, it ain't necessary, I will
continue to do so - old habbits die hard I guess. And I did said I could be
mistaken

Best regards,
Fons

Yes, now work but why until the 1.07 version all query work without this
modification.
I have to change a lot of query

Mirco


"Fernando Dias [Team Elevate]" <fernandodias.removthis@easygate.com.pt> ha
scritto nel messaggio
news:DD62678B-BEAE-43D4-9728-65B4C46BBC4B@news.elevatesoft.com...
> Malagoli
>
>> No, is the standard "ptUnknow" when add parameter in SQL code.
>
> In that case, It can be the cause...
> Set it to "ptInput" and see what happens.
>
> --
> Fernando Dias
> [Team Elevate]

Mirco,

<< Yes, now work but why until the 1.07 version all query work without this
modification.  I have to change a lot of query >>

ElevateDB supports input and output parameters for SQL statements.  For
example, INSERT statements can have an output parameter for retrieving the
value of an IDENTITY column after an insert.  This is why it is important
that it know the type of parameter.

Also, by default, when ElevateDB parses the parameters and auto-populates
them, it sets the parameter type to ptInput, so you must have, at some
point, changed the parameter type.

--
Tim Young
Elevate Software
www.elevatesoft.com