>I have seen this happen to me many times in 6, 7, and now VFP8. I change some code in some areas. I then run and get errors to find out that an area of code that I didn't even change and has nothing to do with the part I was coding in any way (via step on) is caused by the activate of the form being initiated again, yet there is nothing in the code now as there was not before that would tell the code to re-run the activate of the form (which is what causes the errors because there is code in the activate which I would not want to run at that time). I usually spend some time and figure out a work around, but that takes time and it is annoying to bandaid this with no explanation as to why it does that.
>
>Can anyone tell me why this occurs?

Sounds like you're trying to run the debugger and go back and forth between it an your form. Are you running the debugger in it's own frame? That may work better for you if you're not doing it that way.