|
Hi Julie, I would strongly recommend the separate library approach. Our system supports multiple companies by way of a "company number" field within the database itself. While this approach worked well in the completely host-centric environment of the past, it has proven to be a significant security problem now that we have ODBC, JDBC, OLD-DB to contend with. Because the package supports up to 99 companies, we would need to build 99 logical files over each and every PF in order to have row-level security. Even if the database supported row level security directly, I would still opt for the separate libraries, because it would require less administration. Regards, John Taylor Canada ----- Original Message ----- From: "Julie Francis" <jfrancis6222@voyager.net> To: <MIDRANGE-L@midrange.com> Sent: Friday, March 17, 2000 08:28 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.