> Right now, the only way I can see doing this is by making the checkbox > relate to a column in the same table that would mark it as selected. Then a > button would execute an eep that would process all so marked rows. > > It seems to me that there might be a better way to do this. Couldn't a > checkbox not actually save to the table before the process runs? Is there a > way to enforce the DB change before the processing begins?
By "better way" do you mean one that does not involve adding that extra, non-multi-user-safe column to the table? You could do this in two ways: with a temp table that contains the Yes/No processing column, or by basing your form on the real table but making the checkbox a variable, rather than DB, checkbox. In the second case, in the OnClick code, if the box is being checked you would take "some action" action to ensure that the row is included in the processing, if it is being unchecked you do the opposite. Two possibilities for the "action" are to add or remove the primary key value for that row to a delimited list in a variable, or to insert or delete it from a temp table of primary key values. -- Larry
