Generating from CDM to Logical.
PD 9.5.2.889

This is a weird one - 4 tables in my model have more than one foreign key
reference to table COROrg.  By default a foreign ket to COROrg generates as
COROrgKy.  I have renamed the other foreign keys appropriately - e.g.
COROrgKyEmpGrp.  After the rename when I generate from CDM to Logical
everything's fine for all but on of the foreign key columns (i.e. the new
name/code are maintained in all but one).

The list of changes to happen (obtained from Merge dialog -> Merge Preview)
says it's going to
    'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
Looking to see what this modification will involve I see that it's going to
attempt to over-write the code (but not the name) with what's generated from
the CDM (over-write COROrgKyEmpGrp with COROrgKyCOROrgKy2)

The only thing that I can see different about this one is that it's in a
table where there are 3 foreign key references to COROrg (the other 3 tables
only have two foreign key references to COROrg) but maybe it's something
else altogether - any ideas?

It probably doesn't have anything to do with the number 3.
Do you see the column in question in the Merge dialog box?  Is it showing up
as 2 separate lines, by any chance?  That would indicate that PowerDesigner
has somehow lost the link between the CDM relationship and the logical
foreign key column.  In that situation, you have to manually re-link the
columns together using the "Manually Synchronize" button on the toolbar
(just to the left of the "VCR" buttons).

-- 
Mike Nicewarner [TeamSybase]
http://www.datamodel.org
mike@nospam!datamodel.org
Sybase product enhancement requests:
http://www.isug.com/cgi-bin/ISUG2/submit_enhancement

"Thelma Stronge" <thelma.stronge@s1.com> wrote in message
news:3fae9bb9@forums-1-dub...
> Generating from CDM to Logical.
> PD 9.5.2.889
>
> This is a weird one - 4 tables in my model have more than one foreign key
> reference to table COROrg.  By default a foreign ket to COROrg generates
as
> COROrgKy.  I have renamed the other foreign keys appropriately - e.g.
> COROrgKyEmpGrp.  After the rename when I generate from CDM to Logical
> everything's fine for all but on of the foreign key columns (i.e. the new
> name/code are maintained in all but one).
>
> The list of changes to happen (obtained from Merge dialog -> Merge
Preview)
> says it's going to
>     'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
> Looking to see what this modification will involve I see that it's going
to
> attempt to over-write the code (but not the name) with what's generated
from
> the CDM (over-write COROrgKyEmpGrp with COROrgKyCOROrgKy2)
>
> The only thing that I can see different about this one is that it's in a
> table where there are 3 foreign key references to COROrg (the other 3
tables
> only have two foreign key references to COROrg) but maybe it's something
> else altogether - any ideas?
>
>

It is the same one (on same line not 2 separate ones) - i.e. doesn't need to
be Manually Synchronized.

My foreign key column names, reference names and indexes on foreign key
columns had all gotten mixed up in the tables where I'd more than 1
reference to COROrg (probably result of some Manual Synchronization between
some of them!!) so I took note of all the details of the column names,
references & index details & zapped the relationships from CDM/references
from PDMs.  I had this problem with
    'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
before zapping them.

Recreated all using names like "Table 1 ref A", "Table 1 ref B", "Table 2
ref A",  etc. then based on the foreign key being generated for each named
the relationships appropriately.  After all that zapping and startting from
scratch I still had the very same problem with
    'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
though I did suceed in ironing out the other confusions.

I'm confused!


"Mike Nicewarner" <psyclo@nospam_datamodel.org> wrote in message
news:3faeb7f1$1@forums-1-dub...
> It probably doesn't have anything to do with the number 3.
> Do you see the column in question in the Merge dialog box?  Is it showing
up
> as 2 separate lines, by any chance?  That would indicate that
PowerDesigner
> has somehow lost the link between the CDM relationship and the logical
> foreign key column.  In that situation, you have to manually re-link the
> columns together using the "Manually Synchronize" button on the toolbar
> (just to the left of the "VCR" buttons).
>
> -- 
> Mike Nicewarner [TeamSybase]
> http://www.datamodel.org
> mike@nospam!datamodel.org
> Sybase product enhancement requests:
> http://www.isug.com/cgi-bin/ISUG2/submit_enhancement
>
> "Thelma Stronge" <thelma.stronge@s1.com> wrote in message
> news:3fae9bb9@forums-1-dub...
> > Generating from CDM to Logical.
> > PD 9.5.2.889
> >
> > This is a weird one - 4 tables in my model have more than one foreign
key
> > reference to table COROrg.  By default a foreign ket to COROrg generates
> as
> > COROrgKy.  I have renamed the other foreign keys appropriately - e.g.
> > COROrgKyEmpGrp.  After the rename when I generate from CDM to Logical
> > everything's fine for all but on of the foreign key columns (i.e. the
new
> > name/code are maintained in all but one).
> >
> > The list of changes to happen (obtained from Merge dialog -> Merge
> Preview)
> > says it's going to
> >     'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
> > Looking to see what this modification will involve I see that it's going
> to
> > attempt to over-write the code (but not the name) with what's generated
> from
> > the CDM (over-write COROrgKyEmpGrp with COROrgKyCOROrgKy2)
> >
> > The only thing that I can see different about this one is that it's in a
> > table where there are 3 foreign key references to COROrg (the other 3
> tables
> > only have two foreign key references to COROrg) but maybe it's something
> > else altogether - any ideas?
> >
> >
>
>

I can't think of anything that might help you.  Have you found a solution
yet?

-- 
Mike Nicewarner [TeamSybase]
http://www.datamodel.org
mike@nospam!datamodel.org
Sybase product enhancement requests:
http://www.isug.com/cgi-bin/ISUG2/submit_enhancement

"Thelma Stronge" <thelma.stronge@s1.com> wrote in message
news:3fafe9f2@forums-1-dub...
> It is the same one (on same line not 2 separate ones) - i.e. doesn't need
to
> be Manually Synchronized.
>
> My foreign key column names, reference names and indexes on foreign key
> columns had all gotten mixed up in the tables where I'd more than 1
> reference to COROrg (probably result of some Manual Synchronization
between
> some of them!!) so I took note of all the details of the column names,
> references & index details & zapped the relationships from CDM/references
> from PDMs.  I had this problem with
>     'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
> before zapping them.
>
> Recreated all using names like "Table 1 ref A", "Table 1 ref B", "Table 2
> ref A",  etc. then based on the foreign key being generated for each named
> the relationships appropriately.  After all that zapping and startting
from
> scratch I still had the very same problem with
>     'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
> though I did suceed in ironing out the other confusions.
>
> I'm confused!
>
>
> "Mike Nicewarner" <psyclo@nospam_datamodel.org> wrote in message
> news:3faeb7f1$1@forums-1-dub...
> > It probably doesn't have anything to do with the number 3.
> > Do you see the column in question in the Merge dialog box?  Is it
showing
> up
> > as 2 separate lines, by any chance?  That would indicate that
> PowerDesigner
> > has somehow lost the link between the CDM relationship and the logical
> > foreign key column.  In that situation, you have to manually re-link the
> > columns together using the "Manually Synchronize" button on the toolbar
> > (just to the left of the "VCR" buttons).
> >
> > -- 
> > Mike Nicewarner [TeamSybase]
> > http://www.datamodel.org
> > mike@nospam!datamodel.org
> > Sybase product enhancement requests:
> > http://www.isug.com/cgi-bin/ISUG2/submit_enhancement
> >
> > "Thelma Stronge" <thelma.stronge@s1.com> wrote in message
> > news:3fae9bb9@forums-1-dub...
> > > Generating from CDM to Logical.
> > > PD 9.5.2.889
> > >
> > > This is a weird one - 4 tables in my model have more than one foreign
> key
> > > reference to table COROrg.  By default a foreign ket to COROrg
generates
> > as
> > > COROrgKy.  I have renamed the other foreign keys appropriately - e.g.
> > > COROrgKyEmpGrp.  After the rename when I generate from CDM to Logical
> > > everything's fine for all but on of the foreign key columns (i.e. the
> new
> > > name/code are maintained in all but one).
> > >
> > > The list of changes to happen (obtained from Merge dialog -> Merge
> > Preview)
> > > says it's going to
> > >     'Modify Column "COROrgKyEmpGrp" in the Table "CORInteractnPlan"'
> > > Looking to see what this modification will involve I see that it's
going
> > to
> > > attempt to over-write the code (but not the name) with what's
generated
> > from
> > > the CDM (over-write COROrgKyEmpGrp with COROrgKyCOROrgKy2)
> > >
> > > The only thing that I can see different about this one is that it's in
a
> > > table where there are 3 foreign key references to COROrg (the other 3
> > tables
> > > only have two foreign key references to COROrg) but maybe it's
something
> > > else altogether - any ideas?
> > >
> > >
> >
> >
>
>