Gustav Brock
gustav at cactus.dk
Fri Jul 23 06:16:19 CDT 2004
Hi Stephen > Hi Gustav, you're up early! 11pm Friday here. Oh not at all, I'm in Europe - it's 13.00 hours here. > In the report, I am using the field FY. It presents in the Field List, and in the Sorting And Grouping drop box. > startDate is included in the detail line of the report. > Will try your suggestion and let you know. OK. /gustav > Stephen Bond >> -----Original Message----- >> From: Gustav Brock [mailto:gustav at cactus.dk] >> Sent: Friday, 23 July 2004 10:59 p.m. >> To: Access Developers discussion and problem solving >> Subject: Re: [AccessD] Report Grouping on a derived query field >> >> >> Hi Stephen >> >> How do you specify it in the report's headings and groupings >> specification? >> You may need to write the original expression: >> >> =IIf(Month(startDate) < 7, Year(startDate), 1 + Year(startDate)) >> >> Is startdate included as i (not visible) textbox in the report? >> >> /gustav >> >> >> > Access 2000 - >> > In a query which feeds a report I have a derived field. It >> is derived directly from a date field in one of the >> contributing tables, thus: >> >> > FY:Iif(Month(startDate) < 7, Year(startDate), 1+Year(startDate)) >> >> > The query runs perfectly, and gives me values like 2003, >> 2004 etc in the FY field. >> >> > I am using this derived field, FY, as a grouping level (the >> only grouping level) in the report. When I run the report, >> it bombs off immediately with the error message "The >> expression is typed >> > incorrectly, or is too complex to be evaluated ..." and >> more stuff about simplifying the expression. When I remove >> the Grouping Level completely the report runs. There is no >> code-behind-forms >> > (there will be but I have removed it to attempt to solve this). >> >> > Any Ideas? >> >> > TIA >> > Stephen Bond >> > Otatara, New Zealand