You have two nearly identical catalogue databases.... based on the AVEVA supplied MAS project one from you one from client with different numbers and hence different unique refs.
You want to bring these two CATA DBs and your DESI's into one DB. If that is correct then there is no problem you can create an MDB with these two sets of unique CATA DBs and DESI together no problem.
I am gathering that you are maybe worried that going forward your users are going to possibly select catalogue references from the client MAS, rather than yours. Resulting in a mess of cross references.
Is this your problem?
If it is you have some options. :)
If you have your own copy of the clients MAS that you will use going forward you need to disable the specs in it so your users can't pick the components from there.... effectively moving the whole client catalogue to limbo spec, and stopping your users selecting it's content.
You have two nearly identical catalogue databases.... based on the AVEVA supplied MAS project one from you one from client with different numbers and hence different unique refs.
You want to bring these two CATA DBs and your DESI's into one DB. If that is correct then there is no problem you can create an MDB with these two sets of unique CATA DBs and DESI together no problem.
I am gathering that you are maybe worried that going forward your users are going to possibly select catalogue references from the client MAS, rather than yours. Resulting in a mess of cross references.
Is this your problem?
If it is you have some options. :)
If you have your own copy of the clients MAS that you will use going forward you need to disable the specs in it so your users can't pick the components from there.... effectively moving the whole client catalogue to limbo spec, and stopping your users selecting it's content.
