>(sigh) Yeah, I'm using DO FORM, and I thought about that, but it would take some large changes in the framework for that app. At this point I don't want to make those kind of changes. With some more testing, I learned that it only happens to some forms, really only one at this point. This has confused me because the form is basically the same as the others in its basic characteristics. At this point, unless something jumps out at me, I'm gonna let the sleeping dog sleep.

Nothing wrong with DO FORM. Just a personal opinion, but I don't think that there's anything inherently better by creating the form as an object. DO tends to be faster, but you can do some things with an object before it's displayed that you couldn't easily do otherwise.

Just one more thought. Try setting the .Visible property to false, do the .Move thing, then set it to .T. in the .Init.