TIME() vs DATE() (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== TIME() vs DATE() (AREV Specific) ====
=== At 28 MAR 2001 01:36:28PM Peter Dunlap wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
Does AREV 3.12 (on Novell 5.0 with NLM) use a different access method for it's DATE() function than it's TIME() function?



After several days of operation my RBASIC scheduler application becomes confused regarding the current date.  The symptom manifests itself upto 5 minutes (so far) before midnight.  Durring this pre-midnight zone, the date is being erroniously reported by the AREV DATE() function, as the next day. This misleads the scheduler into re-launching it's programs and making false log entries.



I can duplicate this problem by allowing a test to run for several days. The durration before the problem occurs appears to be shorter on faster machines (e.g. 1 GHZ Pentium III's).
</QUOTE>
----

=== At 28 MAR 2001 02:57PM Dave Bennett wrote:  ===

<QUOTE> Is the Arev time insink with the computer time? Are you using Server Time?

-----------------------------7d14c3515021c--

</QUOTE>

----

=== At 28 MAR 2001 04:05PM Peter Dunlap wrote:  ===

<QUOTE>After several days running... probably not. Does AREV get the date from the network and it's time from somewhere else?

</QUOTE>

----

=== At 29 MAR 2001 09:15AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>AREV gets its date and time from the operating system of the workstation, using standard DOS calls.



In many systems we have seen delay code which has a bug where it activates after a period (say 5 minutes) and the system looks for TIME()+(5*60) but doesn't test for a result ] 86400. So around midnight the test fails. 



Often it is better in delay code to use (DATE() * 86400) + TIME() as an absolute time index.



You may simply have a standard error slipping into the date as a result of the PC speed. Many Pentium 4's run at 1+ GHz - there are not many Pentium 3's in this speed class. The Intel site has a utility to check if your PC is overclocked.



But then again, let's just blame Microsoft - who have recently implemented Microsoft Time as a new Windows standard. Especially - 



http://support.microsoft.com/support/kb/articles/Q189/7/06.ASP

http://support.microsoft.com/support/kb/articles/Q229/7/59.asp





You can always use this [url=http://www.state-of-the-art.com.au/util30.zip]SYNCTIME[/url]          routine to synchronize the workstation date and time with the Novell Server. If you prefer, the Novell supplied utility SYSTIME.EXE also achieves a server-workstation time synchronization. This should reset the DOS date supplied to AREV and solve your problem. Call SYNCTIME ahead of each DATE() and TIME() call.



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=83810A9E330CA7AC85256A1D0060B945|View this thread on the  forum...]]