locked
Seperate Groups Without a Page Break RRS feed

  • Question

  • I am creating a quote activity report. The report needs to have a seperate table for each quoter along with some details concerning each quoter that is not in the table. It should look like the following.

    Project Manager:
    Total Quote $:
    Quote Count:

    Table goes here that displays details concerning individual quotes for this quoter.

    _______________________ A Line (Not a Page Break) _______________

    Project Manager:
    Total Quote $:
    Quote Count:

    Table goes here that displays details concerning individual quotes for this quoter.

    _______________________ A Line (Not a Page Break) _______________

    Project Manager:
    Total Quote $:
    Quote Count:

    Table goes here that displays details concerning individual quotes for this quoter.

    _______________________ A Line (Not a Page Break) _______________

    I have not been able to figure out how to seperate the tables this way without a page break.

    Tuesday, November 23, 2010 3:32 PM

Answers

  • I ended up solving this by creating a sub report. I prefer not to use sub reports but it worked.

    • Marked as answer by Tony Chain Tuesday, November 30, 2010 1:28 AM
    Monday, November 29, 2010 1:50 PM

All replies

  • Well you can have a text box in between two tables,

    Make Bottom/Top border visible. and here you go , you will have a line in between .


    Gaurav Gupta http://sqlservermsbiblog.blogspot.com/
    Tuesday, November 23, 2010 5:18 PM
  • Hi Scott Hanebutt,

    Based on the example you posted, could you posted more details about the organization of tables in the report in Design mode. By generally, we could achieve this by using only one table with multi-level groups or using table nested in a list control. So how do you achieve this? Or if I have something understand, please also let me know.

     

    Thanks,
    Tony Chain


    Please remember to mark the replies as answers if they help and unmark them if they provide no help
    Thursday, November 25, 2010 7:15 AM
  • I ended up solving this by creating a sub report. I prefer not to use sub reports but it worked.

    • Marked as answer by Tony Chain Tuesday, November 30, 2010 1:28 AM
    Monday, November 29, 2010 1:50 PM