2023.2 version stability

If you already done the migration, I don't think you will need to re-do it again just because you update from 2019. I *think* the migration is needed for programs made pre-2019, of course it will still be needed for those programs that you *didn't* migrate.

 vpt.se 

I understand the point of "not doing it again" as I have been just playing with the migration at this point to see how it works. But also understand the issues I've had in the past with "undocumented enhancements" from version to version and feel it best to have the 2023.2 version open that we will be using so I get no surprises when we open programs in 2023.2 if they were migrated to 2020R2.

We (the other programmer here) had a discussion yesterday and came to the agreement that since we will be going to 2023.2 (boss wants to use Nexus as this where it is first applicable) that we will have 2023.2 open when the migration utility is launched. We are going to play with several part families to see how it affects going from XactMeasure to GeoTol and what changes are going to be necessary to get ready for production use.

 vpt.se 

I understand the point of "not doing it again" as I have been just playing with the migration at this point to see how it works. But also understand the issues I've had in the past with "undocumented enhancements" from version to version and feel it best to have the 2023.2 version open that we will be using so I get no surprises when we open programs in 2023.2 if they were migrated to 2020R2.

We (the other programmer here) had a discussion yesterday and came to the agreement that since we will be going to 2023.2 (boss wants to use Nexus as this where it is first applicable) that we will have 2023.2 open when the migration utility is launched. We are going to play with several part families to see how it affects going from XactMeasure to GeoTol and what changes are going to be necessary to get ready for production use.