|
"Cassidy, Alan" <CassidyA@xxxxxxxxxx> wrote in message news:mailman.178.1168294990.12056.midrange-l@xxxxxxxxxxxxxxx
==>IMHO it's a useful feature and a handy solution to lots of situations, like apparently Mikes', but new users should >proceed with caution. IMHO multiple members should remain "lightly used" because they can complicate your life really quick, especially if you >start defining LF members based on this and that list of PF members, and so on. And using SQL to get to data in multiple->member files is kind of a kludge sometimes..
Agreed and understood. We probably only have this one instance where this is a marvelous solution to our problem. At the moment, I can't think of another area where we could leverage it but there may be. The lion's share of *FILE objects that we create and process will be single-member.
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.
midrange.com
