🚀 go-pugleaf

Thanks!

Tharun, the exact opposite works.

I set the Attibutes to include pa_Nullable, the DataType to ftString

and the value to a NULL (not empty!) variant and it worked!



Guiliano, I will try that as well.


        John Biddle
        Vigilant Systems


"John Biddle" <johnb@vigilant-systems.com> wrote in message
news:3b683e99$1_1@dnews...
> I have a TADOQuery hooked up to a MS SQL Server 7.0 database.
> I am trying to execute a parameterized insert statement to update a
> VARCHAR(64) field that is nullable in the SQL database.
>
> ADO will not allow me to set this parameter to NULL.
> It always raises an exception:
> 'Parameter object is improperly defined.
> Inconsistent or incomplete information was provided'
>
> I have tried all of the following without success:
>
> Assigning the TParameter to an empty variant (VT_EMPTY).
> Assigning the TParameter to an null variant (VT_NULL).
> Setting the TParameter Attributes to pa_Nullable.
> Setting the TADOQuery ParamCheck to false.
>
> The query works fine if I replace the parameter in the SQL text with the
> NULL keyword.
>
> I have lots of parameters in this query and would really like to avoid
> having
> to generate the SQL at runtime.
>
> Any ideas?!?!?!?!?
>
>     John Biddle
>
>
>