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.