We are trying to set an installation of Connect Kit and it's
supposed to be put over c4 VRC so a new branch is created
in our derivation tree apart from the one which contains stnd,
mven, mvco, iber ( spanish locations ), even service packs.
Has someone confronted this same problem ? If so, how did
you solved it ? Thanks in advance and read you soon.

Tomas Sanchez Tejero
deckard@encomix.es

Post installation of Baan Connect Kit you have a new VRC branch created from standard VRC.
However to integrate the new VRC into your live package combination, you will need to correct the derivation structure.

If you have a tools validation password you would be able to correct the derivation structure.
In our case, we posted it as a case on support website and it was resolved by a baan specialist dialling in and correcting the derivation structure.

The installation kit for BCK should have the option of selecting the VRC to be used as your parent VRC before installation, which is not present and as a result it is installed as a derivation from the standard Baan IV VRC.
New Derivation structure we have:

B40 c4
B40U c4 stnd -> Update for Standard
B40L c4 bci2
B40U c4 bci2 -> Update for BCK
B40C c4 liv0 -> Live VRC