I've been asked to transfer our reports from a standalone application to one where the _static data_ reports are generated in batch overnight and made available on the intranet the next day. The current application is PowerBuilder that allows the user to save the report output in just about any file format they want (txt, xls, csv, sql, doc...), so that functionality will probably need to remain in the new approach... I'm just brainstorming, but am interested in what approach others may have taken... Did you produce generic files on the server and serve them up as text? What if the users what the ability to bring them into say...Excel. Do you still drop the .txt file on the server and convert it .xls on the way to the client? at the client? Or do you build mutiple file formats of the same report...( can't see this being very efficient, but hey ...that's why I'm asking...) I know we're probably not going to entertain any 3 party applications like Crystal Reports. Our approach is going to center around Perl....and I'm just looking for some big pictures/ideas on how to deliver it... Appreciate any thoughts Mark Sutfin Tech Mgr Application and System Development Affinity Group Inc. (303) 728-7474 _______________________________________________ Perl-Win32-Web mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
