Any other same-named columns between LineHeader and LineDetail tables
that could be causing inadvertent (non-)linking? Even if they are not
used in the form.
Or between Header and Linedetail?
Doug
On 9/6/2020 6:02 PM, Bruce Chitiea wrote:
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]
<mailto:[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>.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
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/c704baf1-10bf-d317-cf10-d3c9e058c7be%40wi.rr.com.
