Resolved >>> Common Dialog in Excel 2007

I have a book about Excel 2003 (http://www.amazon.com/Excel-Macro-Pr...3096938&sr=8-1) and it has a chapter about programming Common Dialogs. Now since it is pretty short book (less than 300 pages) I would expect some Excel 2007 VBA books that have closer to thousand pages to even mention Common Dialogs. Nope. Neither does Excel Help system. At least I didn't find.

So the question shortly: Did the name for Common Dialog change for Excel 2007 and if, then what is this new name?

I think Common is a word chosen by the book's author rather than Microsoft.

You might look in the VBEditor help system, keyword "Built in Dialog" (three words) for more on the subject.

From http://www.xcelfiles.com/comdlg.html:

The Win32® Common Dialog API functions are located in COMDLG32.DLL, which must be in the Windows system directory for the dialog interface to function.

The Common Dialog functions provide a standard set of Windows dialog boxes for operations such as opening, saving, and printing files, or selecting colors and fonts. The class creates objects that, with the exception of an object instantiation line, are code-compatible with Visual Basic's Common Dialog control.

Programs using the Visual Basic Common Dialog control require that COMDLG32.OCX be available and correctly registered. (Note this is the control and NOT the Dll, which all Windows systems have) If the Common Dialog class is included as a class module in a Visual Basic project, no other files are required. If the class is compiled as an in-process server, the resulting DLL will need to be available at run time and must be correctly registered.

The Win32 Common Dialog object is easier to use than the Visual Basic Common Dialog control because it doesn't need to be a part of a form, so there is less over head ie you don't need to have the users ensure that they have this control. The Common Dialog object (DLL) provides the same methods and properties as the Common Dialog control (OCX) and it can be used to replace the Common Dialog control in existing projects with very little modification to code.

Originally Posted by shg

From http://www.xcelfiles.com/comdlg.html:

The Win32® Common Dialog API functions are located in COMDLG32.DLL, which must be in the Windows system directory for the dialog interface to function.

The Common Dialog functions provide a standard set of Windows dialog boxes for operations such as opening, saving, and printing files, or selecting colors and fonts. The class creates objects that, with the exception of an object instantiation line, are code-compatible with Visual Basic's Common Dialog control.

Programs using the Visual Basic Common Dialog control require that COMDLG32.OCX be available and correctly registered. (Note this is the control and NOT the Dll, which all Windows systems have) If the Common Dialog class is included as a class module in a Visual Basic project, no other files are required. If the class is compiled as an in-process server, the resulting DLL will need to be available at run time and must be correctly registered.

The Win32 Common Dialog object is easier to use than the Visual Basic Common Dialog control because it doesn't need to be a part of a form, so there is less over head ie you don't need to have the users ensure that they have this control. The Common Dialog object (DLL) provides the same methods and properties as the Common Dialog control (OCX) and it can be used to replace the Common Dialog control in existing projects with very little modification to code.

Thank you, this answer is great!