|
At 09:28 03/17/2000 , Julie Francis wrote: >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. Given absolutely no interaction between branches and NO consolidation requirements now and forever more amen? Go with multiple libraries. The code will be simpler and backups will be easier with less down time per branch while the system gets to a checkpoint. It will, however make your life a living nightmare if he who gaveth taketh awayeth. Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | 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-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.