|
Julie, Your question really depends on what reporting your going to want. If any level of the company is going to need combined reports, you will have to either A) be very good at SQL and Query (it is possible but messy) or B) combine data in to a "merge librarry" where the reporting will be created from. From an AS/400 administration standpoint you will have a little more work with the set up of multiple libraries, but that should be a one time shot, and not much to maintain after. Change control is another point. With multiple libraries, it will be tempting to allow the data base structures to diverge, meaning a change is needed for one branch but not another. Don't let that happen. Change controll software will be very helpfull there. Try to maintain one software library, with all the data libraries identical at the object level and you should be fine either way. Security and recovery/backup might be a bit easier with multiple libraries as well I'm sure quite a few folks will be interested in your decision. For me it's flip a coin. Jim Oberholtzer +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.