Environment versions
Network:
Windows 2000 Server
>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...
function DateTimeExt
* extend datetime() with millisecond reso
LOCAL ltNow,lnSeconds
ltNow=DATETIME()
lnSeconds=SECONDS()
* check if we didnt get an timeupdate during the 'store'
DO WHILE SEC(ltNow)<>INT(MOD(lnSeconds,60))
ltNow=DATETIME()
lnSeconds=SECONDS()
ENDDO
RETURN DTOT(TTOD(ltNow))+lnSeconds
* this function does not really give msec resolution, because it seems to be based on the internal timertick
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only