>Michelle,
>
>This is just to give you maybe a couple of new ideas, not trying to get you to change your whole app...
>
>There are knitting machines in the database I'm working on at the moment. The end user wants to be able to create various subsets of those machines for reports. I give them a selection grid with a checkbox and the MachineName the grid is based on a temp table that has one row for every machine and it sets the lSelected for the row based on the previously selected items stored in a separate table. It's really pretty workable and is all data driven. They can add new machines and create new subsets without any code changes. The client hasn't seen this yet I hope they think it's as cool as I do. *g*

I've done something similar for the doctors, once - they had to check five or ten items (things they've performed) for every patient; the lookup table was some 3000 records long, so I've kept a private selection from it for each doctor, and they usually kept them below 50 items. A good thing to keep in mind when you go to a specialist - their bag of tricks ain't so deep :). Now this short list still wasn't quick enough, because there were some standard selections which had to be repeated often, so I've made a standard selections lookup table, where they could pick from. They loved it, and I'm sure your clients will love your solution - you only have to think of a reasonable amount to charge for it :)