|
Speaking from recent experience, multiple members can be a "hassle" but in our scenario works well. Mark Allen IS Manager Kelly's Kids markallen@kellyskids.com -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Reger, Bill Sent: Friday, March 17, 2000 3:24 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: Need 2 cents on multiple libraries I agree with you David. I never use multiple member files, nor multiple libraries of similar files, for all the reasons you specify and more. I was just confirming that SQL can handle multiple-member files. I certainly wouldn't recommend them as a solution for a new application. William K. Reger Senior Project Manager Levitz Furniture Corporation Phone: (561) 994-5114 E-mail: breger@levitz.com <mailto:breger@levitz.com> -----Original Message----- From: David Morris [mailto:dmorris@plumcreek.com] Sent: Friday, March 17, 2000 3:36 PM To: MIDRANGE-L@midrange.com Subject: RE: Need 2 cents on multiple libraries Bill, You can certainly handle one member at a time using overrides, you can't override to *ALL. Another alternative is to use an SQL ALIAS, same limitation. Multiple libraries/members are not the way to go unless there is some distinct advantage. Library list overflow, unique key problems, SQL limitations, all make it much more difficult to handle multiple libraries. The only advantage I can think of is backup window in multiple time zones. David Morris >>> breger@levitz.com 03/17/00 10:37AM >>> SQL will handle multiple-member files by issuing an OVRDBF before the SQL operation. William K. Reger Senior Project Manager Levitz Furniture Corporation Phone: (561) 994-5114 E-mail: breger@levitz.com <mailto:breger@levitz.com> Multi-member files are a no-no though. SQL (?? someone confirm) can't handle multi-member files. Maybe others, too? +--- | 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 +--- +--- | 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 +--- +--- | 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.