🚀 go-pugleaf

Thanks for the answer, but I'am not sure I understand what you are
proposing...

I have a TDateTime variable.
How can I mulitiply the millisec part with 1000000 without changing the
complete timestamp ?

Regards
Bo


"Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote in message
news:3fdc2a9c$1@newsgroups.borland.com...
> Borland timesmap structure and Microsoft timestamp structure are
different.
> Where there are milliseconds in Borland, 1*10^-9 sec. in Microsoft. So try
> to just multiply milliseconds by 1 000 000.
>
> //------------------------------------------
> Regards,
> Vassiliev V. V.
> http://www.managed-vcl.com - using .Net objects in Delphi + ADO.Net
> http://www.oledbdirect.com - The fastest way to access MS SQL Server,
> MS Jet (Access) and Interbase (through OLEDB)
>
> "Bo Sundahl" <innovate@get2net.dk> �������/�������� � �������� ���������:
> news:3fdb9267@newsgroups.borland.com...
> > Hi
> >
> > I'am using BCB6 TADOStoredProc with a MS SQL Server 2000 database and
have
> a
> > problem with the millisec part of the datatime value.
> >
> > In the SQL Server 2000 I have like
> >
> > CREATE  PROCEDURE TEST_ADD
> >  @P_TIMESTAMP datetime
> > AS
> > insert into nancy.TEST values( @P_TIMESTAMP)
> >
> > In BCB6 I do
> >      pSPData->ADOStoredProcAdd->Parameters->Items[0]->Value =
dtTimestamp;
> > where dtTimestamp is a TDateTime with milliseconds.
> >
> > The data stored in the SQL server database is round to nearest second
> > although it do support milliseconds, i.e. "2003-12-12 12:23:44:000"
> >
> > Anyone having any idear where this goes wrong ??
> >
> > Thanks in advance
> > Bo Sundahl
> >
> >
> >
> >
> >
> >
> >
>
>