lucianc Wrote: That just might be the cause of the bug. The built-in query executers are internally registered via a property file located inside the JR jar, namely jasperreports_extension.properties. If JR fails to find that resource in the Sybase environment, the query executers (incl. the SQL one) will not be available. Is this a documented Sybase JRE limitation? I haven't found anyting about problems with propreties files on installing jars to sybase enviroment, but I think that may be it. I've notticed warnings from log4j that appear when there's no properties, and there is one in my jar and it is used when I run my jar in eclipse or in console. That's why I think it was ignored, and so are probobly JR properties. Anyway I've managed to load my classes to sybase's classpath and I can use them now without installing them to the enviroment and everything works fine :) well maybe except report viewer which crashes my db after closingh it :) but that's prblem with sybase and JVM I think. Thanks for your time. PiotrN