>Oops, did not check my control combos, before writing that. sorry.
>
>I do not use list, because they want to see deleted records.
>Same problem just reversed. No delete marks in listbox. :(
>
>I have a form that I did for them with listbox, but they just came back and said that they wanted to see which records were deleted. I am trying to simulate a browser window for them, without the ability to edit the fields and give them the multi select ability.
>
>Nothing is ever simple. :)
>Beth

IMO, deleted records should be considered deleted, gone. It is very tricky to give the user the option to recover lost records. For example, in a parent-child-relation, if you use a cascading delete, when deleting the parent the children also get deleted. Now, there is no built-in way to distinguish records deleted as part of the cascading delete, and records deleted years ago by the users.

If you do give users the ability to manually recover deleted records, I would suggest to hide them most of the time - SET DELETED ON - and then use special maintenance forms to recover deleted records.

In some cases, it is better not to delete a record, but to put another special mark, i.e. field. For instance, in Bata/Bolivia, purchase orders were not deleted - they were marked as "anulled" or whatever that is called in English. We didn't allow the user to delete the record, 'cause we wanted to keep a record of anulled orders, and deleted records will eventually disappear, when a PACK is done.