Awesome!
Karen
-----Original Message-----
From: Bruce Chitiea <rby...@safesectors.com>
To: rbase-l@googlegroups.com <rbase-l@googlegroups.com>
Sent: Mon, Sep 7, 2020 9:45 am
Subject: Re[2]: [RBASE-L] - Forms: Relational Fail | Fix
#yiv2388235119 #yiv2388235119xdd5ae517410248c
#yiv2388235119xce0a6bc6429748f68a1fbd60505e23fd, #yiv2388235119
#yiv2388235119xdd5ae517410248c #yiv2388235119xce0a6bc6429748f68a1fbd60505e23fd
#yiv2388235119x0ffa9ca747a0444 #yiv2388235119x5341b55c703f4d708da1fcccafdd6cf1,
#yiv2388235119 #yiv2388235119xdd5ae517410248c
#yiv2388235119x86b4dd35dfc94ef5a5432fdb70f5f643{font-size:12pt;}#yiv2388235119
#yiv2388235119 #yiv2388235119 #yiv2388235119 --blockquote.yiv2388235119cite
{margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px
solid #cccccc;}#yiv2388235119 blockquote.yiv2388235119cite2
{margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px
solid #cccccc;margin-top:3px;padding-top:0px;}#yiv2388235119 a img
{border:0px;}#yiv2388235119 #yiv2388235119 #yiv2388235119 #yiv2388235119 ,
#yiv2388235119 #yiv2388235119 #yiv2388235119 #yiv2388235119 , #yiv2388235119
#yiv2388235119 #yiv2388235119 #yiv2388235119 , #yiv2388235119 #yiv2388235119
#yiv2388235119 #yiv2388235119 {list-style-position:inside;}#yiv2388235119 body
{font-family:Segoe UI;font-size:12pt;}#yiv2388235119 .yiv2388235119quote
{margin-left:1em;margin-right:1em;border-left:5px #ebebeb
solid;padding-left:0.3em;}#yiv2388235119 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. ChitieaSafeSectors, Inc.-----------------------------------112 Harvard
Ave #272Claremont CA
91711-4716-----------------------------------rby...@safesectors.com-----------------------------------+011
(909) 238-9012 c+011 (909) 912-8678 f
------ Original Message ------From: "'Karen Tellef' via RBASE-L"
<rbase-l@googlegroups.com>To: "rbase-l@googlegroups.com"
<rbase-l@googlegroups.com>Sent: 9/7/2020 6:26:35 AMSubject: 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 <rby...@safesectors.com>
To: rbase-l@googlegroups.com <rbase-l@googlegroups.com>
Sent: Sun, Sep 6, 2020 6:02 pm
Subject: [RBASE-L] - Forms: Relational Fail
#yiv2388235119 #yiv2388235119 --#yiv2388235119x6a6fba8347e24e1
#yiv2388235119x60e28c9091074ff #yiv2388235119xce0a6bc6429748f68a1fbd60505e23fd,
#yiv2388235119 #yiv2388235119x6a6fba8347e24e1 #yiv2388235119x60e28c9091074ff
#yiv2388235119xce0a6bc6429748f68a1fbd60505e23fd #yiv2388235119x0ffa9ca747a0444
#yiv2388235119x5341b55c703f4d708da1fcccafdd6cf1, #yiv2388235119
#yiv2388235119x6a6fba8347e24e1 #yiv2388235119x60e28c9091074ff
#yiv2388235119x86b4dd35dfc94ef5a5432fdb70f5f643{font-size:12pt;}#yiv2388235119
#yiv2388235119x6a6fba8347e24e1
blockquote.yiv2388235119cite{margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px
solid rgb(204, 204, 204);}#yiv2388235119 #yiv2388235119x6a6fba8347e24e1
blockquote.yiv2388235119cite2{margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px
solid rgb(204, 204, 204);margin-top:3px;padding-top:0px;}#yiv2388235119
#yiv2388235119x6a6fba8347e24e1 a img{border:0px;}#yiv2388235119 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. ChitieaSafeSectors, Inc.-----------------------------------112 Harvard
Ave #272Claremont CA
91711-4716-----------------------------------rby...@safesectors.com-----------------------------------+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 rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/em5d0cc3c6-2d6f-4e6b-b46a-5f1a2d55a216%40pathfinder.
--
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 rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/46816626.1067437.1599485195630%40mail.yahoo.com.
--
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 rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/em300f2a88-db4d-49a6-8da8-a33250c6f158%40pathfinder.
--
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 rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/1348168437.1122076.1599494339995%40mail.yahoo.com.
