You do not have to start from scratch, use your code base, cut and paste into
a new project. Then place modules used in old project into new project, and
take settings from originating Designer for each module and set up new project
modules with those settings.
Then compile and debug one functional area at a time. Should not be mount Everest
to climb, just a methodical determined approach.
Also if you run into a problem, post your new project and forum will try to help you.
Apologies, completely missed the point its a legacy part. But part is
still in Designer catalog, so possible to move to new project, but
there may be issues with individual modules not operating same
as in Designer 3.2. But thats a debug process that should be able
You have a bit of a delemma, each revision of Designer fixed problems
in prior revison, as well as enhance. But legacy parts in future releases
I would posit are not retested, so there is risk by staying with old Designer,
and same for going to new Designer in order to use the legacy parts.
You could consider using services of CyPro to do the migration to a new
part if turn around is your primary consideration.
Or just try to debug old designer with Designer 3.2 and your old tools.
One last idea, you could file a CASE and get Cypress opinion on best
approach, point the case to this thread, and give Cypress your drop
dead constraints. Maybe ask them to talk to 233 designer to see if using
newer Designer may have any hidden issues.
“Create a MyCase”