It happens in both VFP 5 and 6. I am confident that you can easily reproduce it.
The rule expression is an expression that must evauluate to .T. before a row can be saved from a view. It is used for data integrity.

I personally don't use them, but I have written a utility that equates to a view editor of sorts, and recently added the ability to edit this property in views. If you add a RuleExpression accidentally, or change your mind, you must remove it somehow. But apparently removing it breaks the view.

Since this behavior is not documented on MSDN, I'll be reporting it as a bug.

>I haven't seen this behavior, but since I use views a lot, am curious where and under what circumstances you did. Is this in VFP 6.0/5.0? And why were you removing the RuleExpression (i.e. I don't even know what that is used for so don't know why you'd want to remove it).
>
>Sylvia
>
>>Pascal Declercq pointed out what at first appeared to be a bug with eView, but now looks to be a bug with Visual Foxpro.
>>
>>When trying to remove a view's RuleExpression property, using the following syntax:
>>
>>DBSETPROP("MyView", "View", "RuleExpression", "")
>>
>>the DBSETPROP returns .T., but when opening the view subsequently VFP throws an error 1584: "Error reading property from the database; property is ignored." The view then opens and operates like normal.
>>
>>This has happened with every view I have tested, in multiple databases.
>>
>>Can anyone confirm or further explain this behavior? Is there any other way to remove a view's rule expression? (BTW, there does not have to be a RuleExpression present initially for this behavior to surface)
>>
>>Thanks.