To make sure that SET DELETED is really OFF, either change or check the option, just before running the view. I want to insist on this, because the fact that different datasessions can have different settings for SET DELETED (and some other commands) has wrought confusion to many a programmer.
To check the current setting:
? set("deleted")>Hi Hilmar,
>
>This behavior occurs outside of the main application too. I opened the view through the project manager in the main VFP window, and SET DELETED is OFF. The view works fine with DELETED()=.F., but not with DELETED()=.T., which is what is puzzling me. I even made sure SET DELETED was off, buy running the command in the command window.
>
>I agree about considering deleted records as gone. However, the client has some very odd requirements, which is requiring me to build a somewhat non-traditional solution.
The usual alternative is to have a field called "excluded", "inactive", "cancelled", or something to this effect. Then, you can easily show inactive clients (for instance), active ones, or both - just change the filter.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
