🚀 go-pugleaf

Hmmm.  Interesting.  But, it doesn't work.

BTW, using the Oracle OLE DB provider.

When I assign NULL, the TParameter Value is 0 and the Size is -1.  On an
INSERT, it actually puts a "0" into the table column.  I really want an
empty
value, not zero.  However, I found that when I assign a NULL AnsiString or
empty C string and then set the TParameter Size to -1, it seems to give
the desired result.  It seems unhappy only when the Size is zero.

"BM" <m02x7z00@cwcom.net> wrote in message news:3b23a7eb_2@dnews...
> First of all I'm more familiar to Delphi so I apologies for any
> discrepancies.
> Can't tell you why these things happen but from our experience if you have
a
> NULL string you must set the parameter to NULL (i.e check its a blank
> string- if it is set Parameter.Value = NULL) otherwise you see this error.
> Another advisable thing to do is initialise all parameters to NULL i.e.
> before any parameters are set is loop through them and set their value to
> NULL.
>
> BM
>
>
> 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?
> >
> >
>
>