Problem with Alter Script generation

[Former Member]

I recently upgraded from Powerdesigner 16.0 to 16.5 and since then the generation of alter scripts for the latest changes to the data model are not running correctly.  A change to a "code" table that is referenced by many other tables fails (MS SQL Server 2008) because of the existence of a Foreign Key reference.  The tool use to generate these scripts correctly, i.e. they dropped all foreign key references and then altered the table and then recreated the foreign keys.  Not sure what has happened after the upgrade.  Does anyone else know what might have changed. 

I hope I have the correct forum, this is my first post under SAP (use to use Sybase often enough but the tool hasn't given me any trouble in a very long time).  I'll probably open a support case Monday, as this issue has only been noticed for the first time this last week but is a serious issue.  Still hoping it might be something simple that others already know.

thanks,

James K.

[arnaud_laurent]

Here is the expected behavior. If the code is a parent table is changed then PowerDesigner 16.5 generates an alter.sql to:

- alter the child table to drop FK constraint

- drop PK constraint of the parent table

- drop then recreate the parent table

- add the FK constraint again to the child table

Make sure you installed PowerDesigner 16.5 GA (build 3982) before applying any PowerDesigner 16.5 ESD.