Report to show open tasks

[Sam]

Hello, I'm trying to create a report where it shows tasks that have not been
completed.

We track packages and when the contents inside are completed. So basically,
once the package is received and the "GivenToDate" field is filled in, that
is considered started. "EnteredByDate" field filled in is considered the
package finished/closed.

What I'm trying to do is see in a user specified time frame (open for an X
amount of hours) in which a package has been started, but NOT finished. So if
"EnteredByDate" is not filled in, that is considered not completed.

So lets say we want to know which pages have been given to an employee and
have been open/not finished for 24 hours.

How would I go about doing this? Thank you!

 

[Evi]

If different tasks may want different completion times then add a number
field to your Tasks table Comp (for Complete by).
If it is categories of tasks that have those different completion times then
add the number field to your Category table.

If you want to count the time given to employees to finish a task in hours
rather than days then in the example you give you would put 24 in the field
for that task/category of task (otherwise you would put 1 if you were
counting in days).
You can always specify a Default Value of say 24 in the table if most tasks
have to be completed within 24 hours.

Base a table on your Tasks table which includes this Comp field
In your query write into one column (if counting completion time in hours)
Due: IIf(IsNull([EndDate]),[StartDate]+([Comp]/24))
Or if you are counting in days:
Due: IIf(IsNull([EndDate]),[StartDate]+[Comp])
Filter the EndDate field by
Is Null
Filter the Due field by
<=Now()
Base a report on this query

Evi

 

[Sam]

Without adding anything extra, is there anyway to do it by days instead of
hours? It would be fine to say... "based from today, these tasks have not
been completed in 1 day". So, Access would pull up todays date and then count
how many days since RecievedByDate there have been, and then show a report on
which have been null for more than a day from today.

If different tasks may want different completion times then add a number
field to your Tasks table Comp (for Complete by).
If it is categories of tasks that have those different completion times then
add the number field to your Category table.

If you want to count the time given to employees to finish a task in hours
rather than days then in the example you give you would put 24 in the field
for that task/category of task (otherwise you would put 1 if you were
counting in days).
You can always specify a Default Value of say 24 in the table if most tasks
have to be completed within 24 hours.

Base a table on your Tasks table which includes this Comp field
In your query write into one column (if counting completion time in hours)
Due: IIf(IsNull([EndDate]),[StartDate]+([Comp]/24))
Or if you are counting in days:
Due: IIf(IsNull([EndDate]),[StartDate]+[Comp])
Filter the EndDate field by
Is Null
Filter the Due field by
<=Now()
Base a report on this query

Evi

Hello, I'm trying to create a report where it shows tasks that have not been
completed.

We track packages and when the contents inside are completed. So basically,
once the package is received and the "GivenToDate" field is filled in, that
is considered started. "EnteredByDate" field filled in is considered the
package finished/closed.

What I'm trying to do is see in a user specified time frame (open for an X
amount of hours) in which a package has been started, but NOT finished. So if
"EnteredByDate" is not filled in, that is considered not completed.

So lets say we want to know which pages have been given to an employee and
have been open/not finished for 24 hours.

How would I go about doing this? Thank you!

 

[Sam]

Okay, I completely overlooked your day answer, thanks. However, I still have
that one question. Is it possible to just list the package(s) that has been
StartDate for more than 1 day from the current system date without adding any
extra fields?

Without adding anything extra, is there anyway to do it by days instead of
hours? It would be fine to say... "based from today, these tasks have not
been completed in 1 day". So, Access would pull up todays date and then count
how many days since RecievedByDate there have been, and then show a report on
which have been null for more than a day from today.

If different tasks may want different completion times then add a number
field to your Tasks table Comp (for Complete by).
If it is categories of tasks that have those different completion times then
add the number field to your Category table.

If you want to count the time given to employees to finish a task in hours
rather than days then in the example you give you would put 24 in the field
for that task/category of task (otherwise you would put 1 if you were
counting in days).
You can always specify a Default Value of say 24 in the table if most tasks
have to be completed within 24 hours.

Base a table on your Tasks table which includes this Comp field
In your query write into one column (if counting completion time in hours)
Due: IIf(IsNull([EndDate]),[StartDate]+([Comp]/24))
Or if you are counting in days:
Due: IIf(IsNull([EndDate]),[StartDate]+[Comp])
Filter the EndDate field by
Is Null
Filter the Due field by
<=Now()
Base a report on this query

Evi

Hello, I'm trying to create a report where it shows tasks that have not been
completed.

We track packages and when the contents inside are completed. So basically,
once the package is received and the "GivenToDate" field is filled in, that
is considered started. "EnteredByDate" field filled in is considered the
package finished/closed.

What I'm trying to do is see in a user specified time frame (open for an X
amount of hours) in which a package has been started, but NOT finished. So if
"EnteredByDate" is not filled in, that is considered not completed.

So lets say we want to know which pages have been given to an employee and
have been open/not finished for 24 hours.

How would I go about doing this? Thank you!

 

[Marshall Barton]

If it's always one day, you can put that in the query
instead of a table. This is not a good way to do things,
but if you can not change the table, what else can you do.
Just add a calcuated field in the query:
DateDiff("d", StartDate, Date())
with the criteria:

1

--
Marsh
MVP [MS Access]

Okay, I completely overlooked your day answer, thanks. However, I still have
that one question. Is it possible to just list the package(s) that has been
StartDate for more than 1 day from the current system date without adding any
extra fields?

Without adding anything extra, is there anyway to do it by days instead of
hours? It would be fine to say... "based from today, these tasks have not
been completed in 1 day". So, Access would pull up todays date and then count
how many days since RecievedByDate there have been, and then show a report on
which have been null for more than a day from today.

If different tasks may want different completion times then add a number
field to your Tasks table Comp (for Complete by).
If it is categories of tasks that have those different completion times then
add the number field to your Category table.

If you want to count the time given to employees to finish a task in hours
rather than days then in the example you give you would put 24 in the field
for that task/category of task (otherwise you would put 1 if you were
counting in days).
You can always specify a Default Value of say 24 in the table if most tasks
have to be completed within 24 hours.

Base a table on your Tasks table which includes this Comp field
In your query write into one column (if counting completion time in hours)
Due: IIf(IsNull([EndDate]),[StartDate]+([Comp]/24))
Or if you are counting in days:
Due: IIf(IsNull([EndDate]),[StartDate]+[Comp])
Filter the EndDate field by
Is Null
Filter the Due field by
<=Now()
Base a report on this query

Evi


Hello, I'm trying to create a report where it shows tasks that have not
been
completed.

We track packages and when the contents inside are completed. So
basically,
once the package is received and the "GivenToDate" field is filled in,
that
is considered started. "EnteredByDate" field filled in is considered the
package finished/closed.

What I'm trying to do is see in a user specified time frame (open for an X
amount of hours) in which a package has been started, but NOT finished. So
if
"EnteredByDate" is not filled in, that is considered not completed.

So lets say we want to know which pages have been given to an employee and
have been open/not finished for 24 hours.

How would I go about doing this? Thank you!

 

[Sam]

That does work, but not necessarily how I would like. I'd like to only show
the packages that do not have the EnteredByDate filled in (so if it is not
filled in, that is considered not finished).

If it's always one day, you can put that in the query
instead of a table. This is not a good way to do things,
but if you can not change the table, what else can you do.
Just add a calcuated field in the query:
DateDiff("d", StartDate, Date())
with the criteria:
>1
--
Marsh
MVP [MS Access]

Okay, I completely overlooked your day answer, thanks. However, I still have
that one question. Is it possible to just list the package(s) that has been
StartDate for more than 1 day from the current system date without adding any
extra fields?

Without adding anything extra, is there anyway to do it by days instead of
hours? It would be fine to say... "based from today, these tasks have not
been completed in 1 day". So, Access would pull up todays date and then count
how many days since RecievedByDate there have been, and then show a report on
which have been null for more than a day from today.

:

If different tasks may want different completion times then add a number
field to your Tasks table Comp (for Complete by).
If it is categories of tasks that have those different completion times then
add the number field to your Category table.

If you want to count the time given to employees to finish a task in hours
rather than days then in the example you give you would put 24 in the field
for that task/category of task (otherwise you would put 1 if you were
counting in days).
You can always specify a Default Value of say 24 in the table if most tasks
have to be completed within 24 hours.

Base a table on your Tasks table which includes this Comp field
In your query write into one column (if counting completion time in hours)
Due: IIf(IsNull([EndDate]),[StartDate]+([Comp]/24))
Or if you are counting in days:
Due: IIf(IsNull([EndDate]),[StartDate]+[Comp])
Filter the EndDate field by
Is Null
Filter the Due field by
<=Now()
Base a report on this query

Evi


Hello, I'm trying to create a report where it shows tasks that have not
been
completed.

We track packages and when the contents inside are completed. So
basically,
once the package is received and the "GivenToDate" field is filled in,
that
is considered started. "EnteredByDate" field filled in is considered the
package finished/closed.

What I'm trying to do is see in a user specified time frame (open for an X
amount of hours) in which a package has been started, but NOT finished. So
if
"EnteredByDate" is not filled in, that is considered not completed.

So lets say we want to know which pages have been given to an employee and
have been open/not finished for 24 hours.

How would I go about doing this? Thank you!

 

[Tom Lake]

That does work, but not necessarily how I would like. I'd like to only show
the packages that do not have the EnteredByDate filled in (so if it is not
filled in, that is considered not finished).

In the criteria field of the EnteredByDate put Is Null

Tom Lake

 

[Sam]

Amazing! Thank you. Now, my last question... I swear. Is there anyway to put
a default value in the StartDate popup that comes up when I run the report
for StartDate? Preferably the current system date so the user doesn't have to
type it in all the time.

Happy Holidays.