Generation SS 2000 Missing Foreign Keys

[Jeff Odell]

I'm generating a 15 or so table database from EA.  I have all the Foreign Keys specified using the Foreign Key dialog.  I'm doing a package-wide generation into a single file.  I have the Create Foreign Keys checkbox checked.  I also have Create Drop DDL checked.

Once the file is generated, I have all my DROP CONSTRAINT statements for the Foreign Keys at the top of the file as expected.  However, at the end of the file are only 5 of my CREATE CONSTRAINT statements for the Foriegn Key constraints.  There are several missing.

It almost seems like the generation quits prematurely or something.

Any ideas?  Thanks - Jeff Odell

Returning to my model I cannot see any difference between the ones that are showing up and the ones that are not.

[Jeff Odell]

For anyone else suffering with this problem, build 4.1.734 does NOT exhibit this problem on the exact same model.  4.1.736 does have the problem.  This will provide you with a workaround until the problem is resolved.

Jeff Odell

[jfortuny]

I have the same problem, In one package I have  several diagrams to show different aspects of the application.

I have noticed that when I have one of the diagrams open at the moment of the generation of the SQL file it includes the Foreign Key references of that diagram. But not from the rest of the diagrams. On the same manner if no diagram is open, no Foreign Keys are created.

[Ignacio]

Hi,

I had updated from 730 to 737 because, it was nothig to do about creating Foreign Keys when I tried to generate the DDL for an Oracle table.

I still no having the posibility to do it.

Does anyone know how to solve it?

Thanks in advance.
Ignacio Soler

I have the same problem, In one package I have  several diagrams to show different aspects of the application.

I have noticed that when I have one of the diagrams open at the moment of the generation of the SQL file it includes the Foreign Key references of that diagram. But not from the rest of the diagrams. On the same manner if no diagram is open, no Foreign Keys are created.

[Jeff Odell]

The problem in SQL Server 2000 cleared itself up with build 737.  There was no mention in the release notes, but the developer that had followed up on my bug report told me it was fixed.

[hd]

Yes - this bug was fixed for build 737 (missed the release notes  ).

The problem was that when generating package level DDL, EA was only generating foreign keys for open diagrams. It now generates FKs for all tables in that package.