Prevent saving to wrong CATIA version

[RogerJames]

Any ideas how I can prevent CATIA from allowing a user to open a R16 file and save as R18? I'd prefer something at file open but would settle from preventing saving.

I already plan to display the version in the title bar, display a msgbox at CATIA startup with the version, and change background color.

Thanks

Roger

 

[Azrael]

How does your enviroment look like? Do you use pdm or is it file based?
A thougt was that you maybe could script to add version as metadata and when called from a pdm refuse a checkout if the version doesn't comply maybe with P&O.
If you have file based then maybe you can set different write permissions on the folder depending on the user logged in, using two different user account for the different versions

Doing it inside CATIA I don't have any ideas, can't see how to prevent a save due to a criteria is not met. Maybe somebody else has an idea on this.

 

[DBezaire]

Roger,
If you lock users with catia admin settings from a server, you can use DLNAMES. As each job is kicked off you will add the DLNAME structure of where people can load/save from. You will create a new set of admin settings for each version of Catia. As a new job is kicked off in the next version, DLNAME structure is created in next version admin settings. This will enforce company standards for how and where documents are saved.

Regards,
Derek