I'm not sure what you mean, Christian. If you're just pointing out to me what Microsoft's fix does, thanks. Although I kind of figured that much out on my own. The wrapper function that Microsoft sent was called "DisableDropShadows.exe" so I kind of figured that it "Disabled Drop Shadows". I'm just smart that way. :) Just kidding. I don't mean to pick on you.

Actually, what I meant by my comment in the last message was that I think it would make more sense for Microsoft to issue an actual "patch" - like a service pack etc. Something that could be applied once and have the problem go away because FoxPro would handle it correctly in the future.

The wrapper function that they sent is an okay workaround for now. It insures that, even if the user re-enables drop shadows - that VFP will still operate properly. Of course, it also means that every time the user runs my app, they will disable drop shadows on their workstation. (Note that the wrapper does not re-enable them when FoxPro shuts down.) So, the "correct" course of action is to fix FoxPro itself so that it does not have the problem.

I hope this clarifies things a bit.