|
Eric DeLong wrote: > > Security wise, the multiple members concept seems more practical > than company key-field. Personally, however, I'd be much more > comfortable with separate libraries & files for each company, which > could be secured as required. Really, though, I all depends on the > situation. > > Eric DeLong > > ______________________________ Reply Separator >_________________________________ > Subject: Re: Optimized Search method for DB files. ? > Author: <MIDRANGE-L@midrange.com > at INET_WACO > Date: 10/22/98 12:29 PM > > Instead of combining data from multiple companies into the same file, > have you considered using multiple members? (ie) A member for each > company. Depending on the company you want to work with, a CL can set up > appropriate overrides. > > Ravi > > Be aware that not all software packages "like" members. If you plan on using non-as400 SQL packages you could run into a problem using members. John Hall Home Sales Co. +--- | 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.