Re: Need 2 cents on multiple libraries

[nina jones <ddi@xxxxxxxxxxxxxxxxx>]

> We are setting up a new work order system for a company with multiple
> branches.  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

there have been a lot of good arguments both ways.  

so flip a coin.  or better yet, evaluate the situation!

advantages of keeping it together is flexibility for the future,
conformity, and ease of getting consolidated data easier if the need
ever arises.  for backup, one library only to mess with.

advantages of separating it are flexibility for the present (that can
turn into future nightmares if you ever need to consolidate) and
separating backups.   

years ago, we did work for a liquor wholesaler, and they took on several
separate ventures.  the data was separated, and they had their own
program libraries, etc.  then we made a major software enhancement, and
all three libraries needed to be changed, etc.  i remember cursing the
programmer (who had left) that made that decision.

nj
+---
| 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
+---