word crashes when opening vb environment

Word crashes when opening vb environment code#

This function cannot be reused for another purpose, e.g. It means that ProcessDocument is dependent on the swModel and will be only able to work with active document (or the one assigned to swModel). Variable is initialized in the main function.

Word crashes when opening vb environment code#

In the below code snippet the swModel variable is declared at the module level which makes it accessible from within the ProcessDocument function. This would make a consumption of the function more predictable and function can be reused. Try to keep functions and modules as independent as possible from another functions, module level variables and environment. Single entry point in the macro Independent Functions And Modules With the setup above, only one function will be available for running: 'Consumes InitData to perform the work End Sub 'Initializes InitData End Sub Sub DoWork( Optional dummy As Variant = Empty) Running this function directly will most likely result into the 'Run time error 91: Object variable block variable set'Įnd Sub Sub Init( Optional dummy As Variant = Empty)

DoWork - Function which performs the work, however, it requires InitData to be initialized.

Running this as an entry point will not cause errors, but it will not produce any results This function itself doesn't perform the work.

Init - Function which initialized data, required to do work.

Running this function will result into expected outcome

main - Actual expected entry function.

The code below has 3 parameterless functions Most of the VBA macro enabled applications, such as MS Word, MS Excel, SOLIDWORKS, Autodesk Inventor would consider any parameterless function as a potential entry point of the macro. Depending on the requirement application can proceed and consider this as safe error or it can log the error or display the message to the user. Execution terminated' End IfĪnd it is up to the calling function to decide what to do with this case. Prefer to use descriptive names instead of commentĮrr.Raise vbError, '', 'Model of the component is null. When developing any application (VBA is not an exception) try to use as descriptive as possible names for variables, functions, procedures, modules, classes and events. Visit 5 best practices to make your VBA macro great blog article for the video demonstration of the practical application of the below guidelines. MS Word, MS Excel, SOLIDWORKS, Autodesk Inventor etc. These guidelines applies to any type of the macro, e.g. As macros are applications, they should be considered as such and all the practices for writing reliable, maintainable and stable application should still be applied when developing macros.īelow is the list of guidelines for improving the quality of the macro. In nowadays Visual Basic is mainly used in VBA macros format with a minor exception of several legacy applications.Īlthough VBA macros are usually small applications, those are still playing a major role in millions of organizations worldwide.