C-Box

you could also use the AnchorNameExpression as we do for that purpose. This is also quite seldom used. just my two cents C-Box

In what band you have put your subreports? This message comes only if you put an stretching subreport in static bands (like page-footer/header)?!?!?!? You should attach your JRXML again. I must throw an eye on it, so it's easier to see what you've changed. If a textelement overlaps subreport content then you the textelement is not set to position-type = float. So please attach your JRXML. till later C-Box

What Page-Format have you set for your report (width & height)? And what band-height do you set for your DummyGroupHeader/FooterBands. If you JUST have the SubReport-Element in your DummyGroupHeader/FooterBand and no other elements.. then you can set the band height to just 1 pixel because the subreport stretches itself. The SubReport-Element is then of course also just 1 pixel. So 10 groups for 10 subreports would just cause 10 pixel more space. I do have up to 13 groups.... for an A4 page --> no problem! hth C-Box

Just take this as TextField-Expression (set the class to java.lang.String for that TextField): Code:$F{YourBooleanFieldFromDB}?"1":"0" this is the short If-Then-Else Expression. hth C-Box

Well this is something I think I can help you. I have made a so called "FilterableDTODataSource". As I do also show Master Child Relations within my reports I do put all my SubReports (as JasperReport Objects) and all its CustomDataSources (as FilterableDTODataSource Objects) in a container object that holds these SubReports and DataSources. In the design I made following SubReport-Expression: Code:$P{DataContainer}.getSubReportByName("MyNeededSubReportNumber1"«») this method at my DataContainer returns a JasperReport Object by the name that I've given it before. the DataSourceExpression looks like this: Code:[code]$P{DataContainer}.getDataSourceByName("MyNeededDataSourceNumber1","NameOf TheMatchingFieldInChildDataSourceLikeParentId",$F{Id}) This method returns my FilterableDTODataSource that does following things before returning: gets the datasource from the list in the container make a clone of this (because of reuse in nested subreports) if needed call the method "moveFirst" to the cloned datasource set the attribute "filterFieldName" to the given Name (in my sample "NameOfTheMatchingFieldInChildDataSourceLikeParentId" set the attribute "filterValue" to the value that is passed into (in my sample the Value of the field "Id" from parent master datasource) return this FilterableDTODataSource[/ol] the "next" Method in this FilterableDTODataSource filters out the records that fullfill the filter criteria (filterFieldName + filterValue) so I do work up to 13 SubReports with its related SubDataSources... and I do even have nested SubReports that reuse the same DataSource that the upper SubReports already loops through... works great since 2 years with our Server Client Enterprise Application. finally: every a thing of your creativity - JasperReports is therefor the best choice!!! ;) hth + good Luck C-Box

Just a hint again: Don't make Bands too large in height that just contains SubReports. The SubReport-Element can only be 1 Pixel high as the SubReport itself stretches as needed by its design and data. If you make it too large it can happen, that the "unused" space is moved forward that could (!!!) cause empty space - even empty pages. So jus my two cents (again) ;) C-Box

Have you set your Style "HeaderBold" also to the elements that should be bold? I think just adding a style without using it, doesn't work. Just select all your elements within iReport and set the style in the properties dialog. hth C-Box

again me: you should also play around a bit with PositionType = FLOAT instead of FixRelativeToTop Your SubReports are stretching itself so it's no need to reserve the space for them. Just put your elements below each other and set Postion type to FLOAT so it moves downwards itself. hth C-Box

[color=#FF0000]AHHHHHHHHHHHHHHHHHHHHHHHHHHHH! [/color]What is this???? I've seen many Reports but this "design" is quite "space-waste"....:blink: So your empty space comes from the [color=#FF0000]really really big[/color] detailband..... you must be carefull with space between the last element and the band-bottom... also with empty space to get some distance between fields.... Try to build some dummy-groups see the Tips-And-Tricks at JasperHomePage ... there is (was!?!?) a tip from Teodor how to handle such big bands! :-)You must know the page-break logic of JR a bit and make your design fitting this logic. hthC-Box Post edited by: CBox, at: 2006/09/19 13:50

?!?! We do just send the JasperPrint Object back to the client that displays this Object in it's viewer... so you should just create your output as JasperPrint or PDF and send the result back to client. The JasperViewer has nothing to do within a server-class. (our server = JBoss - our clients = handmade) ;) hth C-Box

I Don't understand... if you already have an own Formater-Class where is the problem and how can the date-string (I guess you return it as java.lang.String) contain spaces between some parts? Isn't it part of your Formater-Class to return a string fitting your own needs? So it can't be a Jasper-Matter, or what I don't understand!??!?! second - if you id field is variable length.. you should make it as wide as it can max be. (so in your case 15 chars). Then it doesn't break itself.... and if it doesn't stretch it can't influence the other output. Are your dates side by side or below? So as I use our dates also as String objects (depending at a global setting within our ERP-System) I don't have problems with patterns etc. hth C-Box

a bit few information... what's the problem actually? Are there any data missing? Do you want just 5 empty pages with pure static text? More info = more answers! ;) C-Box

Well I guess you should think about another solution than passing a dummy query to your main report... Try to create for each SubReport a DummyGroup (without an expression) and place the subreport in each Dummygroupheader-band.... so you can pass either an empty-datasource to your masterreport (if you don't need any data for it) or you pass your master-query to it (if you want to show some (meta)data). Placing many Subreports in just ONE band is (as I experienced) no good solution as the remaining space calculation and the page-break logic becomes more a random game than a defined way. Sometimes Subreports overlap each other even, if you don't set float etc..... So DummyGroupBands are much better for many subreports. just my two cents C-Box

Don't know if I understood your problem right but here my thoughts: Your Boolean-StatusField from query: $F{YourStatusBooleanField} that is TRUE or FALSE Your Textfield-1: $F{YourTextField1} Your Textexpression for that field should be: $F{YourStatusBooleanField}? $F{YourTextField1} + " YES":$F{YourTextField1} + " NO" Means in simple minds: append the String " YES" to your first Textfield if your statusfield is TRUE.... otherwise append String " NO". Do the other two fields of course the same way! That's how I did interprete your question, if wrong please post again (more precisely). hth C-Box

Hi Guilio, first: COOL new Forum! :woohoo: second: I just upgraded from 1.2.2 to 1.2.6 (due the lack of sparetime :( )and I really like the new design - but of course the repositioning of all the frames is very annoying. :S Would you please remember the size and position of iReport MainFrame and of all its child frames (element options etc). Would be a dream! ;) regards from sunny Germany C-Box