|
At 02:20 PM 12/12/1997 -0500, Buck Calabro wrote: >>There're probably historical reasons for using separate libraries. E.g., I >>think key field handling was not so easy in S/34 or S/36, hence the >>separate files methodology? > >Key handling wasn't the issue for us on our old S/3; it was the pace of >acquisitions. When you have an organisation that has a key like this: >SLSM (2,0) >CUST(5,0) >and you buy another company, you'll be faced with this choice: >a) change umpteen dozen files to have a new key structure, or >b) make a new library to segregate one business from another. > >Mostly, we picked (b) because it goes quickly, and with few >hidden gotcha's. In our case, we control the key, since we're not necessarily dealing with acquisitions so much as selling our services to, say mortgage lenders. So we end up with exactly the same file structure in multiple libraries. It's a little like the library is another key field. In the case you describe, it seems you're keeping the structure of files that the new company already has. In our case, as I say, we are just adding a new 'code'. Cheers Vernon Hamberg Systems Software Programmer Old Republic National Title Insurance Company 400 Second Avenue South Minneapolis, MN 55401-2499 (612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.