Jump to content
We've recently updated our Privacy Statement, available here ×

ict.projects

Members
  • Posts

    6
  • Joined

  • Last visited

ict.projects's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. I have an simmilar problem. I would like to send leave reports to every employer autmaticaly. At the moment I have a report where on every page a employers leave records are listed. Ideal would be to send to every employer just his own page. Is that possible?
  2. Hi Paul, your posts about this problem was years ago, but I have the same problem. Did you found a solution in 2009?
  3. I have to create Reports with data from a remote MySQL database. This one is configured with Latin1 Character encoding: mysql> SHOW VARIABLES LIKE 'c%'; +--------------------------+----------------------------+ | Variable_name | Value | +--------------------------+----------------------------+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_results | latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | | collation_connection | latin1_swedish_ci | | collation_database | latin1_swedish_ci | | collation_server | latin1_swedish_ci | | concurrent_insert | ON | | connect_timeout | 5 | +--------------------------+----------------------------+ When I run a SELECT from the mysql command prompt it gives me the correct special caracters. E.g. äöü But If I try to create a Report with this Datasource instead strange characters apear: "ä" etc. I already tried to change the JDBC configuration in the datasource: 'characterEncoding=latin1&characterSetResults=ISO8859_1' but no luck. The problem is the same with iReport 5.0 and Jasperserver 5.0 Anyone an idea how I can make Jasperserver interpret the data correctly from a latin1 datasource?
  4. The only way I know is to use a subreport instead of a dataset. A subreport can have "ReturnValues", so it can comunicate with the main report.
×
×
  • Create New...