Thanks for the reply Bob. That certainly works well for simple cases and I'm sure I'll take advantage of that some day. What I've actually got is a situation where I want to change the control source for a field depending on the value of another field.
eg. when displaying the components of a 'toy car' product I'd have a 'Product' table & 'Component' table. A 'toy car' might be made up of 1 electric motor and 4 wheels amongst other things. The electric motor might only ever have 1 [u]fixed</u> description, which would be stored on the 'Component' table. The wheels, however, might have several [u]variable</u> descriptions, depending on the product. ie. rear right wheel, rear left wheel etc.
My subform is based on a 'Product/Component' table. Here I was intending to store the variable descriptions. When I display the subform I only want to pick up the relevant description field. So if the component was of a 'fixed' type the description would be mapped onto the 'Component' table and be non-editable. If it was 'variable' the description would be mapped onto the 'Product/Component' table and be editable. Each row would be examined as to whether the component was Fixed or Variable, and then the relevant table.column would be assigned as the field's control source. An alternative might be to have 2 fields for the descriptions, making 1 of them 'visible' & the other not 'visible'.
Using the subform's 'current' event I'm able to do either of the above but the effect applies on [u]all</u> rows not just individual ones. (I want to show all rows ie. continuous form, not 1 at a time.)
Hope this makes sense !! What I'm actually working on is to do with high volume printing, concerning inserts, stock codes etc, but I thought the toy car analogy would be easier to illustrate the point.
I'd guess that I'm trying something that can't be done in Access in which case I'll have to redesign the data, unless someone knows a neat way round ;).
Paul
|