Report formatting hangs
in [Reports]
|
From: Tara on 2 Jun 2010 13:23 I have a report (rptHV) that uses a query (qryHV) as its record source. The user opens a form (frmHVClient), chooses a name from a combo box, and then clicks a command button (cmdClient) to run the report. The report works fine as long as certain client names are not chosen. If those certain client names are chosen, a progress bar appears in the status area with the message, "Formatting report - press ctrl + Break to stop..." and the report hangs and never formats at all. Coincidentally (or not) the clients that cause the issue are all assigned to the same staff member. I've looked at the data in those records several times and everything appears normal, so I'm at a loss as to why this is happening.
From: Allen Browne on 2 Jun 2010 23:17 This is probably to so with the properties of the sections and groupings. It may be attempting to find a solution that's not possible. To test if this is the problem, open the report in design view. In the Sorting and Grouping box, make sure that each group header/foot is set to "Do not keep together." If that doesn't solve it, right-click the Detail section, and choose Properties. On the Format tab of the properties box, set Keep Together to No. Repeat for the other sections on the report. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Tara" <Tara(a)discussions.microsoft.com> wrote in message news:355DD739-733B-4436-9FF3-182826071C72(a)microsoft.com... > I have a report (rptHV) that uses a query (qryHV) as its record source. > The > user opens a form (frmHVClient), chooses a name from a combo box, and then > clicks a command button (cmdClient) to run the report. The report works > fine > as long as certain client names are not chosen. If those certain client > names are chosen, a progress bar appears in the status area with the > message, > "Formatting report - press ctrl + Break to stop..." and the report hangs > and > never formats at all. Coincidentally (or not) the clients that cause the > issue are all assigned to the same staff member. I've looked at the data > in > those records several times and everything appears normal, so I'm at a > loss > as to why this is happening.
From: Tara on 3 Jun 2010 10:18 The second suggestion fixed it! Now I just have to figure out why it's having trouble with the grouping... Thanks so much! "Allen Browne" wrote: > This is probably to so with the properties of the sections and groupings. It > may be attempting to find a solution that's not possible. > > To test if this is the problem, open the report in design view. In the > Sorting and Grouping box, make sure that each group header/foot is set to > "Do not keep together." > > If that doesn't solve it, right-click the Detail section, and choose > Properties. On the Format tab of the properties box, set Keep Together to > No. Repeat for the other sections on the report. > > -- > Allen Browne - Microsoft MVP. Perth, Western Australia > Tips for Access users - http://allenbrowne.com/tips.html > Reply to group, rather than allenbrowne at mvps dot org. > > > "Tara" <Tara(a)discussions.microsoft.com> wrote in message > news:355DD739-733B-4436-9FF3-182826071C72(a)microsoft.com... > > I have a report (rptHV) that uses a query (qryHV) as its record source. > > The > > user opens a form (frmHVClient), chooses a name from a combo box, and then > > clicks a command button (cmdClient) to run the report. The report works > > fine > > as long as certain client names are not chosen. If those certain client > > names are chosen, a progress bar appears in the status area with the > > message, > > "Formatting report - press ctrl + Break to stop..." and the report hangs > > and > > never formats at all. Coincidentally (or not) the clients that cause the > > issue are all assigned to the same staff member. I've looked at the data > > in > > those records several times and everything appears normal, so I'm at a > > loss > > as to why this is happening. > > . >
From: John Spencer on 3 Jun 2010 14:06 Usually, the amount of the data in the section is TOO large to keep together. So Access looks for another page to put it on, but if the amount of data is too large to fit on one page Access looks for another page and ... John Spencer Access MVP 2002-2005, 2007-2010 The Hilltop Institute University of Maryland Baltimore County Tara wrote: > The second suggestion fixed it! Now I just have to figure out why it's > having trouble with the grouping... > > Thanks so much! > > "Allen Browne" wrote: > >> This is probably to so with the properties of the sections and groupings. It >> may be attempting to find a solution that's not possible. >> >> To test if this is the problem, open the report in design view. In the >> Sorting and Grouping box, make sure that each group header/foot is set to >> "Do not keep together." >> >> If that doesn't solve it, right-click the Detail section, and choose >> Properties. On the Format tab of the properties box, set Keep Together to >> No. Repeat for the other sections on the report. >> >> -- >> Allen Browne - Microsoft MVP. Perth, Western Australia >> Tips for Access users - http://allenbrowne.com/tips.html >> Reply to group, rather than allenbrowne at mvps dot org. >> >> >> "Tara" <Tara(a)discussions.microsoft.com> wrote in message >> news:355DD739-733B-4436-9FF3-182826071C72(a)microsoft.com... >>> I have a report (rptHV) that uses a query (qryHV) as its record source. >>> The >>> user opens a form (frmHVClient), chooses a name from a combo box, and then >>> clicks a command button (cmdClient) to run the report. The report works >>> fine >>> as long as certain client names are not chosen. If those certain client >>> names are chosen, a progress bar appears in the status area with the >>> message, >>> "Formatting report - press ctrl + Break to stop..." and the report hangs >>> and >>> never formats at all. Coincidentally (or not) the clients that cause the >>> issue are all assigned to the same staff member. I've looked at the data >>> in >>> those records several times and everything appears normal, so I'm at a >>> loss >>> as to why this is happening. >> . >>
|
Pages: 1 Prev: Multiple Queries...? Next: Highlighting a word when it shows up on a report |