>>Jeroen,
>>
>>You're right that VFP stores the values, it just doesn't evaluate or send them correctly. It's all very nice that it stores it, but what good is it if it doesn't evaluate it or send it to another data source properly?
>
>I have no idea.
>I guess someone in the designtime of VFP thought it was a great idea to have millisecond resolution in the datetime-vars. However they did not bother to adapt the conversion routines to work with the milliseconds.
>There are some functions that are working in milliseconds though: time(1) and seconds().
>Together with all the info supplied in this thread you can build some basic functions to work in millisecond resolution.
>Remember: VFP is all about extensibility...

Jeroen,

Yes, I know about extensibility. However, this is a case where clearly VFP neither stores incoming date/times to the resolution that they're sent, nor sends it in the proper resolution.