I shudder for the future - "It's really only practical in cases where you have complete control over the database schema..." Sorry, I've seen too many cases where Java developers decided to be their own DBA/Data Architect. It may be perfect for stand-alone, stovepipe, localized reporting where they want it "pretty...pretty" on the web. But they won't leave well enough alone. Shortly (not sooner or later but, rather, sooner), someone will want to do an enterprise-wide app using this. Hopefully the resulting mess will kill this idea dead. -- //www.freelists.org/webpage/oracle-l