× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Need 2 cents on multiple libraries
  • From: Vance Stanley <w_vance_stanley@xxxxxxxxx>
  • Date: Fri, 17 Mar 2000 10:16:13 -0800 (PST)

You can override to a file member then sql it....

--- "Bale, Dan" <DBale@TFSA.Textron.com> wrote:
> >In your shoes, I would add "yet" to "no shared
> information between the
> branches".<
> My thoughts exactly.  Seen it too many times.
> 
> Multi-member files are a no-no though.  SQL (??
> someone confirm) can't
> handle multi-member files.  Maybe others, too?
> 
> Use the branch code field.
> 
> That's my vote.  But John Taylor made some good
> points to that need
> consideration.
> 
> - Dan Bale
> 
> -----Original Message-----
> From: Fisher, Don [mailto:DRF@HeiligMeyers.com]
> Sent: Friday, March 17, 2000 11:11 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: Need 2 cents on multiple libraries
> 
> 
> In your shoes, I would add "yet" to "no shared
> information between the
> branches".  That said, I would definitely not
> recommend the multiple library
> approach.  In my opinion, it would be unncecessarily
> cumbersome and make it
> difficult to add branches later.  One library
> containing files with a member
> for each branch would be more practical, I think.
> 
> Having said that, files with multiple members make
> consolidated reporting
> rather difficult.  I personally believe there is no
> substitute for using
> primary keys, like a branch number, for tracking and
> extracting information.
> 
> As always, just my opinion.
> 
> Donald R. Fisher, III
> Project Manager
> Heilig-Meyers Furniture Company
> (804) 784-7500 ext. 2124
> Don.Fisher@HeiligMeyers.com
> 
> <clip>
>  We are debating between using one database library
> per branch
> vs. a branch code field key and one library.  These
> files will be large
> and in use 24 hours per day and there will be no
> shared information
> between the branches.  May I have your comments on
> your experience with
> using either/or.  TIA   Julie
> +---
> | 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
> +---
> 

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.