Is there a way to have multiple groupings for a single dataset in a table's
detail row? I need to be able to hide individual grouped data, but still
need to see the hidden data aggregated in the footer row of the table.
The purpose is to make the report easy to read for troubleshooting by hiding
issues that aren't that important but still need to be calculated. Any help
would be greatly appreciated.No
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"joelnbtx" <joelnbtx@.discussions.microsoft.com> wrote in message
news:9783877A-C8AA-4E51-A49F-4EB1D6CC2463@.microsoft.com...
> Is there a way to have multiple groupings for a single dataset in a
> table's
> detail row? I need to be able to hide individual grouped data, but still
> need to see the hidden data aggregated in the footer row of the table.
> The purpose is to make the report easy to read for troubleshooting by
> hiding
> issues that aren't that important but still need to be calculated. Any
> help
> would be greatly appreciated.sql
Showing posts with label detail. Show all posts
Showing posts with label detail. Show all posts
Friday, March 23, 2012
Multiple Group/Detail Records are not showing
I have a report with a page header, a report header and footer, and many group headers, one group / detail line, and some group footers.
The problem is that only one record per ID is allowed in the one group/detail line. Both records per ID will show in data view but not in the report output. I do not have "allow duplicates" selected anywhere that I am aware of.
Where else can I look?
Thanks,
cj
multiple formulas when suppressing a detail section
I have a report, details a and details b. i need details b to show when a series of formulas are met.
I am having trouble getting this to work:
{loan_main.datepurchased} <> {?Date Purchased} AND not ({loan_query.reivname} like "*wells*")
AND is not performing an AND...
help me please.
thank you :confused::eek: 'AND is not performing an AND...' ?
As you said, you want to show the records when
{loan_main.datepurchased} <> {?Date Purchased} AND not ({loan_query.reivname} like "*wells*")
Right?
I've created a similar formula and it works but in the apposit way: the records which met such a condition are suppressed.
So...... if you want to show those records may be you will change your formula like that:
{loan_main.datepurchased} = {?Date Purchased} AND {loan_query.reivname} like "*wells*" //?
...or correct me if I understood something wrong, please.|||You are correct. I need to show records that meet the criteria, thus i am suppressing records that are on either side.
so, i need to suppress all records
{loan_main.datepurchased} <> {?Date Purchased} AND not ({loan_query.reivname} like "*wells*")
so i would get all loans that are purchased on the date entered upon running the report AND all loans that reivname like wells...
i hope this makes sense.
i am suppressing all the records that do not meet the daily criteria.
thank you|||I've understood what you've written to mean that you want the records with a purchase date of ?DatePurchased, (note the comma) and you want names like wells. i.e. the date is irrelevant for 'wells'.
If so, you want an OR, not an AND.
I find it's easier to write the formula for what records you actually want, and then NOT the whole thing for the suppression formula. e.g.
not( <what you want> )|||I appreciate all help i can get ;)
is it possible to select only the records i want for one section? detail section A is working great, i am having this problem when working with detail section B.
If i can only select records for details section B, i am set...
if not, then besides having two reports, this is it... i think...
i have tried the OR. I need all records that are LIKE 'wells' and date selected is the date purchased.
any help and all help is appreciated.
thank you|||I'm afraid it's still not clear (to me!).
"so i would get all loans that are purchased on the date entered upon running the report AND all loans that reivname like wells..."
The stress on the AND implies to me that you want the union of two sets of data:
1) date entered
2) like wells
i.e. the date is irrelevant for the wells' records, get them all regardless of their date. For non-wells records, base it on the date.
But "I need all records that are LIKE 'wells' and date selected is the date purchased." implies to me that you want
1) date entered and like wells
i.e. only records which satisfy both criteria at once, being wells records for that date.
So which is it?
Maybe you could start at the beginning for us to understand better. e.g. what's in your record selection formula, what you want in detailsA, what you want in detailsB, and whether one record can appear in both detail sections or if they are mutually exclusive.
If mutually exclusive the suppression formulas would be almost the same, e.g. one would be "<formula>" while the other would be "not(<formula>)".|||yes, sorry for the confusion - this report confused me in the beginning too...
I need all records that fit both criteria, datepurchased and like wells.
not one or the other, has to be the date and like wells...
that is why i am trying to use the AND.
hope this makes sense.
thank you...
details A has no formula attached, it shows all records.
thank you|||So I think we've decided that the records you want to show in detailsB are the ones that match both criteria at once :)
The ones you want are therefore:
{loan_main.datepurchased} = {?Date Purchased} AND {loan_query.reivname} like "*wells*"
So the suppression formula is:
NOT (
{loan_main.datepurchased} = {?Date Purchased} AND {loan_query.reivname} like "*wells*"
)
And as someone suggested in a different forum, can either of these fields be NULL?
Also, could 'wells' actually be 'Wells' or 'WELLS' etc.?|||Thank you sooooo much. it worked... :)
i appreciate your help and patience.
thank you sooo much again. it means a lot for the help...|||Glad we got there!
And the reason I always use not(<what I want>) for suppression is because trying to work out the inverse yourself is messy.
e.g. your requirement was effectively "a=x AND b like y"
I believe the logical inverse of that is
not(A<>x OR not(b like y))
which is nearly what you started with, but is nowhere near as easy to understand as what you ended up with.|||I agree. I havent really worked much with crystal, so it is still a learning curve for me... i will deffo use the way you suggested for any future reports.
thank you
I am having trouble getting this to work:
{loan_main.datepurchased} <> {?Date Purchased} AND not ({loan_query.reivname} like "*wells*")
AND is not performing an AND...
help me please.
thank you :confused::eek: 'AND is not performing an AND...' ?
As you said, you want to show the records when
{loan_main.datepurchased} <> {?Date Purchased} AND not ({loan_query.reivname} like "*wells*")
Right?
I've created a similar formula and it works but in the apposit way: the records which met such a condition are suppressed.
So...... if you want to show those records may be you will change your formula like that:
{loan_main.datepurchased} = {?Date Purchased} AND {loan_query.reivname} like "*wells*" //?
...or correct me if I understood something wrong, please.|||You are correct. I need to show records that meet the criteria, thus i am suppressing records that are on either side.
so, i need to suppress all records
{loan_main.datepurchased} <> {?Date Purchased} AND not ({loan_query.reivname} like "*wells*")
so i would get all loans that are purchased on the date entered upon running the report AND all loans that reivname like wells...
i hope this makes sense.
i am suppressing all the records that do not meet the daily criteria.
thank you|||I've understood what you've written to mean that you want the records with a purchase date of ?DatePurchased, (note the comma) and you want names like wells. i.e. the date is irrelevant for 'wells'.
If so, you want an OR, not an AND.
I find it's easier to write the formula for what records you actually want, and then NOT the whole thing for the suppression formula. e.g.
not( <what you want> )|||I appreciate all help i can get ;)
is it possible to select only the records i want for one section? detail section A is working great, i am having this problem when working with detail section B.
If i can only select records for details section B, i am set...
if not, then besides having two reports, this is it... i think...
i have tried the OR. I need all records that are LIKE 'wells' and date selected is the date purchased.
any help and all help is appreciated.
thank you|||I'm afraid it's still not clear (to me!).
"so i would get all loans that are purchased on the date entered upon running the report AND all loans that reivname like wells..."
The stress on the AND implies to me that you want the union of two sets of data:
1) date entered
2) like wells
i.e. the date is irrelevant for the wells' records, get them all regardless of their date. For non-wells records, base it on the date.
But "I need all records that are LIKE 'wells' and date selected is the date purchased." implies to me that you want
1) date entered and like wells
i.e. only records which satisfy both criteria at once, being wells records for that date.
So which is it?
Maybe you could start at the beginning for us to understand better. e.g. what's in your record selection formula, what you want in detailsA, what you want in detailsB, and whether one record can appear in both detail sections or if they are mutually exclusive.
If mutually exclusive the suppression formulas would be almost the same, e.g. one would be "<formula>" while the other would be "not(<formula>)".|||yes, sorry for the confusion - this report confused me in the beginning too...
I need all records that fit both criteria, datepurchased and like wells.
not one or the other, has to be the date and like wells...
that is why i am trying to use the AND.
hope this makes sense.
thank you...
details A has no formula attached, it shows all records.
thank you|||So I think we've decided that the records you want to show in detailsB are the ones that match both criteria at once :)
The ones you want are therefore:
{loan_main.datepurchased} = {?Date Purchased} AND {loan_query.reivname} like "*wells*"
So the suppression formula is:
NOT (
{loan_main.datepurchased} = {?Date Purchased} AND {loan_query.reivname} like "*wells*"
)
And as someone suggested in a different forum, can either of these fields be NULL?
Also, could 'wells' actually be 'Wells' or 'WELLS' etc.?|||Thank you sooooo much. it worked... :)
i appreciate your help and patience.
thank you sooo much again. it means a lot for the help...|||Glad we got there!
And the reason I always use not(<what I want>) for suppression is because trying to work out the inverse yourself is messy.
e.g. your requirement was effectively "a=x AND b like y"
I believe the logical inverse of that is
not(A<>x OR not(b like y))
which is nearly what you started with, but is nowhere near as easy to understand as what you ended up with.|||I agree. I havent really worked much with crystal, so it is still a learning curve for me... i will deffo use the way you suggested for any future reports.
thank you
Multiple Files -- DTS
I have a rather large sale transaction DB. Basic header, and detail tables. I am providing a third party company with daily sales information, and I need to give them back data from about 8 or 9 months ago. I currently have a DTS package that gets sales for the current day, but since I have to go back, I have to manually edit the query in the DTS package, and change the date range...UNLESS ...
Blah, blah, blah. The problem is that they can only take the data in Daily files. So, there would be ONE file for each day. I really don't need to be manually running these jobs, so I'm wondering if someone could point me to a way of writing a package (maybe ActiveX, not sure) that would run through a loop, basically, of dates, and create a seperate file for each day. Versus having to edit a generic DTS package, and changing the date range 350 times...would it be an option to select the current daterange from a table. Then, as a last step, update daterange to the next (or have a daterange column and another column that acts as a 'done this one' and update that column)? If the package simply exports the table contents you could also consider creating a dynamic sp but I am not sure if that's an option for you.|||That does make sense, but I am not sure how I would go about "looping" through the Daterange, and then creating a file for each day based on the query that is in the one DTS package.|||This is what I've done, and it's led me to another question:
@.Date1=(SELECT BeginDate FROM DateRangeTable)
@.Date2=(SELECT EndDate FROM DateRangeTable)
...SELECT BLAH, BLAH...WHERE Date BETWEEN @.Date1 AND @.Date2
UPDATE DateRange SET Loaded='YES' WHERE BeginDate=@.Date1
EXEC master..xp_cmdshell 'REN I:\DailySales ' + @.Date1
--
By itself, the EXEC xp_cmdshell runs just fine. However, when I include The Main query, It doesn't work at all with NO errors...anyone know what gives?|||Does it have to be formatted a certain way? You could certainly do it in ActiveX, or simply use xp_cmdshell to execute BCP:
EXEC master..xp_cmdshell 'bcp ' + 'SELECT BLAH, BLAH...WHERE Date BETWEEN @.Date1 AND @.Date2'|||Yes, the DTS Package has a certain format that I haven't been able to figure out how to match with bcp.|||I haven't worked with BCP for sometime, but it does have a parameter for a "format file". If you can't get BCP to format it the way you want, you can do it in ActiveX.
Blah, blah, blah. The problem is that they can only take the data in Daily files. So, there would be ONE file for each day. I really don't need to be manually running these jobs, so I'm wondering if someone could point me to a way of writing a package (maybe ActiveX, not sure) that would run through a loop, basically, of dates, and create a seperate file for each day. Versus having to edit a generic DTS package, and changing the date range 350 times...would it be an option to select the current daterange from a table. Then, as a last step, update daterange to the next (or have a daterange column and another column that acts as a 'done this one' and update that column)? If the package simply exports the table contents you could also consider creating a dynamic sp but I am not sure if that's an option for you.|||That does make sense, but I am not sure how I would go about "looping" through the Daterange, and then creating a file for each day based on the query that is in the one DTS package.|||This is what I've done, and it's led me to another question:
@.Date1=(SELECT BeginDate FROM DateRangeTable)
@.Date2=(SELECT EndDate FROM DateRangeTable)
...SELECT BLAH, BLAH...WHERE Date BETWEEN @.Date1 AND @.Date2
UPDATE DateRange SET Loaded='YES' WHERE BeginDate=@.Date1
EXEC master..xp_cmdshell 'REN I:\DailySales ' + @.Date1
--
By itself, the EXEC xp_cmdshell runs just fine. However, when I include The Main query, It doesn't work at all with NO errors...anyone know what gives?|||Does it have to be formatted a certain way? You could certainly do it in ActiveX, or simply use xp_cmdshell to execute BCP:
EXEC master..xp_cmdshell 'bcp ' + 'SELECT BLAH, BLAH...WHERE Date BETWEEN @.Date1 AND @.Date2'|||Yes, the DTS Package has a certain format that I haven't been able to figure out how to match with bcp.|||I haven't worked with BCP for sometime, but it does have a parameter for a "format file". If you can't get BCP to format it the way you want, you can do it in ActiveX.
Wednesday, March 21, 2012
Multiple Detail Sections
I have created a report that is using a table with multiple groupings. My
main result set from a stored procedure populates the detail section of the
table. I have a secondary result set that I would like to populate based on a
value from the first result set. For example:
Detail 1 Customer 1
Detail 2 Order 1
Order 2
Order 3
Detail 2 is populated based on the customer id.
How can I accomplish this using the report authoring tool?
Any help would be appreciated.Assuming you are not trying to do a table with groupings, this can be
accomplished with nested "List" items (a list inside of a list) which allow
a free form layout. You just bind each list to the correct dataset for your
detail. See the Sample Reports for an example.
"Scott2624" <Scott2624@.discussions.microsoft.com> wrote in message
news:8411C050-B2FE-48B1-8E26-755220D4FD06@.microsoft.com...
>I have created a report that is using a table with multiple groupings. My
> main result set from a stored procedure populates the detail section of
> the
> table. I have a secondary result set that I would like to populate based
> on a
> value from the first result set. For example:
> Detail 1 Customer 1
> Detail 2 Order 1
> Order 2
> Order 3
> Detail 2 is populated based on the customer id.
> How can I accomplish this using the report authoring tool?
> Any help would be appreciated.
>
main result set from a stored procedure populates the detail section of the
table. I have a secondary result set that I would like to populate based on a
value from the first result set. For example:
Detail 1 Customer 1
Detail 2 Order 1
Order 2
Order 3
Detail 2 is populated based on the customer id.
How can I accomplish this using the report authoring tool?
Any help would be appreciated.Assuming you are not trying to do a table with groupings, this can be
accomplished with nested "List" items (a list inside of a list) which allow
a free form layout. You just bind each list to the correct dataset for your
detail. See the Sample Reports for an example.
"Scott2624" <Scott2624@.discussions.microsoft.com> wrote in message
news:8411C050-B2FE-48B1-8E26-755220D4FD06@.microsoft.com...
>I have created a report that is using a table with multiple groupings. My
> main result set from a stored procedure populates the detail section of
> the
> table. I have a secondary result set that I would like to populate based
> on a
> value from the first result set. For example:
> Detail 1 Customer 1
> Detail 2 Order 1
> Order 2
> Order 3
> Detail 2 is populated based on the customer id.
> How can I accomplish this using the report authoring tool?
> Any help would be appreciated.
>
Monday, March 19, 2012
Multiple Detail Rows Rendering in CSV
I'm not sure if this is the expected feature, but when I render a
simple table that has two detail rows to CSV the second row is appended
to the end of the first row. This does not happen in PDF/HTML/EXCEL.
Here how the report is designed:
Table
Column1|Column2|Column3
TextBox1|TextBox2|TextBox3
TextBox4|TextBox5|TextBox6
In Excel, the output is:
1,2,3
a,b,c
4,5,6
a,b,c
In CSV, the output is
1,2,3,a,b,c
4,5,6,a,b,c
Is there any way to get the output to work in CSV as it does in Excel?
Thanks
scottSome additional research and testing shows that this happens regardless
of if the two detail rows are in one table or two. If you put two
"single detail row" tables in seperate list boxes and have the list
boxes group by the same field you will end up with the same "look and
feel" in HTML/PDF/Excel view (Excel will be slightly different).
However, when saving to CSV the second table's row will be appended to
the end of the first table's row just like in the example above.
The dirty workaround to this is to save as Excel and then save as CSV.
However, the Excel render is much slower since there is a lot of extra
formatting and it produces a much larger file.
Is there any chance this is a bug? Am I setting something up wrong?
It also happens regardless of the encoding method (ASCII vs Unicode).
Is this by design?
Thanks for the help.
scott bieker
simple table that has two detail rows to CSV the second row is appended
to the end of the first row. This does not happen in PDF/HTML/EXCEL.
Here how the report is designed:
Table
Column1|Column2|Column3
TextBox1|TextBox2|TextBox3
TextBox4|TextBox5|TextBox6
In Excel, the output is:
1,2,3
a,b,c
4,5,6
a,b,c
In CSV, the output is
1,2,3,a,b,c
4,5,6,a,b,c
Is there any way to get the output to work in CSV as it does in Excel?
Thanks
scottSome additional research and testing shows that this happens regardless
of if the two detail rows are in one table or two. If you put two
"single detail row" tables in seperate list boxes and have the list
boxes group by the same field you will end up with the same "look and
feel" in HTML/PDF/Excel view (Excel will be slightly different).
However, when saving to CSV the second table's row will be appended to
the end of the first table's row just like in the example above.
The dirty workaround to this is to save as Excel and then save as CSV.
However, the Excel render is much slower since there is a lot of extra
formatting and it produces a much larger file.
Is there any chance this is a bug? Am I setting something up wrong?
It also happens regardless of the encoding method (ASCII vs Unicode).
Is this by design?
Thanks for the help.
scott bieker
Multiple Detail Lines
Hi Folks,
If you have multiple detail lines in a table, is there any way to keep them
on the same page?
Thanks,
GregI am running into the same issue. It is creating a big problem for us.
--
James Scott
JaMMoN Enterprises, LLC
"Greg Low [MVP]" wrote:
> Hi Folks,
> If you have multiple detail lines in a table, is there any way to keep them
> on the same page?
> Thanks,
> Greg
>
>|||Hi Greg,
Welcome to MSDN Managed Newsgroup!
From your descriptions, I understood you scenario when there is too much
rows in the data, it will be automatically separate into multiple pages
(for example, if there is 1000 rows in the table, you will have to see them
in around 20 pages). Do I address "multiple detail lines in a table"
correctly? If I have misunderstood your concern, please feel free to point
it out and show me some sample / reproduce steps.
Based on my knowledge, the number of rows will be determined by the height
of Report and you could configure the report to enlarge this number.
(Report -> Report Properties -> Layout -> Page Height)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
The issue that we are facing is we never know how tall an individual row is
going to be. One Key example is a comments field. That single textbox can
grow from .5in all the way to 4in depending on how detailed the PM is.
Is there any way to force a report to break page if it knows that the row is
going to spill over to the next page?
Thanks & Regards,
~James
--
James Scott
JaMMoN Enterprises, LLC
"Michael Cheng [MSFT]" wrote:
> Hi Greg,
> Welcome to MSDN Managed Newsgroup!
> From your descriptions, I understood you scenario when there is too much
> rows in the data, it will be automatically separate into multiple pages
> (for example, if there is 1000 rows in the table, you will have to see them
> in around 20 pages). Do I address "multiple detail lines in a table"
> correctly? If I have misunderstood your concern, please feel free to point
> it out and show me some sample / reproduce steps.
> Based on my knowledge, the number of rows will be determined by the height
> of Report and you could configure the report to enlarge this number.
> (Report -> Report Properties -> Layout -> Page Height)
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi James,
>> Is there any way to force a report to break page if it knows that the
row is
>> going to spill over to the next page?
No, I am afraid report could not tell itself to make a break page when row
is going to spill over to the next page.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||OK, thanks for the confirmation..
Regards,
~James
--
James Scott
JaMMoN Enterprises, LLC
"Michael Cheng [MSFT]" wrote:
> Hi James,
> >> Is there any way to force a report to break page if it knows that the
> row is
> >> going to spill over to the next page?
> No, I am afraid report could not tell itself to make a break page when row
> is going to spill over to the next page.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
If you have multiple detail lines in a table, is there any way to keep them
on the same page?
Thanks,
GregI am running into the same issue. It is creating a big problem for us.
--
James Scott
JaMMoN Enterprises, LLC
"Greg Low [MVP]" wrote:
> Hi Folks,
> If you have multiple detail lines in a table, is there any way to keep them
> on the same page?
> Thanks,
> Greg
>
>|||Hi Greg,
Welcome to MSDN Managed Newsgroup!
From your descriptions, I understood you scenario when there is too much
rows in the data, it will be automatically separate into multiple pages
(for example, if there is 1000 rows in the table, you will have to see them
in around 20 pages). Do I address "multiple detail lines in a table"
correctly? If I have misunderstood your concern, please feel free to point
it out and show me some sample / reproduce steps.
Based on my knowledge, the number of rows will be determined by the height
of Report and you could configure the report to enlarge this number.
(Report -> Report Properties -> Layout -> Page Height)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael,
The issue that we are facing is we never know how tall an individual row is
going to be. One Key example is a comments field. That single textbox can
grow from .5in all the way to 4in depending on how detailed the PM is.
Is there any way to force a report to break page if it knows that the row is
going to spill over to the next page?
Thanks & Regards,
~James
--
James Scott
JaMMoN Enterprises, LLC
"Michael Cheng [MSFT]" wrote:
> Hi Greg,
> Welcome to MSDN Managed Newsgroup!
> From your descriptions, I understood you scenario when there is too much
> rows in the data, it will be automatically separate into multiple pages
> (for example, if there is 1000 rows in the table, you will have to see them
> in around 20 pages). Do I address "multiple detail lines in a table"
> correctly? If I have misunderstood your concern, please feel free to point
> it out and show me some sample / reproduce steps.
> Based on my knowledge, the number of rows will be determined by the height
> of Report and you could configure the report to enlarge this number.
> (Report -> Report Properties -> Layout -> Page Height)
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi James,
>> Is there any way to force a report to break page if it knows that the
row is
>> going to spill over to the next page?
No, I am afraid report could not tell itself to make a break page when row
is going to spill over to the next page.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||OK, thanks for the confirmation..
Regards,
~James
--
James Scott
JaMMoN Enterprises, LLC
"Michael Cheng [MSFT]" wrote:
> Hi James,
> >> Is there any way to force a report to break page if it knows that the
> row is
> >> going to spill over to the next page?
> No, I am afraid report could not tell itself to make a break page when row
> is going to spill over to the next page.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
Wednesday, March 7, 2012
multiple columns in details section
I have three fields in my report that make up each record. I would like to display these in detail section.
so instead of
1. alam Dept1 10000
2. khaiser dept2 20000
3. mujeeb dept2 20000
I would have
alam khaiser mujeeb ...
dept1 dept2 dept2 ...
10000 20000 20000 ..Use Crosstab Report|||1. Right-click on the dtails section, to open the Section Expert dialog box.
2. On the 'Sections' list, click the details section.
3. On the 'Common' tab, select 'Format with multiple columns' check box. A new tab called 'Layout' appears.
4. On the 'Layout' tab, specify the formatting for the columns:
Enter the width of the column in the 'Width' box. (you can set the height by dragging the section borders in the Design view of the report)
Enter the space between labels going across the page in the 'Horizontal gap' checkbox.
Enter the space between labels going down the page in the 'Vertical gap' box.
Select the printing direction, 'Across then Down' or 'Down then Across'.
Good Luck|||after using the Scetion expert i got mutliple columns but the sum of salary should be in right side but it is not coming ......
so instead of
1. alam Dept1 10000
2. khaiser dept2 20000
3. mujeeb dept2 20000
I would have
alam khaiser mujeeb ...
dept1 dept2 dept2 ...
10000 20000 20000 ..Use Crosstab Report|||1. Right-click on the dtails section, to open the Section Expert dialog box.
2. On the 'Sections' list, click the details section.
3. On the 'Common' tab, select 'Format with multiple columns' check box. A new tab called 'Layout' appears.
4. On the 'Layout' tab, specify the formatting for the columns:
Enter the width of the column in the 'Width' box. (you can set the height by dragging the section borders in the Design view of the report)
Enter the space between labels going across the page in the 'Horizontal gap' checkbox.
Enter the space between labels going down the page in the 'Vertical gap' box.
Select the printing direction, 'Across then Down' or 'Down then Across'.
Good Luck|||after using the Scetion expert i got mutliple columns but the sum of salary should be in right side but it is not coming ......
Subscribe to:
Posts (Atom)