× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Multiple Related Databases
  • From: "Ashok Singh" <asingh@xxxxxxxx>
  • Date: Thu, 14 Jan 1999 07:43:41 -0600
  • Importance: Normal

Yes I have tried something similar but not with RCM and it will cork
correctly as long you make sure all your file pointers are correct, with fle
pointers I mean All the Join logical files should also point to RCM in this
library. And to achieve that you will have to recreated all the join logical
files. And logical files as well.

Ashok
Prosoft

-----Original Message-----
From:   owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com] On Behalf
Of Mindaugas Bielskus
Sent:   Wednesday, January 13, 1999 9:08 PM
To:     BPCS-L@midrange.com
Subject:        Re: Multiple Related Databases

Bill Robins wrote:
>
> (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 BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---


Bill:

I don't have any advise on how to optimally configure BPCS for your
situation, but if you are interested in an easy way to map your new
company's data into BPCS, I could steer you to a product that we sell.
The product is the Intelligent Data Conversion System.  Its an AS/400
based product that has been used in many BPCS implementations.  Please
email me if you are interested.

Mindaugas Bielskus
Data Summary, Inc.
708-795-0606
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.