>Jess,
>
>You were right the first time. Rows will be processed based on selections made by the user. If this was all that they had to do, you first suggestion would be great. Unfortunately, not only must the user select whether or not to include a row for processing, they must also select a value for each row, the columns should actually be:
>
>Product Name Product Code Quantity Include?
>----------------------------------------------
>
>I want the user to select the rows that they require, as well as either accepting the default quantity for each selected row, or changing it to the desired value. My plan was to add another column and use a spinner to allow them to do this. Sorry, I probably should have said this in the original thread!
>

Steve,

If thats the case then the absolute remedy is to create an extra field for checkbox bounding. The problem again this time is multi-user issues, because what if more than one user activated the same module of selection ? And so, your dbf filename should be unique to every user. We use SYS(2015) for that matter.

>>>Guess I assumed they was going to porocess the selections
>>>based upon if the checkbox was checked.
>>>
>>>If the grid will be just save back to the table,
>>>they will definitely have to add a logical field
>>>to thier table.
>>
>>
>>Logical Field or Numeric (width 1) . Where 0 equivalent to .F. 1 equivalent to .T.