I am experiencing an interesting problem that appears to be worse in version 4.5 than in earlier releases of version 4.
I have a set which utilizes the same tables twice. I'll attempt a diagram:
Parent
-Child
-grandchild
=great-grandchild
-great-great-grandchild
-Child (different table as "child" above)
-grandchild1 (same table as "grandchild" above)
=great-grandchild1
-great-great-grandchild1
("-" represents a one-one relationship, "=" represents a one-many relationship)
If the user attempts to access either of the child data tables to change/modify a record, the parent table changes to another record upon data entry in the child, even though the fields being displayed on the form do not necessarily change.
If the great-grandchild and great-great-grandchild data tables are removed from the set, the problem disappears. If one of the sets of links under a child table are removed (duplicate table references), the problem still exists.
In summary, the parent record becomes a moving target and the child data being changed is not linked to the intended parent record. result: very frustrated user.
I have already eliminated index, lookup and posting activities as being connected to this issue. I am using Alpha Five, version 4.5, build 263.
Any ideas? Many thanks,
Rick Hollowell
(This message is was originally mistakenly posted under "Announcements")
I have a set which utilizes the same tables twice. I'll attempt a diagram:
Parent
-Child
-grandchild
=great-grandchild
-great-great-grandchild
-Child (different table as "child" above)
-grandchild1 (same table as "grandchild" above)
=great-grandchild1
-great-great-grandchild1
("-" represents a one-one relationship, "=" represents a one-many relationship)
If the user attempts to access either of the child data tables to change/modify a record, the parent table changes to another record upon data entry in the child, even though the fields being displayed on the form do not necessarily change.
If the great-grandchild and great-great-grandchild data tables are removed from the set, the problem disappears. If one of the sets of links under a child table are removed (duplicate table references), the problem still exists.
In summary, the parent record becomes a moving target and the child data being changed is not linked to the intended parent record. result: very frustrated user.
I have already eliminated index, lookup and posting activities as being connected to this issue. I am using Alpha Five, version 4.5, build 263.
Any ideas? Many thanks,
Rick Hollowell
(This message is was originally mistakenly posted under "Announcements")
Comment