Ed,

Do you have some code in the Form Activate, Deactivate methods? What if you seed DEBUGOUT commands instead of messagebox() to track what's going on? Does it make a difference if you are using the FoxPro or Debug frame for the debugger?

>I appear to be having significant problems with VFP 5.0, Service Pack 3, having to do with the debugger. I can run my code and produce the expected results when I'm stepping through it with the debugger. However, I can run it without the debugger and find that some events (specifically InteractiveChange, Valid and LostFocus) do not appear to run. I say "do not appear" because it looks like the values are not what I expect in a text box as I run the application.
>
>What's even more strange is that I can add a MESSAGEBOX command somewhere in the LostFocus() method, which updates a number of other fields on the form before the object loses focus, and everything works fine. If MESSAGEBOX is in the method code, and I hit a button on a toolbar or menu item that saves the info in the form, the message box appears, the form on the screen appears current, and the record is saved. However, if I leave the MESSAGEBOX out and do the same test, the form doesn't reflect the record changes, nor does the saved record.
>
>Any ideas?
>
>Ed