# Tip when using Jasper Reports from Oracle Datasets

**URL:** <https://forum.servoy.com/t/tip-when-using-jasper-reports-from-oracle-datasets/16540>\
**Category:** Classic Servoy\
**Created:** [September 24, 2012, 3:40pm UTC](https://forum.servoy.com/t/tip-when-using-jasper-reports-from-oracle-datasets/16540 "2012-09-24T15:40:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jd2p](https://avatars.discourse-cdn.com/v4/letter/j/9d8465/32.png) [@jd2p](https://forum.servoy.com/u/jd2p)\
**Post date:** [September 24, 2012, 3:40pm UTC](https://forum.servoy.com/t/tip-when-using-jasper-reports-from-oracle-datasets/16540/1 "2012-09-24T15:40:41Z")

</div>

Hello everyone,

We spent this last weekend pulling our hair off trying to make Jasper Reports work with Datasets. According to the wiki, there was no need to do anything special to send a Dataset as a parameter as opposed to using a Foundset, so we didn’t now why it always showed null values even though the query did return rows. The same report did work if we loaded that Dataset to a Foundset. Since it did show null values for every row we assumed there was some problem with the versions of the servoy plugin and iReport. So we tried several other versions to no avail.

Finally today, with our nearly hairless heads, we found the problem ![:o]( "Surprised") . When you perform a query to an Oracle database, the column names are returned in Upper Case. However, within the Jasper report the column names were in lower case. So we changed the case for columns and that got it to work ![:D]( "Very Happy") ![:!:]( "Exclamation") So, watch out for this!

Regards,  
jd