Bug in Infopath

[Craig]

I have no idea if this bug has been brought to light before, nor of its
severity, just its existence.

Platform: Infopath 2003 Service Pack 2

Creation Conditions:
- Create a form using a database as a datasource
- Tools -> Data Connections -> Modify

Have a root table set up with 3+ foreign keys. When you go to add/link the
tables via those keys, if you start with the bottom table and move up, the
numbering of the new tables will remain at 1

i.e.

RootTable
PKey
FKey1
AddTbl3 [is named "Subtable_1 (Database.dbo)"]
FKey2
AddTbl2 [is named "Subtable_1 (Database.dbo)"]
FKey3
AddTbl1 [is named "Subtable (Database.dbo)"]

Since FKey1's table was added last, it should have been named "Subtable_2
(Database.dbo)", as happens if you add them in top-down order (FKey1 first,
FKey3 last). I did not test how this affects the references, if it does at
all (lack of time), but thought I would point this out.

Thanks

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...aa0-7a3b53936c32&dg=microsoft.public.infopath

 

[Craig]

For further clarification:

The actual key setup I used that caused the problem was:

MainTable
SubTable1
SubTable4_1
SubTable2
SubTable4_1
SubTable3
SubTable4

Which should have been:

MainTable
SubTable1
SubTable4_2
SubTable2
SubTable4_1
SubTable3
SubTable4

Upon re-adding the keys in a top-down order rather than botom-up I DID get:

MainTable
SubTable1
SubTable4
SubTable2
SubTable4_1
SubTable3
SubTable4_2

Just in case...