🚀 go-pugleaf

"Wayne Niddery [TeamB]" <wniddery@chaff.aci.on.ca> wrote in message
news:3deaa556$1@newsgroups.borland.com...
> "Edward Diener" <eddielee@tropicsoft.com> wrote in message
> news:3dea8b03$1@newsgroups.borland.com...
> >
> > That's not the question. The question is: how do I convert DATE, TIME,
and
> > TIMESTAMP variant values to values I can use in an SQL statement. Does
SQL
> > using these types accept a 32 bit integer number, a 32 bit integer
number,
> > or a 64 bit integer number respectively for each of these values, or do
> > these values have to be in some sort of string format, ie. for DATE "Dec
> > 01,2002", to be accepted. If SQL accepts these values as just integer
> > numbers, then everything is fine, but if SQL needs some sort of string
> > values, then I have to convert them to some sort of acceptable string
> > format.
>
> Interbase accepts them as strings in standard formats, or as parameters.
You
> are *much* better off using parameters wherever possible. You are also
much
> better off avoiding variants wherever possible, especially with regard to
> dates and times. For dates and times, use the Delphi TDateTime type if you
> can. If you want to format a date into SQL, you can use the FormatDateTime
> function (avoid DateToStr, et al as these convert according to the local
> Windows settings which may or may not be acceptable formats for
Interbase).
>
> Using parameters is simple:
>
> Query1.SQL.Text := 'select * from table where datefield = :datefield';
> Query1.ParamByName('datefield').AsDateTime := MyTDateTimeVar;
> // or... Query1.Params[0].AsDateTime := MyTDateTimeVar;

I can't avoid Variants ( why should I ? ) but I will use your suggestion
above for using parameters, as that should work to get the values
automatically converted. I do wish their were a straightforward way to
convert the Variant value to a valid DATE, TIME, or TIMSTAMP string but
maybe that is what the Variant streaming operator, which I am using for all
other values does ( I am using C++ ). Thanks !