0
How can you debug a macro you have recorded or modified in Microsoft?
Wiki User
∙ 11y ago
Microsoft Office products convert recorded Macros into Visual Basic code. This code can be read and hand edited using the VBA Editor available from the menus.
Wiki User
∙ 11y ago
Add your answer:
Earn +20 pts
What is the meaning of macro in Microsoft Word?
A macro is a series of commands that is recorded so it can be played back, or executed, later. There are a couple different ways to create Word macros: The first and easiest way is to use the macro recorder; the second way is to use VBA.
What has the author MICROSOFT written?
MICROSOFT. has written: 'MICROSOFT MACRO ASSEMBLER 5.1 REFERENCE'
What is masm?
it means Microsoft Macro Assembler
What is the main route of infection for macro viruses?
Microsoft Office documents
What is a small program that can be written inside a file?
Macro in Microsoft Word
What virus attaches to documents such as word or excel files?
Macro viruses use Microsoft Word and Excel's capabilities to embed code and programs into the document. When the document is opened, the macro virus is executed and infects your computer.
What programs are most likely by a macro virus?
Microsoft Word and similar applications.
You have recorded a macro. By mistake you recorded an action in it which you do not want. How will you remove the unwanted action without having to record the whole macro again?
All you need to do is edit the macro and remove the section you do not want in the macro. Excel 2007: From the Developer tab on the Menu ribbon, click on the Visual Basic icon in the Code section. See related links for a detailed tutor on how to edit an Excel macro.
What pre-processer will do in c language?
The preprocessor (or precompiler) processes all the preprocessor directives and macro definitions within your source files. In other words it creates modified source files where all directives and macros are completely stripped out and replaced by their respective definitions. For instance, each #include statement in your source inserts the named header just as if you'd copy/pasted that entire header into your source. However, prior to insertion, the header itself must be preprocessed, thus it is the modified code that is physically inserted. Once inserted, the #include directive is removed from the modified source. Since the compiler works with modified source files (intermediate sources), the compiler never sees your macro definitions and therefore cannot help you debug them. A macro is a primitive text replacement system so if this creates invalid code, a compiler error occurs but the compiler cannot tell you where that error originated because it is processing code that does not exist in your source.
What are the file formats for Microsoft Word?
Original: .docFor 2007 and 2010 Microsoft Word new file formats were introduced:".docx" - Word Document".docm" - Word Macro-Enabled Document".dotx" - Word Template".dotm" - Word Macro-Enabled TemplateAdditional Supports:.dot.mht, .mhtml.xml.rtf.htm, .html.rtf.txt
How do you identify the type or name of a virus which auto-inserts running text into Word Excel and Google?
You mean a macro virus? Macro viruses infect Microsoft Excel and Word documents. When the infected document is viewed, the virus is executed.
What is a macro in c plus plus?
A macro is preprocessor definition that is processed prior to compilation. All occurances of a macro within your C++ source code are replaced with the macro definition, much like an automated search-and-replace-all operation. If the macro's definition is a function with one or more arguments, then the function is inline expanded within your code, replacing the defined arguments with the arguments that were passed to the macro. However, macro functions are not type safe and cannot be debugged because they only exist in your source code; the compiler only sees the intermediate code emitted by the preprocessor, at which point all macro definitions will no longer exist. To address this problem, C++ also supports the concept of template functions, which not only eliminates any unwanted inline expansion (resulting in smaller code), but also ensures that all calls to the function are type safe and can be debugged in the normal way. That said, macro functions, when used appropriately, can greatly simplify your code and can achieve things that would be difficult if not impossible to achieve with C++ alone. The ability to use code fragments via a macro is one such possibility. However, when combined with preprocessor directives such as #ifdef DEBUG, macros can also be used to provide useful and powerful debugging routines that only exist in debug code, compiling to no code in release builds. This cannot be achieved with C++ alone.
