Hi Sven, Thanks for your reaction. I will try to explain why I want to have the iReport compiler do this task for me… I notice that iReport checks the sql when you start building a report. When creating a sql-string in iReport, iReport checks which columns are available for building the report. When you you want to use a field in the report which is not available by sql, and you compile, the compiler raises an error message “field not foundâ€. I like this feature of iReport, because it prevents me to make mistakes. When compiling existing reports iReport doesn’t check anymore if the columns the reports want to use are really available. I can think of 3 reasons why it’s very convenient to have this check when compling with IReport: 1) It prevents me to make mistakes, some changes happens on the database and I'm not aware of all of them; 2) The error is discovered before the report is excecuted in production. I suppose that it’s good to discover errors In early stages, before to go to production; 3) To compile and check (by excecuting) all your reports manually is boring and can use some automation with Ant or Batchcompiler. It will be good if the compiler can do the check if the sql strings are still delivering the field which reports wants to use. Best regards, Jan van Engelen