RE: Need 2 cents on multiple libraries

[Jon Erickson <jerickson@xxxxxxx>]

Consider user/reporting access authority between branches.  Users may
require access to multiple branches at once, or even switch between branches
for inquiry/report/maintenance.

I think I'd vote for a branch code field key and one library approach.  You
could either define logicals with select/omit or opnqryf selection criteria
for access methods.

Good luck, let us know which method you choose...

Regards,
Jon A. Erickson
Sr. Programmer Analyst
800.COM Inc.
1516 NW Thurman St
Portland, OR  97209-2517

Direct: 503.944.3613
Fax: 503.944.3690
Web: http://800.com



-----Original Message-----
From: Julie Francis [mailto:jfrancis6222@voyager.net]
Sent: Friday, March 17, 2000 7:29 AM
To: MIDRANGE-L@midrange.com
Subject: Need 2 cents on multiple libraries


Hello All,
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

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