- I just left it the way it was when I created the subform from that table. I removed the Control Source field, and the field just reads as Unbound. Unfortunately then as I viewed each form they all had "1" as their MainRecipeReferenceID.
1. When I have all my information in I just want it to look neat and complete, not like it is waiting for extra information. I don't find in Datasheet View (like Excel), but would prefer the form to be cleaner.
2. Is there a way to set up a filter for 1 combo box once a selection has been chosen from the previous, from the information in the tables and not that in the form. As I have all my categories and their folders listed in their tables but have not input recipes for them all yet. I think my joins and subforms makes this more complicated.
3. I would just like to confirm that you would generally do my form off a query with the 2 subforms? (for continuous entry)
4. Also you would do the bulk of your data entry through forms, right?
1. MS Access is a relational database management system, not a spreadsheet; you can't expect them to behave in the same way. If you hide the empty row by setting the AllowAdditions property to False, you will then have to include a way for the user to reset it to True when they want to insert a new row into the subform, and then back to False after the new row has been inserted. For this you'll need to write the VBA code. However I'd still question the need to do this. The cleanness of presentation which you are aiming at is more a matter for a report than the forms interface. In due course I would envisage your primary medium for the presentation of the recipes being reports rather than forms. Reports allow you vastly greater flexibility in the control of the layout than a form allows.
2. You can only correlate combo boxes in a form. It is done by referencing the first combo box as a parameter in the RowSource of the second, and requerying the second in the AfterUpdate event procedure of the first.
3. Whether the parent form or the first subform is based on a table or query is not relevant to this issue, but forms are almost invariably based on a query rather than a table, if only to return the rows in a desired order. The key thing here is that the second subform is based on a query which correlates it with the first by referencing the key of the first as a parameter. The underlying mechanism is exactly the same as that for correlation combo boxes described in the preceding paragraph, but at subform level rather than control level. Note that none of the queries need to be saved as querydef objects, the RowSource property can simply be the SQL statement of the query.
4. Not the bulk of it, ALL of it. Never enter data directly via a table's datasheet.