M
Michel
Hello
I did a reverse engeneering for both Oracle and MSAcces of a table that have a self referencing foreign key
When I check the resulting model, visio 2000 gives an error L3022 Self-referencing foreign key column 't.b' cannot exist as both a parent and a child in the same relationship
IMHO that error L3022 is a visio 2000 bug
I created a table in access and Oracle and try the reverse engeneering from both with the same problem
create table t
a integer not null
b integer not null
c integer not null
constraint t_pk primary key (a, b)
constraint t_fk1 foreign key (c, b) references t (a, b
)
The c field is a reference to a parent record that have the same b field in the same table
Thank in advance for your comments
Can someone reproduce my test with a more recent version of visio ?
I did a reverse engeneering for both Oracle and MSAcces of a table that have a self referencing foreign key
When I check the resulting model, visio 2000 gives an error L3022 Self-referencing foreign key column 't.b' cannot exist as both a parent and a child in the same relationship
IMHO that error L3022 is a visio 2000 bug
I created a table in access and Oracle and try the reverse engeneering from both with the same problem
create table t
a integer not null
b integer not null
c integer not null
constraint t_pk primary key (a, b)
constraint t_fk1 foreign key (c, b) references t (a, b
)
The c field is a reference to a parent record that have the same b field in the same table
Thank in advance for your comments
Can someone reproduce my test with a more recent version of visio ?