difficult query calculation (tweak needed)

Added the criteria to qryCalcActive field ActiveTimes as Active=False seems empty the query.  What could I be doing wrong?

some renames...  qryCalcActiveDurations and now MinutesActive that is not reporting minutes active but also some unecessary minutes.  Help requested.   update posted http://www.dropio.com/tasksdb

OK, I'm looking at qryCalcActiveDurations.

Help me zero in on the problem.  the results are shown in the attached file.

What should they look like instead?

Thanks.

   


qryCalcActiveDurations-Results.GIF

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.

I downloaded the DB as you posted it and changed no data.

Would something in it be changing the data just by virtue of opening the DB?

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).

So is the problem believed to be in the CAPTURE of the data, or the REPORTING of the data?

I was looking at the reporting side ...

I think it could be in the CAPTURE of the data.  This thread here denotes some changes to the table that GrayL is saying need to be fixed first.   Can you read it here https://www.experts-exchange.com/questions/23791933/Help-renaming-a-field-in-a-table.html?cid=239&anchorAnswerId=22661151#a22661151 and give me your perspective?

Modified version taking seconds into account, check and report!

database-v1-3-5c-x.mdb

That's excellent!

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.

What do you think?

<Interestingly, it also calculates time that was 'inactive' which is not desired>
Checking

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.

I'd rather get the query right first.  I see seconds for inactivity which is undesired.  The desire is to see only "active" seconds and preferably represented in min:sec

I may not be following you entirely.  If qryCalcActiveDurations is intermediate, then the goal would be to report the totals in qryCalcLifeSpan, correct?  This is great!

Even so, the periods of 'inactivity' should show as zeros and the reporting should still be min:sec.

Try this!

database-v1-3-5e-x.mdb

Looks better....  How to represent in min:sec ?

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.

OK... thanks for the min:sec calculation...  this helps.

Notice the screenshot.  I have uploaded the database here (version 5g) so you can see it in action.  There is still a problem somewhere?

1.png

I see that, and it is because of completing the task then reactivating!
Looking into that!

you are amazing!


thank you for hanging in there...

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!

I appreciate it very much....  I'll look forward to your reply.

Hello again,
Please test this version.
database-v1-3-5g-x.mdb

I can't respond to this post here https://www.experts-exchange.com/questions/23790442/difficult-query-calculation-tweak-needed.html?cid=239&anchorAnswerId=22668278#a22668278 because there is no submit button when using it from work.  I sent you an email with lenghty detail.  

Here is what I found in short:

1. Unchecked active box shows active time, the good news is that 'inactive time' isn't shown but unchecked is not desired.

2. The done button (which used to move completed items to the bottom of the form no longer works leaving each task always incomplete and in the top of the form.

np

https://www.experts-exchange.com/questions/23788341/How-is-a-this-query-field-calculated.html?anchorAnswerId=22674748http:///Programming/Languages/SQL_Syntax/Q_23788341.html#a22674748http:///Programming/Languages/SQL_Syntax/Q_23788341.html  what do you think?

hnasr...  grayl might be on to something here...  What do you think about this?

closed in interest of clarity