[RESOLVED] Bound/Unbound... Subform... Write Conflict... Conceptual Help
I'm unsure whether this belongs in this Forms thread or in Theory & Practice. Based on the nature of the discussion I chose here.
I write to start a discussion for conceptual help. After returning to Access after many years I am finding that I am relearning most of what I knew. The first form that I most recently designed I ended up writing twice. I chose a standard bound form from the builder that had a lower subform attached. It was only in the final testing phase that I encountered a write conflict which sent me back to the drawing board and I successfully redesigned using a completely unbound form. Yet for that solution and to avoid the write conflict I did forego the lower datasheet view. Therein lies my discussion.
For my next form I would like to again employ a data entry form but this time I would also like to include the use of a subform to view multiple records. My question is how. Do I design an unbound form on the top and a locked and bound subform? Can this subform appear to be paging through records even though it is locked? And what about that dreaded write conflict error when the unbound form programmically updates the record that appears chosen in the lower subform? Am I thinking in the right direction or is there an easier or more elegant solution that will avoid the write conflict using bound forms?
I'm usually good at muddling through and figuring this stuff out. Yet before I proceed I'm sure that receiving some insight as to a direction to follow would indeed be helpful so that writing the same project multiple times can be alleviated. Thank you.
I'm unsure whether this belongs in this Forms thread or in Theory & Practice. Based on the nature of the discussion I chose here.
I write to start a discussion for conceptual help. After returning to Access after many years I am finding that I am relearning most of what I knew. The first form that I most recently designed I ended up writing twice. I chose a standard bound form from the builder that had a lower subform attached. It was only in the final testing phase that I encountered a write conflict which sent me back to the drawing board and I successfully redesigned using a completely unbound form. Yet for that solution and to avoid the write conflict I did forego the lower datasheet view. Therein lies my discussion.
For my next form I would like to again employ a data entry form but this time I would also like to include the use of a subform to view multiple records. My question is how. Do I design an unbound form on the top and a locked and bound subform? Can this subform appear to be paging through records even though it is locked? And what about that dreaded write conflict error when the unbound form programmically updates the record that appears chosen in the lower subform? Am I thinking in the right direction or is there an easier or more elegant solution that will avoid the write conflict using bound forms?
I'm usually good at muddling through and figuring this stuff out. Yet before I proceed I'm sure that receiving some insight as to a direction to follow would indeed be helpful so that writing the same project multiple times can be alleviated. Thank you.
Last edited: