Ceejay64
Bass Playin' Biker Chick
- Local time
- Today, 12:02
- Joined
- Oct 2, 2002
- Messages
- 74
Ahhh, yet another problem.
I have a form with 2 subforms. They are both linked by ID - an autonumber key field. The top subform, "processing," works just fine. As I navigate through the records, the processing form reacts just fine. It is the second subform, "reprocessing," that is the problem.
Now, each record always has to utilize processing, but reprocessing is an "if necessary" item that will likely not be used most of the time. Due to the fact that each of these subforms has a ton of fields on it, each feeds a separate table.
My problem is this: despite the fact that all tables are linked via the ID key, and each subform is supposed to load with the ID in common, when I navigate through the records, the reprocessing subform fails miserably. Instead of recognizing a matching ID, some of which should be blank if the record in question has no reprocessing, it navigates through its own table, screwing up my records and failing to properly record items or show the correct reprocessing information. It's tied right to its reprocessing table, not a query...or should it be a query instead??
What gives?? I'm hoping it's just a simple coding issue, but I have to get this fixed ASAP since it's business related and under the scrutiny of the FAA for our records!!
HELP!!
I have a form with 2 subforms. They are both linked by ID - an autonumber key field. The top subform, "processing," works just fine. As I navigate through the records, the processing form reacts just fine. It is the second subform, "reprocessing," that is the problem.
Now, each record always has to utilize processing, but reprocessing is an "if necessary" item that will likely not be used most of the time. Due to the fact that each of these subforms has a ton of fields on it, each feeds a separate table.
My problem is this: despite the fact that all tables are linked via the ID key, and each subform is supposed to load with the ID in common, when I navigate through the records, the reprocessing subform fails miserably. Instead of recognizing a matching ID, some of which should be blank if the record in question has no reprocessing, it navigates through its own table, screwing up my records and failing to properly record items or show the correct reprocessing information. It's tied right to its reprocessing table, not a query...or should it be a query instead??
What gives?? I'm hoping it's just a simple coding issue, but I have to get this fixed ASAP since it's business related and under the scrutiny of the FAA for our records!!
HELP!!
