🚀 go-pugleaf

Yes.  Setting the value to Null (not zero) sets a 'Size' of zero and this
seems to be what upsets either ADOExpress or ADO.

"Alon Novy" <alon.novy@thinksoftware.com.au> wrote in message
news:3b3c42a6$2_1@dnews...
> Arnie
>
> Does the same happen if you try:
>     q->Parameters->ParamByName( "foo" )->Value = Null;        // note:
using
> Null variable, not c/c++ NULL value
>
> or alternatively:
>     q->Parameters->ParamByName( "foo" )->Value = Variant( );
>
> ???
>
> Alon
>
> "Arnie Mauer" <arnie@marketexpert.com> wrote in message
> news:3b20ed67_2@dnews...
> > In a parameterized INSERT statement in a TADOQuery, when setting
> > q->Parameters->ParamByName( "foo" )->Value = "";
> > will cause q->ExecSQL() to throw an excpetion of: "Parameter object is
> > improperly defined.  Inconsistent or incomplete information
> > was provided."  Same goes for a NULL AnsiString.
> >
> > The TParameter Value == NULL and Length == 0.  The DataType
> > has been properly set to ftString after the assignment.  What's
> > wrong with a NULL string?
> >
> >
>
>