George,

I've noticed all sorts of wierdness going on with the common dialog and any version of VFP debugger. It was annoying enough trying to work with it while I was putting together a Wiki article that I just plain gave up on the effort.

>Knowing how you love bugs...< bg >
>
>I ran across a minor problem with the debugger in VFP 7.0 SP1 and a programmtically ActiveX control, specifically the Microsoft Common Dialogs Control. I should note a couple of things before proceeding.
>
>First, this does not occur with the control dropped on a form. Since the control, however, must be dropped on a form in order to be available in a distributed application (plus you don't have access to the debugger), it isn't really major.
>
>Second, and perhaps more importantly, I haven't tested any of the other Microsoft distributed controls to see if the problem manifests itself with them.
>
>Here's what happened...From the command window I issued

oDialog = CREATEOBJECT("MSComDlg.CommonDialog.1")

Now the purpose of this was to examine the various properties to see if there was one that was undocumented, or if there some piece of information that I was missing in trying to determine the printer selected with the ShowPrinter method.
>
>I issued the oDialog.ShowPrinter from the command window and opened the debugger. Naturally, in the locals window there was oDialog and I expanded to examine the properties. As I scrolled down, up popped the printer dialog on top of the debugger. When I looked back at the locals windows, there was the method name. Apparently, the appearance of it in the window caused the method to fire.
>
>After several attempts, with the dialog re-appearing each time I failed, I finally managed to close the debugger.
>
>Not a real big deal, but unexpected.