Results 1 to 4 of 4
  1. #1
    Join Date
    Jul 2012
    Location
    Ireland
    Posts
    815
    Provided Answers: 17

    Unanswered: Timers somehow when they were run.

    Hi guys.
    I ran into a problem I can't seem to solve.

    Lets say I create a database that uses 10 timers. Some run every day, others run on certain days of the week, month or year.

    To test if the timers are working I changed the date and time on my PC so to pretend that it's just moments before the timers are expected to run.

    No problem here. Everything works find and I can see my timers have run.

    However, when I set my PC back to the right time the Timers will not run. After investigating this I noticed that somehow the timers are able to remember the last date and time they have run and they won't run for me again until that date and time they last run has passed.

    So my question is, does anyone know where the timers are storing this last run information and how do I clear it.

    Currently the only solution I've found is to the timers and rewrite them.

    Regards
    James.

  2. #2
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    495
    Provided Answers: 24
    Timers dont store info.
    Now be sure your comparisons take in the fact it is date AND time.
    If you are storing time in a variable it also has a date. Make sure you compare
    time w time, or
    date/time with date/time.

    Because time <> date/time

  3. #3
    Join Date
    Jul 2012
    Location
    Ireland
    Posts
    815
    Provided Answers: 17
    Hello.
    Thanks for the reply.

    Timers dont store info.
    I thought that too, but something is most certainly remember the timer has run which is preventing it from running again until the current date and time is of a higher value than the last date and time the timer ran.

    I'm not storing a time related value in a variable either, so it's not something I've coded.

    Very strange.

    Regards
    James

  4. #4
    Join Date
    Oct 2013
    Location
    Philippines
    Posts
    103
    Hi James,

    I had the same experience before. Yes I noticed that changing dates will trigger the problem. I noticed that BD will disable one of the timers when in conflict. I managed to enable the disabled timer by converting it as timer on database startup, then convert it again to the desired type when enabled. Then, as much as possible I created one timer only for one type. This could be the reason since all of them are running simultaneously.

    Regards,

    Ernie
    Last edited by mcmichael; 06-11-14 at 04:33.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •