Martin Kutschker wrote: > If you want to see your broken SQL statements you can simply turn on the > debugging of t3lib_db (see there). or use that little extension I once wrote... http://www.ingo-renner.com/index.php?id=1&tx_ttnews[tt_news]=89&cHash=df84a1be3e Ingo