Following up the subject of Cadence 16.6 and 17.2

Thank so much everyone.
Just wonder if any of you are using EDAC connector from Perception. Try to get it going on Orcad but no luck so far. I could use some help on that.
TiBo

So what problem are you facing on drawing this connector? Maybe upload the datasheet of the specific one plus what you can't achieve.

Thanks Steve, sorry I did not make it clear, EDAC connector is a third party solfware from Perception that link Orcad capture to Agile.
We use EDAC connector to create all part numbers with all new project and upload all files into Agile control environment.
By the way, we have a solution for this problem now.
Best regards,
TiBo

Hello,

Thank for everybody helps.
Now I get both 16.6 and 17.2 working on my pc.
I find out that both versions are using the same local env file which is pointing to the same location or same libraries.
I have create 2 difference Libraries folder, one for 16.6 and one of 17.2
We will use 16.6 for all ECOs and legacy projects, just want to ensure nothing change except whatever we need to change.
We will use 17.2 for all new projects.
So my question for you. Is there the way that I can call out or point to difference local env files when I switch from 16.6 to 17.2 via versa.
Here are the paths to all libraries in my local env file:

set padpath = L:/Allegro_Lib/PADSTACK_WIP $padpath
set psmpath = L:/Allegro_Lib/SYMBOL L:/Allegro_Lib/SYMBOL_WIP L:/Allegro_Lib/MECHANICAL L:/Allegro_Lib/MECHANICAL_WIP L:/Allegro_Lib/FORMAT L:/Allegro_Lib/FORMAT_WIP L:/Allegro_Lib/SHAPE L:/Allegro_Lib/SHAPE_WIP $psmpath
set textpath = . C:/Cadence/SPB_16.6/share/local/pcb/extracta C:/Cadence/SPB_16.6/share/pcb/text/views C:\pcbenv\text L:\Allegro_Lib\Text

These paths are being use for 16.6 and it seems that 17.2 is using the same one.

Thanks,
Regards,
TiBo

The easiest way is to have 2 pcbenv folders, one for 16.6 and one for 17.2. Maybe name one pcbenv_16.6 and the other pcbenv_17.2. Before you start copy the relevant one to pcbenv and then start Allegro. You may be able to come up with a windows batch file that swaps the pcbenv_16.6 to pcbenv then runs the tools.