Hello All, I've seen numerous postings concerning the various ways to implement reporting and getting around the limitations of the AR ODBC driver. (running Linux over an Oracle db)
We have a healthy amount of reports used on a weekly basis. Some are pulled real time and some are scheduled. I had some concerns out doing the subreporting if these take longer to run than doing join forms. My concern with doing join forms is that as new report requests come in, the design change of creating the join form will need to go through our Development, QA, Production process and could take time. Also, I noticed Ben from Avon said they use the Oracle ODBC driver directly to the database. Are you reporting from within Remedy with the results or are you using a separate reporting area? I'm working on the test case of that scenario to see how it works, but would like some additional information on this option if anyone has one. If anyone found it was better to use a reports server with the data timely copied there please let me know. I'm wondering about performance hitting the production database. Thanks, Amy J. Amy K. Jennings (816) 737-4053 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
