>Bruce, I have experienced that at a customer site with FPW 2.6a. Every time this occurred, we deleted the *.fxp and everything then worked.

Yes, I seem to recall behavior like that with fxp & spx years ago, now that you mention it...but haven't seen it in vfp to date, despite several years of constant use. I think it's a beta6 bug after all, I checked last night and SET DEVELOPMENT is ON in my Options. And I tried numerous times and ways to duplicate problem, but couldn't (of course! :))...Ah well, just something to be aware of...