I know we could use Net Time to synchronize a local computer's time to that of a server but I want some alternatives... Sometimes Net Time fails for some strange reasons, sometimes it takes it too long to return a response (5 seconds or more)... Maybe I could use a winsock? But the downside of this is an app should be running in the server right?
In SQL Server there is the GetDate() which could be used, is there an Access equivalent of it?
Last edited by dee-u; Jun 27th, 2005 at 01:49 AM.
Regards,
™
As a gesture of gratitude please consider rating helpful posts. c",)
I think the time returned would be correct no matter how long it took to return. You can also check the server time to see if it's off. I don't think it would be.
What I meant was Net Time encounters errors sometimes, not that it returned an incorrect date/time.
If it's once in a blue moon u could simply do a resume.
Pradeep
Pradeep, Microsoft MVP (Visual Basic) Please appreciate posts that have helped you by clicking icon on the left of the post.
"A problem well stated is a problem half solved." — Charles F. Kettering
To really make it sure that the synchronized time is used everytime we save in the database we actually ALWAYS do the Net Time thing but wants to make it 100% error-free so the saving process wouldnt be interrupted if in case an error occurs...
Regards,
™
As a gesture of gratitude please consider rating helpful posts. c",)