• Subject: Multiple Related Databases
  • From: Bill Robins <brobins@xxxxxxxxxxxxx>
  • Date: Wed, 13 Jan 1999 08:14:16 +0000

(I am sending this message to both the BPCS list and the Midrange list, because
it may be applicable to other situations others have experienced in a non-BPCS

We recently acquired another company, which we want to convert their system to
BPCS 4.0.5CD.  My plan is to start them out with their own database, but in the
future their data would be merged with ours into a single database.

My question is this: Since the plan is to merge the data at some point in the
future, setting up the data so that it will not conflict when merged would be
desirable.  There are customers and vendors that both company's share for
example, that if they had different numbers while in separate databases would
need to be converted so the data could be joined when the data merges.  One idea
floating around my head would be to put a common library above the library list
of each database that would contain certain files that would be shared between
the two.

Example:  Instead of RCMxxx sitting in BPCSFC1 -and- in BPCSFC2, it would sit in
BPCSFCX that is higher in the library list than C1 and C2.  It would not exist
in either C1 or C2, but only in CX.

Anyone tried this?  Does it sound feasible?  Should I see a Psychiatrist?


| 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 thread ...

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

This mailing list archive is Copyright 1997-2019 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].