[AccessD] custom sorts/groups in a report

Hi Susan

Perhaps you On_Open of the report could set the value of a textbox to
the value of your chosen FirstDayOfWeek retrieved from your form; then
use the value of this textbox as a parameter in the function you use
for grouping/sorting in your report.

/gustav


> Sorry, Susan, but I just tuned in. <g>  

> I'm not clear on what you're doing so I'm not being much help.  I do
> dynamic reports for a week period and pass the start date to my report
> then let the report determine what day that is and populate an
> appropriate series of label captions to match.  I base it on a crosstab
> query, rebuilt for each report run, that uses dates as column headings
> and uses parameters to filter the dates.  I set the SQL for that
> crosstab query each time I use a form to call the report (no hand
> tweaking), and I generate an IN list of dates in the specified range to
> create the column headings.  I then use code in the Report_Open event to
> determine which field to bind to which control in the detail of the
> report.  Is that kind of what you're attempting to do?   

> Charlotte Foust

> -----Original Message-----
> From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
> Sent: Monday, April 19, 2004 11:52 AM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] custom sorts/groups in a report


 
> You can only group and sort on a field or an expression involving a
> field, and no, you can't use variables.  Had you mentioned the variable
> before? Why not just create a "week" field in the query and group and
> sort on that calculated field.  Then you could use your variable to
> create a filter for the particular week in question.

> ============I'm passing the firstdayoftheweek value from a form to the
> report -- the report's based on a query. So that's the quandry. That's
> what I mentioned in my last message -- the only way I can see around it
> is to pass the value to the query and run the expressions in the query
> first. I'm not sure I know how to do that really -- I have never passed
> anything to a query before -- just called functions from a query. And in
> this case, that's what I'm trying to avoid -- calling the function from
> the query. 

> Susan H.