are you saying that I need to have subforms when doing a one to many
That is typical, but not a hard rule. If your design dictated a continuous or datasheet form view and you were wanting repeating records, you wouldn't need a subform. I doubt that is the usual approach for anyone, though.
The intention of my first post wasn't to beak off or hijack the path of a solution, so hopefully no one bows out because of it. If you go back to that post, you'll see that I'm saying if you cannot edit, delete or append the query, don't bother looking at the form properties as the initial problem. To repeat, the problem is usually the type of query involved, or the design of the query, or referential integrity (e.g. you can't append child fields when there is no parent record). I suppose there could be other reasons, but those are the ones that come to mind. So if you created a query that retrieved your data but you didn't try to edit/append to it, you missed a step. If you did that, you need to ensure you fully test the parent/child relationships.



Don't let my misunderstanding of the posted statement lead you off track. It sounds like you need a main form with 2 sub forms, which has already been suggested, and as far as I can tell, jwhite's posts contain your solution. You can always post a zipped db copy for help, but I probably can't deal with your version.