R
Robert Nusz @ DPS
I have an MsAccess application that has two tables: Case_Record_A table and
Case_Record_B table. Both tables are DB2 Mainframe tables linked to desktop
MsAccess 2003 Professional Application. The two tables are linked together
on keyed fields of CASE_YR and CASE_NUM as matching Master & Child Links.
I have one form, FR_CR_E that is used to enter new records to both tables at
the same time, thus creating one record for CASE_RECORD_A as master and a
possiblity of multipe CASE_RECORD_B table records, (theres also the
possibility of NO Matching CASE_RECORD_B table records). This form FR_CR_E
is a multitab form, with four panels. The first three tabbed panels reflect
data entry capacity to CASE_RECORD_A table. After various dataentry edits
passing OK, the record is written as user passes control to the 4th panel to
create records to CASE_RECORD_B table. Form panel 4 accepts CASE_YR field
and CASE_NUM from previous panels and then adds SEQ_NO field as part of key
for indexing purposes. There is a dependency that CASE_RECORD_A must have
been written/finalized before any CASE_RECORD_B records can be added to
separate table.
All works well as you ADD A RECORD to CASE_RECORD_A table and then SAVE the
record to CASE_RECORD_A prior to tabbing into 4th panel for to add additional
records to CASE_RECORD_B table. This fourth panel contains a "SUB-FORM" in
detail. It accepts CASE_YR and CASE_NUM from previous panels and pre-files
same required like-named fields for CASE_RECORD_B, thus turning on the
updated form status. If you add records to table B, all works well, seq_no
gets updated properly, records entered properly, but, when you get ready to
return to tabbed panel 1, to create another RECORD_A, the system fails as it
attemps to write a Null record to RECORD_B whis would be invalid. If you
exit the last Panel 4, after writing records to RECORD_B table, with a
complete RETURN or exit of primary form, all works well, no null records
written to CASE_RECORD_B file, and application can close normally. BUT, if
you exit panel 4 after writting CASE_RECORD_B table records (any) by clicking
on one of the previous TABS on the tabbed form, (thus exiting control to
Table B), the application dies after attempting to write null record to table
B.
I want to utilize this tabbed panel form for data-entry as if flows smoothly
between multiple data entry forms of data and writes correct record A, allows
user to add multiple record B's, but dies if any records written, and then
return to any segment of panel 1,2,3.
What condition or switch do I need to check, verify, Undo, etc to clear this
issue.
Thanks in advance.
Case_Record_B table. Both tables are DB2 Mainframe tables linked to desktop
MsAccess 2003 Professional Application. The two tables are linked together
on keyed fields of CASE_YR and CASE_NUM as matching Master & Child Links.
I have one form, FR_CR_E that is used to enter new records to both tables at
the same time, thus creating one record for CASE_RECORD_A as master and a
possiblity of multipe CASE_RECORD_B table records, (theres also the
possibility of NO Matching CASE_RECORD_B table records). This form FR_CR_E
is a multitab form, with four panels. The first three tabbed panels reflect
data entry capacity to CASE_RECORD_A table. After various dataentry edits
passing OK, the record is written as user passes control to the 4th panel to
create records to CASE_RECORD_B table. Form panel 4 accepts CASE_YR field
and CASE_NUM from previous panels and then adds SEQ_NO field as part of key
for indexing purposes. There is a dependency that CASE_RECORD_A must have
been written/finalized before any CASE_RECORD_B records can be added to
separate table.
All works well as you ADD A RECORD to CASE_RECORD_A table and then SAVE the
record to CASE_RECORD_A prior to tabbing into 4th panel for to add additional
records to CASE_RECORD_B table. This fourth panel contains a "SUB-FORM" in
detail. It accepts CASE_YR and CASE_NUM from previous panels and pre-files
same required like-named fields for CASE_RECORD_B, thus turning on the
updated form status. If you add records to table B, all works well, seq_no
gets updated properly, records entered properly, but, when you get ready to
return to tabbed panel 1, to create another RECORD_A, the system fails as it
attemps to write a Null record to RECORD_B whis would be invalid. If you
exit the last Panel 4, after writing records to RECORD_B table, with a
complete RETURN or exit of primary form, all works well, no null records
written to CASE_RECORD_B file, and application can close normally. BUT, if
you exit panel 4 after writting CASE_RECORD_B table records (any) by clicking
on one of the previous TABS on the tabbed form, (thus exiting control to
Table B), the application dies after attempting to write null record to table
B.
I want to utilize this tabbed panel form for data-entry as if flows smoothly
between multiple data entry forms of data and writes correct record A, allows
user to add multiple record B's, but dies if any records written, and then
return to any segment of panel 1,2,3.
What condition or switch do I need to check, verify, Undo, etc to clear this
issue.
Thanks in advance.