Hi,
Here's another one, in the expression builder in the DE enter the required expression, then hit return, (force of habit) VFP saves the expression with no error, but throws an error an runtime. I reported this to Microsoft, their reply was don't hit return.!!!!

>I am also having the same problem (found this after posting ny problem). This change in how filters work breaks almost all my forms because they have filters on multiple tables in the data enviroment.
>
>I cannot believe a fix will not be posted before the final release since it makes it impossible to test existing application in VFP 9 Beta (which work in VFP 7 and 8).
>
>>Hi,
>>Thanks for the reply, it was a difference in the way VFP9 handles filter expressions in the DE from VFP7, all filter expressions now require a leading "=" so that filter is saved as Filter = (!alias.fieldname) and not Filter = "!alias.fieldname" in the memo field in the scx, and it is treated as a string and not a logical expression.
>>
>>BTW the expression builder does it wrong too.
>>
>>>Not offhand, myself, but Garrett might. Garrett?
>>>
>>>>The reason for my interest in this bug, is that it was found trying to find a resolution to a still unresolved problem we are experiencing with our VFP7 app when we run it with VFP9Beta.
>>>>
>>>>Due to time constraints I have been unable to produce some repro code to send for debugging, and it is possibly related to the bug Garrett found.
>>>>
>>>>Do you have any ideas on how to resolve this problem, other than sending the whole app to microsoft.