Linking Field Prompts and fixing VBA Reference Errors

David MeegoThe great postings around the blogsphere just keep coming. I am not complaining as the body of knowledge they provide to community is growing all the time.

My buddy, Mariano Gomez, who is a wealth of knowledge and is always willing to help on the newsgroups has come with a great article explaining why you should ensure you link prompts when working with Modifier and Dexterity.

The importance of linking your fields to their prompts in Microsoft Dexterity


Mohammad Daoud has also created a really useful article which discusses how to resolve VBA (Visual Basic for Applications) reference errors.  These are usually caused by the removal of a field from a form or report without removing the VBA reference first.

The Microsoft_Dynamics_GP.vba project references some objects that cannot be found. these objects are listed in the file: C:\Program Files\Microsoft Dynamics\GP\Dynamics.txt.

To remove the VBA references to fields no longer needed or available, follow the steps below:

  1. Copy the VBA code into a Notepad.exe window.

  2. Remove the Report or Window from VBA (Tools >> Customize >> Remove Current Window/Report from Visual Basic).

  3. Add the Report or Window back to VBA (Tools >> Customize >> Add Current Window/Report to Visual Basic).

  4. Add the required fields back to VBA (Tools >> Customize >> Add Fields to Visual Basic).

  5. Copy the VBA code back into the appropriate VBA Module.

  6. Compile the Project and Save.

Hope you find this info handy. 


Comments (1)

  1. Michael Johnson (the MBS Guru ) has posted a great article about removing invalid references from a Visual

Skip to main content