But you did place this control visually on the form, correct?

Including it in the installation package would be a good idea.

>Actually I just experimented on another machine doing what you describe (i.e., without using the test I described), and the app bombed because COMDLG32.OCX had not been installed/registered on that machine. If that OCX is not registered, then MSComDlg.CommonDialog is not available, and an OLE error will be thrown when the form containing the control is instantiated.
>
>The conclusion I reach is that a VFP app can not assume that MSComDlg.CommonDialog will be available unless the VFP installer you provide (for your own app) contains the OCX as a to-be-installed component. There is no guarantee that COMDLG32.OCX (aka MSComDlg.CommonDialog) already is installed on any given machine.
>