|
Bill, We did something similar here. The only difference being that we were dealing with two Synon models that needed to share the "naming files". Synon uses a set of files that drive the naming of different fields and files. We decided to share the "naming files" because there was a plan to copy model objects from one Synon model to another. We created a library called SHARENAME that is shared by the different models. This worked very well for us, even though we did not really do a lot of multi-modeling. Balaji bvenkata@commsoft.net -------------- Original question --------------------------------------------------------- Bill Robins <brobins@ix.netcom.com> on 01/13/99 03:14:16 AM Please respond to MIDRANGE-L@midrange.com To: "BPCS-L@midrange.com" <BPCS-L@midrange.com>, Midrange Discussion List <midrange-l@midrange.com> cc: Subject: Multiple Related Databases > >(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 >shop.) > >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? >Thanks, >Bill +--- | 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.