Year([due data]) causing problems in grouped report

  • Thread starter Thread starter Michelle K.
  • Start date Start date
M

Michelle K.

I have a report that groups on a calculated field from the source query. The
calculated field is curryear=year([due date]). The database is in a shared
folder and is accessed by 15 other users through the network. The report has
been working wonderfully for 2 months and quite suddenly is not working on
about half of the computers -- and is right on the other half. Taking out
the group by curryear solves the problem. I'm also grouping by the week
number -- that still works. Any thoughts??
 
By any chance is this Access 2003? If so, have you loaded service pak 3 and
all the patches and hotfixes? It sounds like that kind of problem because
=Year([due date]) should normally work.
 
By any chance is this Access 2003? If so, have you loaded service pak 3 and
all the patches and hotfixes? It sounds like that kind of problem because
=Year([due date]) should normally work.
 
Thanks for the response. Yes, this is Access 2003, and no, I can't say for
sure that every computer has all the patches, etc. But . . . they have all
worked OK for the past two months -- which steers me away from the problem
being the lack of something and instead toward perhaps a new automatic
Windows or Office update being the root of the problem?? I haven't checked
yet to see what updates have been installed on each of the computers. It
looks like that's my next step unless someone comes up with another idea.
And I suspect that I will be able to solve the problem by using the DatePart
function instead of Year since that's still working to get the week number so
I do probably have a 'work-around', but I'd like to know why it quit working.

golfinray said:
By any chance is this Access 2003? If so, have you loaded service pak 3 and
all the patches and hotfixes? It sounds like that kind of problem because
=Year([due date]) should normally work.
--
Milton Purdy
ACCESS
State of Arkansas


Michelle K. said:
I have a report that groups on a calculated field from the source query. The
calculated field is curryear=year([due date]). The database is in a shared
folder and is accessed by 15 other users through the network. The report has
been working wonderfully for 2 months and quite suddenly is not working on
about half of the computers -- and is right on the other half. Taking out
the group by curryear solves the problem. I'm also grouping by the week
number -- that still works. Any thoughts??
Click to expand...
Click to expand...
 
Thanks for the response. Yes, this is Access 2003, and no, I can't say for
sure that every computer has all the patches, etc. But . . . they have all
worked OK for the past two months -- which steers me away from the problem
being the lack of something and instead toward perhaps a new automatic
Windows or Office update being the root of the problem?? I haven't checked
yet to see what updates have been installed on each of the computers. It
looks like that's my next step unless someone comes up with another idea.
And I suspect that I will be able to solve the problem by using the DatePart
function instead of Year since that's still working to get the week number so
I do probably have a 'work-around', but I'd like to know why it quit working.

golfinray said:
By any chance is this Access 2003? If so, have you loaded service pak 3 and
all the patches and hotfixes? It sounds like that kind of problem because
=Year([due date]) should normally work.
--
Milton Purdy
ACCESS
State of Arkansas


Michelle K. said:
I have a report that groups on a calculated field from the source query. The
calculated field is curryear=year([due date]). The database is in a shared
folder and is accessed by 15 other users through the network. The report has
been working wonderfully for 2 months and quite suddenly is not working on
about half of the computers -- and is right on the other half. Taking out
the group by curryear solves the problem. I'm also grouping by the week
number -- that still works. Any thoughts??
Click to expand...
Click to expand...
 
Is it possible that you have a Year function defined in your VBA code?
That will override the built-in function. Or if you have a field named
year, that could interfere in some cases.

Try specifying that you want to use the VBA Year function and see if
that makes a difference.
VBA.Year(Due_Date)

If that does work then you may have a custom function named year or one
of the other libraries (Tools: References) may have such a function and
it is getting called when you want the built-in VBA function.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

Thanks for the response. Yes, this is Access 2003, and no, I can't say for
sure that every computer has all the patches, etc. But . . . they have all
worked OK for the past two months -- which steers me away from the problem
being the lack of something and instead toward perhaps a new automatic
Windows or Office update being the root of the problem?? I haven't checked
yet to see what updates have been installed on each of the computers. It
looks like that's my next step unless someone comes up with another idea.
And I suspect that I will be able to solve the problem by using the DatePart
function instead of Year since that's still working to get the week number so
I do probably have a 'work-around', but I'd like to know why it quit working.

golfinray said:
By any chance is this Access 2003? If so, have you loaded service pak 3 and
all the patches and hotfixes? It sounds like that kind of problem because
=Year([due date]) should normally work.
--
Milton Purdy
ACCESS
State of Arkansas


Michelle K. said:
I have a report that groups on a calculated field from the source query. The
calculated field is curryear=year([due date]). The database is in a shared
folder and is accessed by 15 other users through the network. The report has
been working wonderfully for 2 months and quite suddenly is not working on
about half of the computers -- and is right on the other half. Taking out
the group by curryear solves the problem. I'm also grouping by the week
number -- that still works. Any thoughts??
Click to expand...
Click to expand...
Click to expand...
 
Is it possible that you have a Year function defined in your VBA code?
That will override the built-in function. Or if you have a field named
year, that could interfere in some cases.

Try specifying that you want to use the VBA Year function and see if
that makes a difference.
VBA.Year(Due_Date)

If that does work then you may have a custom function named year or one
of the other libraries (Tools: References) may have such a function and
it is getting called when you want the built-in VBA function.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

Thanks for the response. Yes, this is Access 2003, and no, I can't say for
sure that every computer has all the patches, etc. But . . . they have all
worked OK for the past two months -- which steers me away from the problem
being the lack of something and instead toward perhaps a new automatic
Windows or Office update being the root of the problem?? I haven't checked
yet to see what updates have been installed on each of the computers. It
looks like that's my next step unless someone comes up with another idea.
And I suspect that I will be able to solve the problem by using the DatePart
function instead of Year since that's still working to get the week number so
I do probably have a 'work-around', but I'd like to know why it quit working.

golfinray said:
By any chance is this Access 2003? If so, have you loaded service pak 3 and
all the patches and hotfixes? It sounds like that kind of problem because
=Year([due date]) should normally work.
--
Milton Purdy
ACCESS
State of Arkansas


Michelle K. said:
I have a report that groups on a calculated field from the source query. The
calculated field is curryear=year([due date]). The database is in a shared
folder and is accessed by 15 other users through the network. The report has
been working wonderfully for 2 months and quite suddenly is not working on
about half of the computers -- and is right on the other half. Taking out
the group by curryear solves the problem. I'm also grouping by the week
number -- that still works. Any thoughts??
Click to expand...
Click to expand...
Click to expand...
 
Back
Top