RE: Year([due data]) causing problems in grouped report
- From: golfinray <golfinray@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 May 2009 11:10:01 -0700
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." wrote:
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??
- Follow-Ups:
- RE: Year([due data]) causing problems in grouped report
- From: Michelle K.
- RE: Year([due data]) causing problems in grouped report
- References:
- Year([due data]) causing problems in grouped report
- From: Michelle K.
- Year([due data]) causing problems in grouped report
- Prev by Date: Re: can grow text box
- Next by Date: select record value in a report
- Previous by thread: Year([due data]) causing problems in grouped report
- Next by thread: RE: Year([due data]) causing problems in grouped report
- Index(es):
Relevant Pages
|
