Multiple 1->M Joins Don't Survive Save or Mode Switch

[Miros]

I have the following setup in my data model:

Book (key bookno, field titleno)
linked 1->1 with Title (key titleno) by titleno
linked 1->M with AuthorXTitle (key titleno+authornum, field authorno) by titleno
linked 1->1 with Author (key authorno) by authorno
linked 1->M with IllustratorXTitle (key titleno+bookno+authorno) by titleno and bookno
linked 1->1 with Author (key authorno) by authorno
linked 1->M with Subtitle (key maintitleno+titleno) by book.titleno to subtitle.maintitleno
linked 1->1 with Title (key titleno) by titleno
linked 1->M with AuthorXTitle (key titleno+authornum, field authorno) by titleno
linked 1->1 with Author (key authorno) by authorno
linked 1->M with IllustratorXTitle (key titleno+bookno+authorno) by titleno
linked 1->1 with Author (key authorno) by authorno

The data model makes no complaints. I have even managed to get my form set up to reflect this as follows:
fields from Book and the first instance of Title appear in the body of the form
fields from the first instance of AuthorXTitle and the first instance of Author appear in a table which is located on the body of the form
fields from the first instance of IllustratorXTitle and the second instance of Author appear in a table which is located on the body of the form
fields from Subtitle and the second instance of Title appear in a subrecord field (called Subtitle "panel" after this)
fields from the second instance of AuthorXTitle and the third instance of Author appear in a table located in the Subtitle "panel"
fields from the second instance of IllustratorXTitle and the fourth instance of Author appear in a table located in the Subtitle "panel"

However, when I save my form, close and reopen, only the second instance of IllustratorXTitle retains its link to the correct title... both instances of AuthorXTitle and the first instance of IllustratorXTitle have all their fields "undefined." This also happens if you go back and forth between Design and EditData modes more than once.

Have I simply exceeded Paradox's ability to deal with multiple occurances of a table in the Data Model? I could split the form as follows, but would rather not:

Book (key bookno, field titleno)
linked 1->1 with Title (key titleno) by titleno
linked 1->M with AuthorXTitle (key titleno+authornum, field authorno) by titleno
linked 1->1 with Author (key authorno) by authorno
linked 1->M with IllustratorXTitle (key titleno+bookno+authorno) by titleno and bookno
linked 1->1 with Author (key authorno) by authorno

Book (key bookno, field titleno)
linked 1->1 with Title (key titleno) by titleno
linked 1->M with Subtitle (key maintitleno+titleno) by book.titleno to subtitle.maintitleno
linked 1->1 with Title (key titleno) by titleno
linked 1->M with AuthorXTitle (key titleno+authornum, field authorno) by titleno
linked 1->1 with Author (key authorno) by authorno
linked 1->M with IllustratorXTitle (key titleno+bookno+authorno) by titleno
linked 1->1 with Author (key authorno) by authorno

Thanks in advance,
Rosalie Dieteman
miros1@iwon.com

 

[Miros]

Further info: I'm running a brand new freshly installed copy of Paradox 9.

 

[Miros]

More grist for the mill: it survives the save; it's only when I go from Design mode (where I set up the Table Definitions) to Edit mode and back to Design mode that the table definitions get lost.

Rosalie Dieteman

 

[Miros]

Even more grist...

I recreated the form from scratch with even more tables linked into the data model and it now behaves properly when you switch back and forth from Edit Data to Design modes!

Think it's just an aberation in that one form, or a real problem I should watch for?

Rosalie Dieteman
miros1@iwon.com