Jess,
I had thought about the solution that you mention, but I was desperately trying to resist going down that particular avenue. David (Frankenbach) has, however, come up with a brilliant solution. Create a view to return the fields that you need, and add an extra column(s) to the field list. In my case I just add a .F. to the list of things to select. The SQL then looks something like:
SELECT product_name, product_description, .f.
Unlike selecting into a cursor, when the view is executed, the extra column(s) in the view are read/write, so the checkbox is quite happy to be bound to it, and the values are retained as long as the view is open. No need for temporary tables!
I think that this is a great 'trick' to add to the arsenal.<g>
>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.
