Well, based on my experience in the debugger, I added a throw-away line just before the form.refresh() that forced foxpro to re-evaluate the filter expression. Lo and behold, the problem when away.


lctempvar=filter('tablename')


Anybody have any idea why foxpro became so absent minded? I'm guessing that it was a timing issue, the refresh code ran before the data engine had actually set the filter. Just a WAG. Anybody have a better explanation?



>I'm getting an error 1148 (Expression has been re-entered while the filter is executing.) when the beforerowcolchange event fires in the second grid on a form after the refresh.
>
>The bizzare thing is that if I put a breakpoint in the watch window of the debugger on the line
>
>filter('cat2')
>
>the error DOES NOT OCCUR! When I remove the breakpoint, the filter condition get's lost somehow. VFP seems to just flush it away.
>
>Has anyone seen anything like this? There is too much code executing to post. I'm running within the Mere Mortals framework.
>
>I think this is a new 7.0 bug because it wasn't happening in 6.0 but I'm not sure. I'll admit I don't know what the problem is.