Share this Page URL

Chapter 42. Working with Visual Basic fo... > Secrets of the Office Masters: Eleme... - Pg. 1068

Working with Visual Basic for Applications 1068 · Presentations rule in PowerPoint. Inside a presentation, there are Slide objects, and the Text- Frame and TextRange objects on the slides hold the text. Master objects control the Slide, Title, Handout, and Notes masters. · Publisher bears many similarities to Word, except there's more emphasis on the predefined objects available in Publisher--for example, Layout guides and Connector formats. · Outlook objects run the gamut of Outlook applications, from contacts to e-mail to Calendar items to to-do lists. · FrontPage has two independent object models, one for the editor itself, and the other for HTML constructs (tags and the like). · Access, always the oddball, doesn't have a Project object (although there is an OpenAcces- sProject command). Instead, it deals with Forms, Reports, Modules, and Screens--where the Screen object is just the currently active form, report, or control. There are also object models for Data Access Objects (DAO), and even the Visual Basic Editor itself. The DAO and Visual Basic Editor object models are robust, and a skilled VBA programmer can practically work miracles with them. Troubleshooting Distributing Macros Informally I've created a few Word macros that I would like to share with my co-workers, but every time I try, they say they're unable to open the macros. What am I doing wrong? The biggest problem when trying to share macros is security; any time Word opens a template or