difficult query calculation (tweak needed)

The latest revision is at http://www.dropio.com/tasksdb. I am in need of a better calculation or elimination of unneeded values. The qryCalcActive is supposed to note the time span for each 'period of activity' in a field called ActiveTimes which it does do. The problem is that it also reports other data as active when it really isn't. Hnasr states that Active=False "somewhere?" should fix it. I'm going to look for this next. Much thanks to anyone who can take a look at the database and chime in.

It's difficult to tell because I am not sure what you left active and for how long.
If you clear the records in the tables, perform the following.
Leave only one item open for say 5 minutes or so.
Then, deactivate it by unchecking the active check box in frmAddTasks
You will notice that the day field of the frmAddTasks itself now shows No Active Task!
This is what you want.
Now you should be able to look at qryActiveDurations and see some values that should not be there. Ideally, if only one task and one duration was in active status for 5 minutes, then only that task and that duration should show the value.

Not that I know of.... I just clear the records in the two main tables and run a task for 5 minutes through frmAddTasks. I then make that task inactive and check the query. Should only be one number 5. I'm doing it again now to try and nail down the specifics.

This is very odd! In the database I just uploaded, I was about to write saying I made a mistake and that it works perfectly. Notice in the query, that it now shows 18 values for nearly every task at at least one point. I started clicking them at random, which has the effect of activating them and deactivation whatever came before. I clicked done on a few and reactivated some of them randomly. Nothing has been open for more than 15 minutes (including the pear which has an extra 3 minutes added).

Version uploaded as version 5e. It looks like it calculates correctly and I can't get the query to do anything other than behave perfectly!

Interestingly, it also calculates time that was 'inactive' which is not desired. Perhaps that time could be shown as a 0 or something? Also, the time in the query should perhaps report in format min:sec . This will make for an easier comparison down the road with reporting and with timer repair.

Are you talking about calculations in the query?
We are excluding that in the query that is used in the timing "qryCalcLifeSpan"
"qryCalcActiveDurations" query is intermediate and you can nest it later in the used query. But do that in a tidy up stage.

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

I spoke too soon.. Version F uploaded. The longest task is the one named "second task" which was open for over 3 minutes and shows zero's in every active slot. This is partially why it needs to show min:sec so that I can more easily troubleshoot.

Looks easy, but may not.
The idea is not to have two consquative inactives. This situation happens if task b is active, and you activate task a then task b becomes inactive, when clicking complete of task b, it is recorded as inactive for a second time.
Checking later when time allows!

Featured Post

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

QuickBooks® has a great invoice interface that we were happy with for a while but that changed in 2001 through no fault of Intuit®.
Our industry's unit names are dictated by RUS: the Rural Utilities Services division of USDA. Contracts contain un…

I originally created this report in Crystal Reports 2008 where there is an option to underlay sections. I initially came across the problem in Access Reports where I was unable to run my border lines down through the entire page as I was using the P…