By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,761 Members | 1,878 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,761 IT Pros & Developers. It's quick & easy.

branch from the Advantages of a Subform vs. Filtering

zmbd
Expert Mod 5K+
P: 5,397
The question is based on post #3 in the following"
http://bytes.com/topic/access/answer...m-vs-filtering

In the filtred form users simply enter either the inventory id in the textbox or they can select item via the cascading comboboxes. To move to the next desired item the user simply re-selects or re-enters, the form updates once the entries are made. There is logic behind the new record button as a new parent record needs to have the corresponding child record and child records must follow some logic in that it makes no sense to place into service an item that has been marked "out of service" without a prior "repaired" nor if it has been marked as discarded (cradle to grave tracking).

Using the parent/child as shown, to prevent accidental changes to either the parent or child records the controls are locked and the add-new is disabled.

The first challenge is record movement.
In the filtered form... as stated above, finding and moving to the parent record of interest and the subsequent child records is easy.
In the subform... what would be the easiest means of accomplishing the same thing? There are hundreds of parent records; thus, using simple navigation is not the answer. I would assume that one would need to make a query or filter available.

Second challenge: new records in the parent/child need to follow the logic as above. I would surmize using the beforeinsert event to validate the logic would be the best route; however, other ideas?
May 16 '12 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.