Karen: Nope. Had not tried "many to many" prior. But when I do,
perfection:
Quoting Karen T.: "If I am correct, "one to many" means that LineDetail
has to link to the Header table directly, which I assume it does not. It
links thru LineHeader, so there you need the "many"
The interface itself:
I'll admit to not meditating on the precise language of that second
option. When I do, I see the same logic behind Sub Reports ... every Sub
Report table must have SOME link back to the driving table. To be
fair, the R:BASE Forms documentation does read "With more than two
tables assigned to the form, this option is the appropriate setting."
Nevertheless, the "and also" throws me off. A more precise instruction
might read:
"Many to many (every Slave is either (a) directly linked to the Main, or
(b) via link(s) across one or more Slaves to the Main)"
Back up and running! Many thanks!
Bruce A. Chitiea
SafeSectors, Inc.
-----------------------------------
112 Harvard Ave #272
Claremont CA 91711-4716
-----------------------------------
[email protected]
-----------------------------------
+011 (909) 238-9012 c
+011 (909) 912-8678 f
------ Original Message ------
From: "'Karen Tellef' via RBASE-L" <[email protected]>
To: "[email protected]" <[email protected]>
Sent: 9/7/2020 6:26:35 AM
Subject: Re: [RBASE-L] - Forms: Relational Fail
Have you selected "many to many" rather than "one to many"? I find
that when I have >1 table on a form, I need the "many to many"
If I am correct, "one to many" means that LineDetail has to link to the
Header table directly, which I assume it does not. It links thru
LineHeader, so there you need the "many"
Karen
-----Original Message-----
From: Bruce Chitiea <[email protected]>
To: [email protected] <[email protected]>
Sent: Sun, Sep 6, 2020 6:02 pm
Subject: [RBASE-L] - Forms: Relational Fail
All:
The issue:
(1) In Edit Mode. As one scrolls through the values in the Header
table, related values in the LineHeader table step right along, linked
by the HeaderID FK value. Perfect.
(2) The LineDetail table sits inert, as if completely dissociated from
the LineHeader table, even though it contains FK LineHeaderID.
(3) The LineDetail table may be scrolled independently of Header and
LineHeader, scrolling neither.
The Form's Table configuration:
(A) The Form is Bound to the Header table
(B) LineHeader is slaved (one to many) to Header via FK HeaderID
(C) LineDetail is slaved (one to many) to LineHeader via FK
LineHeaderID
(D) It does not seem to matter whether the tables are linked via Common
Columns, PK/FK or drag/drop.
What have we checked?
(a) All three tables have PK and FK keys properly defined, double,
triple checked.
(b) Data from all three tables have been linked, apart from this form,
in Views used to produce Reports with gnarly Sub Reports, within a
daily production context.
(c) There are no "orphaned" rows from any table in the dataset used in
the Form. Each LineDetail row links to a LineHeader row, which links to
a Header row.
(d) All column definitions in all tables have been closely scrutinized
to ensure conformance
(e) All tables have been UNLOAD/RELOADed into a spankin' new database
to eliminate any random, unruly influences.
(f) The above test Form was created to strip away any and all other
Forms considerations.
Any and all thoughts and experience most welcome. Stay cool in the
heat,
Bruce A. Chitiea
SafeSectors, Inc.
-----------------------------------
112 Harvard Ave #272
Claremont CA 91711-4716
-----------------------------------
[email protected]
-----------------------------------
+011 (909) 238-9012 c
+011 (909) 912-8678 f
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/em5d0cc3c6-2d6f-4e6b-b46a-5f1a2d55a216%40pathfinder
<https://groups.google.com/d/msgid/rbase-l/em5d0cc3c6-2d6f-4e6b-b46a-5f1a2d55a216%40pathfinder?utm_medium=email&utm_source=footer>.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/46816626.1067437.1599485195630%40mail.yahoo.com
<https://groups.google.com/d/msgid/rbase-l/46816626.1067437.1599485195630%40mail.yahoo.com?utm_medium=email&utm_source=footer>.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/em300f2a88-db4d-49a6-8da8-a33250c6f158%40pathfinder.
