🚀 go-pugleaf

"Clayton Arends" <nospam_claytonarends@hotmail.com> д����Ϣ����:454a2986$1@newsgroups.borland.com...
> When I first read your second message it appeared to me that you 
> accidentally replied to your own message.  However, I just read it again 
> and saw that you changed a 31 to a 30.  For future reference, when you are 
> correcting something you wrote please make it obvious.  For instance:
>
>  I mistyped the bad date.  It should have been "2006-11-20 12:12:30".
>
> This would make it apparent why the second post exists.
>
> However, to answer your question.  It could be a floating point rounding 
> error though I've never seen that happen to a TDateTime before without 
> some sort of arithmetic involved.
>
> I'll keep my eyes open to try to find out what the issue is.  Hopefully 
> someone else that knows what's going on will respond.
>
> - Clayton
>
Thank you,Clayton!I have seen my program again,I thought maybe you are 
right.Because the DateTime was reprented as a float value in the access,and 
In my application I put data into the table every 200ms, perhaps the 
difference was the different convertion method between Borland and 
Microsoft.so you are right:It could be a floating point rounding .