JamieDenman

Ensure any parameters that your subreport query uses are being passed in:- in main report go to the properties box of the sub-report element and go to Subreport (other) tab. And make sure the subreport is using the correct connection/datasource:- in Subreport tab

Good question, similar to about a hundred others asking about the formatting of iReport chart labels that have not been answered. I have been battling with this issue for days now and before anyone suggests RTFM: the F* manual is useless!! Maybe the site mods can group all these chart posts together and actually answer the question or address the issue that the charts are not really usable if there are more than a couple of data points as the labels cannot be read?

Yep, we're getting the same thing, but only on certain PC (it seems some update by MS last year did the damage) and it's either dependant on the version of MS Word or some JAVA update they decided to send out. No fix I'm affaid. I gave up offering exports of RTF (much quicker than trying to get the issue sorted!!), but have just been requested to provide one so am looking into this issue again. If anyone has a solution please post

What if your SQL does not retrieve the date field from your MySQL DB? I.E SELECT COUNT(*) FROM XXX WHERE XXX.DATE BETWEEN $P{STARTDATE} AND $P{ENDDATE} the XXX.DATE is set to MySQL timestamp (in MySQL) what is iReports treating it as. I have tried changing the parameter type in OpenReports but as I need a startdate and enddate for an Oracle query and for a MySQL query (in subreport) I need to manipulate the parameter to be able to use same selected date for both. Oracle seems "happy" to use a date from the calendar in OpenReports but not so for MySQL. Uses (as string) 01-11-2007 but MySQL will work with 2007-11-01 (as string) Is this a case of just manipulate the date as a string for MySQL rather than attempting to alter it to a timestamp in a different format.

MySQL does not seem to accept DATE($P{date_as_string}) of any variations of that. I'm having the same problems as loads of others on this site: use JasperServer calendar to select a date and report falls over with SQL error or doesn't find any data due to date format being incorrect in very simple MySQL query. iReports can format a date (even as a string) in a text field but this doesn't work when writing the SQL as there is no access to a "pattern". Have tried the MySQL formatting methods and iReports doesn't seem to like them!!!! Why have the developers made a basic element like date handling so complex that there are hundreds of posts (most without any solutions that work) on this site asking about it?

momzilla you are a star! That's what I wanted and it works fine: can now query as many datbases as required in same report (with subreports) Shame the manual couldn't have quoted you in its examples. Now they need to improve subdataset usage and they'll have a reasonable package. Thanks again

Sorry if post was a bit of a rant. All I want (at the moment) is the connection string to connect a subreport that is different from that of the main report. The documentation states to use param "MyDatasource" but fails to state what the value should actually be. Have tried every thing I can think of from the straight JAVA to using the DSN (alias). Have had to drop using iReports for anything slightly complicated until I can sort this out

Don't think you'll get an answer here mate. Have been trying to find this out for over 2 weeks now and nothing. The iReports documentation isn't any help either. Have tried every formation of connection string and alias I can think of and it will not accept anything. If it showed me the value it is placing in its built in connection parameter/variable that would help. Hope you have better luck than I have.

DO NOT BUY THE DOCUMENTATION - IT'S RUBBISH! have just paid for the iReport documentation and downloaded the PDF, eager to get on and write some reports and the documentation doesn't explain anything useful, the examples are useless (simplistic at best) It's just full of circular references that do not go anywhere useful. You lot should be ashamed to say you are apart of the open source crowd when you are producing software that is so complex that documentation is required to get it to work and then produce a useless manual and charge for it. Not that soory for ranting on but have never come across software like this before that states it can do what I require but with no way of finding out HOW!!!!