Using a continuous form to set up link rows

[Mark]

Hi All

I'm coming back to access after a very long break developing in VS.net and
am having a bit of trouble adjusting. I'm writing a front end on an access
2003 database, and have the following scenario I could do with some help on:

I have a master list of products, and also a master list of 'selection
sets'. What I need to do is put a front end on the link table that is used to
specify which products are in which sets (an N-N relationship). I've set up a
continuous form containing the products, with an include checkbox against
each item (the form at this point knows which selection set it is dealing
with). The only problem being that, as I've used a function to specify the
initial value of the checkbox it has set the form as read-only, which put a
hitch in my plan of handling the OnDirty event and using SQL in there to
add/delete the link record as neede).

If anyone could give me some pointers I'd me most appreciative

Thanks in advance for your help

Mark

 

[Marshall Barton]

I'm coming back to access after a very long break developing in VS.net and
am having a bit of trouble adjusting. I'm writing a front end on an access
2003 database, and have the following scenario I could do with some help on:

I have a master list of products, and also a master list of 'selection
sets'. What I need to do is put a front end on the link table that is used to
specify which products are in which sets (an N-N relationship). I've set up a
continuous form containing the products, with an include checkbox against
each item (the form at this point knows which selection set it is dealing
with). The only problem being that, as I've used a function to specify the
initial value of the checkbox it has set the form as read-only, which put a
hitch in my plan of handling the OnDirty event and using SQL in there to
add/delete the link record as neede).

This kind of thing is usually done with a main form bound to
the sets table along with a continuous subform bound to the
linking/junction table. The subform only needs an invisible
text box bound to the setID field and a combo box for the
set's products. The subform control's LinkMaster/Child
properties will automatically fill in the text box when a
product is added to the set.

The combo box's row source could be an unmatched query if
you don't want to allow the same propduct to be selected
more than once.

You probably want a button to delete a record from the
junction table/subform.

I think a check box would be redundant and confusing.