One follow-up thought that I neglected to mention before: Business Objects definitely does metadata better. If you're looking for embed a lot of metadata about heirarchies, related tables, source information, etc., then BO will support that better. Brio is okay, but it's not really robust in that area.
So if you want to make a case for BO over Brio, you might want to start pushing the importance of good metadata, and start entering a lot of it into your database. With that as a opening ante, you might be able to sway the decision a bit. thanks, bruce -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bruce A. Bergman INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).