VBA Developer's Guide: Microsoft Dynamics GP 2010

Microsoft Dynamics GP 2010
VBA Developers Guide

Copyright Copyright 2010 Microsoft Corporation. All rights reserved.
Limitation of liability This document is provided as-is. Information and views expressed in this document, including
URL and other Internet Web site references, may change without notice. You bear the risk of using
it.
Some examples depicted herein are provided for illustration only and are fictitious. No real
association or connection is intended or should be inferred.
Intellectual property This document does not provide you with any legal rights to any intellectual property in any
Microsoft product.
You may copy and use this document for your internal, reference purposes.
Trademarks Microsoft, Excel, Microsoft Dynamics, Outlook, Visual Basic, Windows, and Windows Vista are
trademarks of the Microsoft group of companies. FairCom and c-tree Plus are trademarks of
FairCom Corporation and are registered in the United States and other countries.
All other trademarks are property of their respective owners.
Warranty disclaimer Microsoft Corporation disclaims any warranty regarding the sample code contained in this
documentation, including the warranties of merchantability and fitness for a particular purpose.
License agreement Use of this product is covered by a license agreement provided with the software product. If you
have any questions, please call the Microsoft Dyamics GPCustomer Assistance Department at 800-
456-0025 (in the U.S. or Canada) or +1-701-281-6500.
Publication date March 2010

Contents
Introduction ................................................................................................................................. 2
Whats in this manual .................................................................................................................. 2
Prerequisites .................................................................................................................................. 2
Product support ............................................................................................................................ 3
Symbols and conventions............................................................................................................ 3
Whats next .................................................................................................................................... 4
Part 1: Using VBA ................................................................................................................ 6

Chapter 1: VBA Overview ............................................................................................. 7
The Visual Basic Editor ................................................................................................................ 7
The VBA project ............................................................................................................................ 8
Objects .......................................................................................................................................... 10
Programming model .................................................................................................................. 12
Using VBA with the Modifier ................................................................................................... 13
Online help .................................................................................................................................. 14
Multiple third-party products................................................................................................... 14
Chapter 2: Programming Windows ................................................................... 15

Working with windows in a VBA project ............................................................................... 16
Programming a window object ................................................................................................ 17
Using window events ................................................................................................................ 18
Window open events.................................................................................................................. 19
Window close events.................................................................................................................. 20
Window activate events............................................................................................................. 21
Modal dialog events ................................................................................................................... 22
Using window properties and methods.................................................................................. 24
Chapter 3: Programming Window Fields ..................................................... 31

Working with window fields in your VBA project................................................................ 32
Programming a window field object ....................................................................................... 34
Using window field events ....................................................................................................... 35
Got focus events.......................................................................................................................... 36
User changed events .................................................................................................................. 38
VBA DEVELOPERS GUIDE i

C O N T E N T S
Changed event............................................................................................................................ 40
Lost focus events ........................................................................................................................ 41
Using window field properties and methods ........................................................................ 43
Working with field values......................................................................................................... 47
Verifying field values................................................................................................................. 51
Window field type reference .................................................................................................... 54
Chapter 4: Programming Grids ............................................................................. 73

Working with grids in your VBA project................................................................................ 74
Programming a grid object ....................................................................................................... 76
Types of grids.............................................................................................................................. 77
Using grid events ....................................................................................................................... 78
Using grid properties and methods ........................................................................................ 82
Chapter 5: Programming Reports ....................................................................... 83

Working with reports in your VBA project ............................................................................ 83
Using report events.................................................................................................................... 85
Start/End events ........................................................................................................................ 86
Band events ................................................................................................................................. 87
Using report properties and methods..................................................................................... 91
Working with report fields ....................................................................................................... 92
Exporting data to other applications....................................................................................... 95
Chapter 6: Storing Additional Data .................................................................. 97

Understanding the DUOS......................................................................................................... 97
Structure of the DUOS............................................................................................................... 98
Working with DUOS data objects.......................................................................................... 100
Retrieving a DUOS data object............................................................................................... 101
Deleting a DUOS data object .................................................................................................. 101
Updating a DUOS data object ................................................................................................ 101
DUOS properties and methods.............................................................................................. 102
Using the DUOS ....................................................................................................................... 103
Chapter 7: Distributing a Project ..................................................................... 113

Enabling VBA ............................................................................................................................113
References to external components ........................................................................................113
Distributing project files...........................................................................................................114
ii V B A D E V E L O P E R S G U I D E
C O N T E N T S
Package files .............................................................................................................................. 115

Package file import/export issues ......................................................................................... 118
Part 2: VBA Object Library .............................................................................. 120

Chapter 8: Window Object ..................................................................................... 121
Activate method................................................................................................................ 122
AfterActivate event .......................................................................................................... 123
AfterClose event ............................................................................................................... 124
AfterModalDialog event.................................................................................................. 125
AfterOpen event ............................................................................................................... 128
BeforeActivate event ........................................................................................................ 129
BeforeClose event ............................................................................................................. 130
BeforeModalDialog event................................................................................................ 131
BeforeOpen event ............................................................................................................. 134
Caption property .............................................................................................................. 135
Changed property............................................................................................................. 136
Close method..................................................................................................................... 137
EventMode property ....................................................................................................... 138
Height property ............................................................................................................... 140
Hide method ..................................................................................................................... 141
IsLoaded property ............................................................................................................ 142
Left property ..................................................................................................................... 143
Move method ................................................................................................................... 144
Name property ................................................................................................................. 145
Open method..................................................................................................................... 146
PullFocus method ............................................................................................................. 148
Required property ............................................................................................................ 150
Show method .................................................................................................................... 151
Top property ..................................................................................................................... 152
Visible property ................................................................................................................ 153
Width property ................................................................................................................. 155
Chapter 9: Field Object ............................................................................................. 157

AfterGotFocus event ........................................................................................................ 158
AfterLostFocus event ....................................................................................................... 159
AfterUserChanged event................................................................................................. 160
BeforeGotFocus event ...................................................................................................... 161
BeforeLostFocus event ..................................................................................................... 162
BeforeUserChanged event............................................................................................... 163
Caption property .............................................................................................................. 165
Changed event .................................................................................................................. 166
Empty property................................................................................................................. 168
Enabled property .............................................................................................................. 169
Focus method .................................................................................................................... 170
FocusSeg method .............................................................................................................. 171
VBA DEVELOPERS GUIDE iii

C O N T E N T S
Height property ............................................................................................................... 173

Left property .................................................................................................................... 174
Locked property ............................................................................................................... 175
Move method ................................................................................................................... 176
Name property ................................................................................................................ 177
Object property................................................................................................................. 178
Parent property................................................................................................................. 180
Required property............................................................................................................ 181
TabStop property.............................................................................................................. 182
Top property .................................................................................................................... 183
Value property .................................................................................................................. 184
ValueSeg property............................................................................................................ 187
Visible property ............................................................................................................... 188
Width property ................................................................................................................ 189
Chapter 10: Grid Object ............................................................................................ 191

AfterLineChange event ................................................................................................... 192
AfterLineGotFocus event ................................................................................................ 193
AfterLineLostFocus event............................................................................................... 194
BeforeLineChange event ................................................................................................. 195
BeforeLineGotFocus event ............................................................................................. 196
BeforeLineLostFocus event............................................................................................. 197
BeforeLinePopulate event............................................................................................... 198
Changed property ............................................................................................................ 199
EventMode property ...................................................................................................... 200
Hide method .................................................................................................................... 201
Left property .................................................................................................................... 202
Move method ................................................................................................................... 203
Name property ................................................................................................................ 205
Show method ................................................................................................................... 206
Top property .................................................................................................................... 207
Visible property ................................................................................................................ 208
Chapter 11: Report Object ...................................................................................... 209

BeforeAF event ................................................................................................................. 210
BeforeAH event .................................................................................................................211
BeforeBody event ............................................................................................................. 212
BeforePF event.................................................................................................................. 213
BeforePH event................................................................................................................. 214
BeforeRF event.................................................................................................................. 215
BeforeRH event................................................................................................................. 216
Cancel method.................................................................................................................. 217
End event........................................................................................................................... 218
EventMode property ...................................................................................................... 219
Legend property............................................................................................................... 220
Name property ................................................................................................................ 221
Start event.......................................................................................................................... 222
iv V B A D E V E L O P E R S G U I D E
C O N T E N T S
Chapter 12: VBAGlobal Object........................................................................... 223

DUOSObjectCombineID method ................................................................................... 224
DUOSObjectExtractID method....................................................................................... 226
DUOSObjectsGet method................................................................................................ 228
UserInfoGet method......................................................................................................... 230
Chapter 13: DUOSObjects Collection ......................................................... 231

Exists property .................................................................................................................. 232
Item property..................................................................................................................... 233
Name property.................................................................................................................. 234
Remove method ................................................................................................................ 235
SortByExisting property .................................................................................................. 236
Chapter 14: DUOSObject Object ...................................................................... 239

ID property ........................................................................................................................ 240
Properties property........................................................................................................... 241
Chapter 15: DUOSProperties Collection................................................... 243

Count property.................................................................................................................. 244
Exists property .................................................................................................................. 245
Item property..................................................................................................................... 246
Remove method ................................................................................................................ 248
Chapter 16: DUOSProperty Object ................................................................ 249

Name property.................................................................................................................. 250
Value property................................................................................................................... 251
Chapter 17: UserInfo Object ................................................................................ 253

CompanyName property ................................................................................................ 254
CreateADOConnection method ..................................................................................... 255
IntercompanyID property ............................................................................................... 256
UserDate property ............................................................................................................ 257
UserID property................................................................................................................ 258
UserName property.......................................................................................................... 259
Appendix .................................................................................................................................. 262

Appendix A: VBA Errors ........................................................................................... 263
Handling VBA errors ............................................................................................................... 263
VBA error reference.................................................................................................................. 264
Glossary ..................................................................................................................................... 271
Index............................................................................................................................................... 275
VBA DEVELOPERS GUIDE v

vi V B A D E V E L O P E R S G U I D E
INTRODUCTION
Introduction
Microsoft Visual Basic for Applications, or VBA, is a standard
programming language used by Microsoft Office products, as well as by
many other software providers who choose to embed VBA. Applications
such as Microsoft Dynamics GP host VBA as part of the Modifier. The
tools available in the VBA environment allow you to customize windows,
fields and reports. In addition, you can attach VBA code to fields you create
using the Modifier.
Whats in this manual

The VBA Developers Guide is designed to teach the basics of using VBA
with Microsoft Dynamics GP. The manual is divided into the following
parts:
Part 1, Using VBA, provides information on how you can program

windows, window fields, grids and reports, as well as store additional
application data.
Part 2, VBA Object Library, provides reference information about

properties, methods and events for objects in Microsoft Dynamics GP.
Prerequisites
Keep in mind that VBA is a powerful programming language, and a basic
knowledge of VBA programming concepts is required. If you havent
worked with VBA before, we strongly recommend you review one of the
many books available that discuss programming with VBA.
The remainder of the manual assumes that you are already familiar with
VBAs programming concepts and features, as well as Microsoft Dynamics
GP. It explains how to use your existing VBA knowledge to work with the
VBA capabilities available with the accounting system.
2 V B A D E V E L O P E R S G U I D E
IN TRO DUCT IO N
Product support
Technical support for VBA can be accessed by the following methods:
Telephone support Technical Support at (888) 477-7877 between 8:00

a.m. and 5:00 p.m. Central Time, Monday through Friday. International
users can contact Technical Support at (701) 281-0555.
Internet VBA Technical Support is also available online through

CustomerSource or PartnerSource, and is accessible from
www.microsoft.com/Dynamics/GP.
Symbols and conventions

To help you use the VBA documentation more effectively, weve used the
following symbols and conventions within the text to make specific types of
information stand out.
Symbol Description
The light bulb symbol indicates helpful tips,
shortcuts and suggestions.
Warnings indicate situations you should be

especially aware of.
Margin notes summarize Margin notes call attention to critical

important information. information, and direct you to other areas of
the documentation where a topic is explained.
Convention Description
Part 1, Using VBA Bold type indicates a part name.
Chapter 1, VBA Quotation marks indicate a chapter name.
Overview
Setting window fields Italicized type indicates a section name.
set 'l_Item' to 1. This font is used for VBA code examples.
RUNTIME.EXE Words in uppercase indicate a file name.
Visual Basic for Acronyms are spelled out the first time theyre
Applications (VBA) used.
TAB or ALT+M Small capital letters indicate a key or a key
sequence.
VBA DEVELOPERS GUIDE 3

I N T R O D U C T I O N
Whats next
Before you can begin using VBA, be sure to complete the following tasks:
1. Install Microsoft Dynamics GP.

The runtime engine available with Microsoft Dynamics GP includes the
components necessary to support the VBA environment.
2. Register the Modifier.

To activate the VBA environment, you must register the Modifier. The
registration keys to register the Modifier are supplied with the
accounting system. Once youve registered the Modifier, you can access
the Visual Basic environment.
3. Review Chapter 1, VBA Overview.

This chapter explains the basics of how the accounting system
integrates with the Visual Basic environment. Once youve reviewed
the information in this chapter, you can use the remainder of the
manual to learn specific ways you can use VBA with the accounting
system.
PART 1: USING VBA
Part 1: Using VBA
Use the information in this portion of the documentation to understand
how to begin using VBA with Microsoft Dynamics GP. The following is a
list of the topics discussed:
Chapter 1, VBA Overview, explains the basics of the VBA environ-

ment and how it integrates with Microsoft Dynamics GP. It also
explains the components of Microsoft Dynamics GP youll use when
creating projects in VBA.
Chapter 2, Programming Windows, explains how to use VBA with

the window object.
Chapter 3, Programming Window Fields, explains how to use VBA

with the window field objects.
Chapter 4, Programming Grids, explains how to use VBA with the

grid object (scrolling window).
Chapter 5, Programming Reports, explains how to use VBA with the

report object.
Chapter 6, Storing Additional Data, explains how to store user-

defined data using the Dynamic User Object Store (DUOS).
Chapter 7, Distributing a Project, explains how to package and

deliver a VBA project.
Chapter 1: VBA Overview
Before you start using VBA, its important that youre familiar with the
VBA components specific to Microsoft Dynamics GP. The following
sections explain each of these in detail:
The Visual Basic Editor

The VBA project
Objects
Programming model
Using VBA with the Modifier
Online help
Multiple third-party products
The Visual Basic Editor

You will use the Visual Basic Editor for building and maintaining a VBA
project. Once you register the Modifier, the Visual Basic Editor becomes
accessible though the Tools submenu of the Microsoft Dynamics GP menu.
The following illustration shows this menu:
Modifier and VBA menu

options are available after
you register the Modifier.
To open the Visual Basic Editor, point to Customize on the Tools submenu,
and then choose Visual Basic Editor.
To create or edit VBA code, you must have appropriate user privileges. Typically,
this means being part of the Administrators group or the Power Users group on
Windows XP. On Windows Vista, it means launching Microsoft Dynamics GP
with Administrative privileges.

PA RT 1 U S I N G V B A
The following illustration shows how an existing project looks when

viewed in the Visual Basic Editor:
The Visual Basic Editor is

the environment where
youll define and maintain
a VBA project.
The Visual Basic Editor is similar for each host application, so if youve
used VBA with Microsoft Excel or Word, the Visual Basic Editor in
Microsoft Dynamics GP will be familiar.
The VBA project

The Visual Basic Editor stores customizations in a project file. The first time
you open the Visual Basic Editor, the runtime engine automatically creates a
new, empty project file that is named based on the current dictionary. For
example the VBA project created for Microsoft Dynamics GP is
DYNAMICS.VBA.
If youre working with a third-party application, VBA creates a separate project to

store customizations named NAME.VBA, where NAME is the name of the third-
party products application dictionary.
C H A P T E R 1 V B A O V E R V I E W
You can view a project using the Visual Basic Project Explorer:
Objects defined for your

project appear in the
Project Explorer.
Windows, reports and fields are not automatically part of the project. When
you begin working with VBA, youll selectively add to your project the
window, field and report objects you want to work with. Once added to
your project, you can reference these objects in VBA. In addition, the Visual
Basic Editor lets you add VBA user forms, user-defined procedures and
user-defined class modules to your VBA project.
The VBA Editor lets you develop and maintain a single project at a time. To
work with several different projects, store each project file in a separate
location. When you need to work on a project, copy it to the same location
of the runtime engine, then rename the file name.VBA, where name is the
name of the dictionary the project is based on.
After youve completed a VBA project file, youll distribute it to users. This
file contains your VBA code, the objects youve referenced in your VBA
code, and any VBA user forms you choose to use.

Objects
Applications expose their functionality to VBA through a set of
programmable objects. These objects include windows, reports, grids and
Dynamic User Object Store (DUOS) objects. The relationship each object has
to another object is expressed in a hierarchical object model, shown in the
following illustration:
Window
Window fields
Report
Report fields
Grid
Window fields
UserInfo
DUOSObjects
DUOSObject
DUOSProperties
DUOSproperty
Object
Collection Object
The organization of the model is important, since you must navigate

through the object model within VBA code to access lower-level objects. For
example, to access a window field, you must first indicate the fields
window object:
'Set a field on a window

CustomerMaintenance.CustomerID.Value = "AARONFIT0001"
The following sections explains each object in more detail.
Windows
Most of the VBA programming youll complete for windows will involve
the following objects.
Object Description
Window Represents an open window.
Window field Represents a field in a window.
Refer to Chapter 2, Programming Windows, and Chapter 3,

Programming Window Fields, for more information about using VBA
with windows.
Grids
Grids are VBAs definition of a scrolling window. When working with
grids, youll use the following objects:
Object Description
Grid Represents a grid (scrolling window) in an open
window.
Window field Represents a field in a grid.
Refer to Chapter 4, Programming Grids, for more information about

using VBA with grids, and Chapter 3, Programming Window Fields, for
information about programming window fields within a grid.
Reports
When working with reports, youll use the following objects:
Object Description
Report Represents a report.
Report field Represents a field in a report.
Refer to Chapter 5, Programming Reports, for more information about

using VBA with reports.
User information
When implementing a VBA integration, you may need to retrieve
information about the user currently logged into Microsoft Dynamics GP.
The UserInfo object provides access to this information. Refer to Chapter 17,
UserInfo Object, for more information about retrieving user information.

Dynamic User Object Store (DUOS)

The Dynamic User Object Store (DUOS) allows you to store and display
user-definable data.
Object/Collection Description
DUOSObjects collection Contains all user-definable data objects.
DUOSObject object Represents a single data object.
DUOSProperties collection Contains all properties for a data object.
DUOSProperty object Represents a single property for a data object.
Refer to Chapter 6, Storing Additional Data, for more information about

using VBA with the DUOS.
Programming model
Each object in the object model has defined methods and properties you can
use in VBA code to manipulate the behavior of the object. Methods and
properties for objects are declared using standard VBA object.method and
object.property syntax. Most objects also have specific events that specify
when associated VBA code executes for the object.
Methods
Methods are actions you can perform for a given object. Methods include
opening and closing a window or moving a field in a window. For example,
the field object uses the Focus method to move the focus to a different field
in the window:
'Move the focus to the salesperson field

SalespersonID.Focus
Properties
Properties are characteristics you can retrieve or set for a given object.
Properties include the title of a window, or the value of a field. For example,
you can use the Caption property to change the name of a window or field:
'Change the prompt for a field

CustomerMaintenance.CustomerID.Caption = "Patient ID"
'Change the title of a window

CustomerMaintenance.Caption = "Patient Maintenance"
Events
Youll write the majority of your VBA code within individual event
procedures. Each event procedure executes VBA code at certain times for a
specific object, such as when the user changes the value of a field, clicks a
button, prints a report, or opens a window. You can see these predefined
event procedures in the VBA Code window.
Object list.
Event procedures specify

when VBA code runs. The
event procedures listed
here are specific to
window objects.
For example, BeforeOpen is an event for a window object. This event

executes the associated event procedure when the specified window opens.
In the following example, the BeforeOpen event executes a procedure
when the Receivables Transaction Entry window opens:
Private Sub Window_BeforeOpen()

SortBy.Value = 3 'Set the sort list to "by Date"
DocumentType = 7 'Set the document type to "Returns"
End If
Using VBA with the Modifier

Refer to the Modifier The primary reason to use VBA with the Modifier is to apply programming
Users Guide for logic to new fields you add to a window using the Modifier. By using VBA
additional information with fields added using the Modifier, you can:
about creating new
fields for a window Create push buttons that perform additional tasks, such as opening a
VBA user form, launching another application, or performing calcula-
tions. Refer to Chapter 3, Programming Window Fields, for more
information about using VBA with push button fields.
Add new data entry fields that store additional data in the Dynamic
User Object Store (DUOS). Refer to Chapter 6, Storing Additional
Data, for more information about using the DUOS.

Online help
After you install and register the Modifier, youll have access to online help
for the Visual Basic Editor, the VBA programming language, and for
objects, methods and properties in Microsoft Dynamics GP. Use either of
the following methods to display specific help topics:
Open the help for Microsoft Dynamics GP. A link to the VBA help can
be found there.
Highlight a keyword in the Code window, such as an objects property

or method and press F1. Context-sensitive help for that item will
appear in the help window.
Multiple third-party products

By default, VBA can work with objects from the dictionary that the VBA
project is associated with. For example, the Microsoft Dynamics GP VBA
project can work with resources from the Microsoft Dynamics GP
dictionary (Dynamics.dic). It is possible to have your VBA project reference
objects in other dictionaries. To do this, you must create a reference in the
VBA project to the other dictionary.
To create a reference from a VBA project to another dictionary, select the

VBA project in the VBA Explorer. Choose References from the Tools menu
in the VBA environment. Mark the check box for the dictionary you want to
make references to.
When creating references to other dictionaries, you cant have circular references.
For example, if your Microsoft Dynamics GP VBA project references the SmartList
dictionary, the VBA project for the SmartList dictionary cannot have a reference
back to the Microsoft Dynamics GP project.
Chapter 2: Programming Windows
Programming windows using VBA involves adding a window to your
project, specifying the window events youll use to execute VBA code, and
using window methods and properties to customize window display.
Information about programming windows is divided into the following

sections:
Working with windows in a VBA project

Programming a window object
Using window events
Window open events
Window close events
Window activate events
Modal dialog events
Using window properties and methods
Youll also likely want to customize a window using the windows fields
and scrolling windows (grids). Refer to Chapter 3, Programming Window
Fields, and Chapter 4, Programming Grids, for detailed information
about working with window fields and grids.

Working with windows in a VBA project

In order to use VBA with a Microsoft Dynamics GP window, youll first
need to add the window to your project. Adding a window creates a
corresponding window object in your project, which you can reference in
VBA.
Adding a window object

To add a window object to your project, switch to Microsoft Dynamics GP
and display the window you want to add. On the Tools menu, point to
Customize, then choose Add Current Window to Visual Basic. This will add
the currently-active (topmost) window to your project. The following
illustration shows this menu:
This item adds the active

window to your VBA
project.
Switch to the Visual Basic Editor and display the Project Explorer. It should
look similar to the following:
The Project Explorer displays

the window objects youve
added to the project. Objects
for third-party applications
appear in a separate project.
C H A P T E R 2 P R O G R A M M I N G W I N D O W S
You can continue to switch between the Visual Basic Editor and the main
application to add windows as needed throughout your projects
development. When viewed in the accounting system, each window youve
added to your project will appear with a period (.) at the end of the
windows title. This provides technical support and VBA developers with a
visual cue that the window is part of the VBA project.
Removing a window object

To remove a window object from your project, switch to Microsoft
Dynamics GP and display the window you want to remove. On the Tools
menu, point to Customize, then choose Remove Current Window From
Visual Basic. VBA will remove the window and any window fields
associated with the window.
Be sure you remove from your project all references to a window after youve
removed it.
Programming a window object

There are two primary ways you can write VBA code for a window object:
using a window event procedure, or referencing the window in procedures
throughout your project.
Using a window event procedure

A window event procedure executes VBA code when a user opens, closes
or activates a window in Microsoft Dynamics GP. This is useful for setting
default window field values when the window opens, or closing other
windows when the window closes. In the following example, an event
procedure sets default field values when the Invoice Entry window opens:
Private Sub Window_AfterOpen()

'Set the sort list to "by Date"
SortBy = 3
'Set the document type list to "Returns"
DocumentType = 2
End Sub
The following section, Using window events, explains each type of window
event you can use to execute VBA code. Windows also contain window
fields that you can reference and manipulate through VBA. Refer to
Chapter 3, Programming Window Fields, for more information about
using window fields.

Referencing the window object

After you create a window object in your project, any VBA code you write
in your VBA project has full access to the window object, its properties and
its methods. In the following example, a push button on a VBA form opens
a window using the windows Open method:
Private Sub OpenCustomerMaintenance_Click()

CustomerMaintenance.Open
End Sub
The section titled Using window properties and methods explains the methods
and properties available to procedures in your VBA project.
Using window events

Refer to Chapter 8, A window event executes a specific VBA procedure (an event procedure)
Window Object, for a when a user opens, closes or activates a window, or when a message dialog
detailed explanation appears for the window. To view the window events available, select a
and example of each Microsoft Dynamics GP window object in your project, then display the
window event Visual Basic Code window. Select Window in the Object list; window events
described here. will appear in the Procedure list.
Select Window in the

Object list.
When you choose an
event, the Code window
adds event procedure
syntax automatically.
Window events appear in
the Procedures list.
A window event executes an event procedure either before or after Microsoft

Dynamics GP application code runs for the same event. Therefore, window
events use names like BeforeClose to indicate that the event runs as the
window closes but before Microsoft Dynamics GP application code runs for
the window. When you choose an event, VBA automatically adds the event
procedure syntax to the Code window.
If you use VBA with a window youve modified using the Modifier, you
must set the EventMode property to emModified if you want events to
occur for the modified window. To change the EventMode property for the
window object, use the Visual Basic Properties window.
If you delete a modified window from your forms dictionary (or delete the forms
dictionary altogether), all VBA references to new fields you add to the modified
window will be invalid. If you re-create the modified window, then re-add the new
fields using the Modifier, youll need to re-add those same fields to your VBA
project and re-create any VBA customizations that reference the new fields.
Window open events

VBA window open events occur when the user opens the window, either
before or after the Microsoft Dynamics GP code for the window open event
runs. Microsoft Dynamics GP uses the window open event to set default
field values, such as a default document date or a sorting order.
BeforeOpen event
The BeforeOpen event occurs before the Microsoft Dynamics GP code runs
for the window open event. Its useful when you want to set default field
values in the window, while still allowing any Microsoft Dynamics GP
application code to override your defaults. In the following example, the
event procedure sets the Checkbook ID field when the Invoice Batch Entry
window opens. If this window displays an existing record when opened
(such as when opened from a zoom field), Microsoft Dynamics GP
application code overrides this value with the value stored with the record:
Private Sub Window_BeforeOpen(OpenVisible As Boolean)

'Set the checkbook ID
CheckbookID = "PETTY CASH"
End Sub
This event also includes the OpenVisible parameter. When set to False, this
specifies that the window should open invisibly.

AfterOpen event
The AfterOpen event occurs after the Microsoft Dynamics GP code runs for
the window open event. Its useful for overriding any default values that
were set for window fields. In the following example, the event procedure
marks both check box controls when the Sales Territory Maintenance
window opens. Since Microsoft Dynamics GP application code sets defaults
for these fields when the window opens, using the AfterOpen event
overrides the defaults:

'Set both check boxes when the window opens
MaintainHistory = 1
MaintainHistory1 = 1
End Sub
Window close events

VBA window close events occur when the user closes the window, either
before or after the Microsoft Dynamics GP code for the window close event
runs. Microsoft Dynamics GP uses the window close event to display a
modal dialog asking the user whether to save changes to the record.
BeforeClose event
The BeforeClose event occurs before Microsoft Dynamics GP application
code runs for the window close event. The primary use for this event is to
cancel the window close if the contents in the window dont meet certain
criteria. The following event procedure for the Invoice Entry window
checks whether the user entered a comment ID for the transaction, and
displays a message dialog. If the user clicks Yes, the procedure cancels the
close using the AbortClose parameter, and the user can enter a comment ID:
Private Sub Window_BeforeClose(AbortClose As Boolean)

Dim Response As Integer
If CommentID.Empty = True Then
'Display a message box
Response = MsgBox("Do you want to enter a Comment?", vbYesNo)
If Response = vbYes Then
'They want to enter a comment
AbortClose = True
CommentID.Focus
End If
End If
End Sub
AfterClose event
The AfterClose event occurs after the Microsoft Dynamics GP application
code runs for the window close event. The AfterClose event is a general-
purpose event you can use to perform any clean-up tasks, such as closing
other windows. For example, the following event procedure runs when the
Customer Maintenance window closes. It closes the Customers And
Prospects lookup window if its open (its IsLoaded property is True):
Private Sub Window_AfterClose()

If CustomersAndProspects.IsLoaded = True Then
CustomersAndProspects.Close
End If
End Sub
Window activate events

VBA window activate events occur when the user activates a window,
either by opening it or by making it the frontmost window.
The BeforeActivate event occurs before any Microsoft Dynamics GP

application code runs for the window activate event. The AfterActivate
event occurs after any Microsoft Dynamics GP application code runs for the
window activate event.
Microsoft Dynamics GP rarely executes application code during a window activate

event. Therefore, whether you choose the BeforeActivate or AfterActivate event
may be of little consequence.

Modal dialog events

A modal dialog is a specific type of window that requires the user to
perform some action in order to dismiss the dialog. The most common
modal dialog is an ask dialog, where message text and one or more buttons
appear in the window. A modal dialog appears in the following illustration:
PromptString
Control1String
Control2String Control3String
You apply a modal dialog event to a window in the same manner as other
window events. However, instead of occurring when the window opens,
closes or activates, the modal dialog event occurs for the window whenever
a modal dialog opens.
BeforeModalDialog event
The VBA BeforeModalDialog event occurs when Microsoft Dynamics GP
opens a modal dialog, but before its displayed. Since the dialog is open, but
not visible, this event allows you to dismiss the dialog by programmatically
answering it for the user. In the following example, if a user enters a non-
existent shipping method in the Customer Maintenance window, Microsoft
Dynamics GP displays an ask dialog asking whether the user wants to add
the shipping method. Normally the user must dismiss the dialog manually,
by clicking Add or Cancel. Instead, the event procedure automatically
answers this dialog and removes a step in the data entry process:
Private Sub Window_BeforeModalDialog(ByVal DlgType As Boolean, _

PromptString As String, Control1String As String, Control2String _
As String, Control3String As String, Answer As Long)
If PromptString = "Do you want add this Shipping Method?" Then
'Click the first button, the Add button
Answer = dcButton1
End If
End Sub
The PromptString parameter is the message text, which you can use to filter
which modal dialog you want to respond to. The Answer parameter uses
the constants dcButton1, dcButton2 and dcButton3. When indicated, these
click the first, second or third button in the dialog.
The BeforeModalDialog event is also useful for altering the contents of the
dialog before its displayed, including the modal dialogs message text and
button text. The following event procedure changes the message and button
text:
Private Sub Window_BeforeModalDialog(ByVal DlgType As Boolean, _

If PromptString = "Do you want to add this shipping method?" Then
'Change the message text
PromptString = "Create this shipping method?"
'Change "Add" button to "Create"
Control1String = "Create"
End If
End Sub
AfterModalDialog event
The VBA AfterModalDialog event occurs when Microsoft Dynamics GP
opens a modal dialog, but after the user dismisses it. This event allows you
to ascertain how the user responded to the dialog and perform any
additional tasks based on that response.
Refer to Chapter 6, The primary use for the AfterModalDialog event is to keep data in the
Storing Additional accounting system synchronized with data youve stored using the
Data, for more Dynamic User Object Store (DUOS). For instance, if youve created a DUOS
information about object that stores Internet address information for a customer, youll likely
using the Dynamic want to save it when the user saves the corresponding customer record.
User Object Store
(DUOS). In the following example, the user attempts to close a window without
saving a customer record. In this case, Microsoft Dynamics GP will display
a modal dialog asking if the user wants to save the record. If the user clicks
the modal dialogs Save button, the event procedure saves the
corresponding DUOS object:

Private Sub Window_AfterModalDialog(ByVal DlgType As Long, _

PromptString As String, Control1String As String, _
Control2String As String, Control3String As String, Answer As Long)
Dim Customers As DUOSObjects
Dim Customer As DUOSObject
Dim CustomerProperty As DUOSProperty
If PromptString = "Do you want to save changes to this " + _
"customer?" Then
'The user is trying to save the record using the save dialog.
If Answer = dcButton1 Then 'The user clicked Save.
Set Customers = DUOSObjectsGet("Customers")
Set Customer = Customers(CustomerID)
Customer.Properties("URL Address") = URLAddress
Customer.Properties("Contact E-Mail Address") = _
ContactEMailAddress
End If
End If
End Sub
Using window properties and methods

Refer to Chapter 8, The following table explains the available window methods and properties.
Window Object, for The remainder of this section explains some of the more common methods
detailed explanations and properties youll use when working with windows, as well as
and examples of the additional ways you can use windows.
window properties and
methods described Property/Method Description
here. Activate method Activates the window.
Caption property Specifies the windows title.
Close method Closes the window.
EventMode property Specifies whether window events occur for the
original or modified version of the window.
Height property Specifies the height of the windows client area (in
pixels). The client area is the window less the
windows title bar.
Hide method Hides an open window.
IsLoaded property Specifies whether the window is open (not necessarily
displayed).
Left property Specifies the horizontal position (in pixels) of the
window.
Move method Moves a window to a specified set of coordinates (in
pixels).
Property/Method Description
Name property Specifies the internal name VBA uses for the window.
Open method Opens a window.
PullFocus method Removes the focus from the window.
Show method Shows a window thats hidden using the Hide method.
Top property Specifies the vertical position of the window (in
pixels).
Visible property Specifies whether the window is visible.Width
propertySpecifies the width of the window (in pixels).
Required property Specifies whether the user entered data in all fields
whose Required property is True.
Opening and closing windows

You can open a Microsoft Dynamics GP window directly or indirectly
through VBA. To open and close it directly, use the window objects
Open method and Close method. The following event procedure opens the
Customer Maintenance window after the user logs in:

'The user logged in. Open the Customer Maintenance window.
CustomerMaintenance.Open
End Sub
The recommended method is to open a window indirectly, using VBA to

provide the navigation that displays the window, such as programmatically
clicking a lookup button that displays a lookup window:
Private Sub ShippingMethod_AfterGotFocus()

If ShippingMethod.Empty = True Then
'No shipping method specified. Click the lookup button
LookupButtons = 1
End If
End Sub
Microsoft Dynamics GP application code attached to navigational controls

(such as the lookup button) prepares the window to display data correctly.
Clicking these controls using VBA ensures that this processing occurs.

Working with forms

In Microsoft Dynamics GP, forms are a logical grouping of windows that
function together to perform a specific task. For instance, the Customer
Maintenance, Customer Account Maintenance and Customer Maintenance
Options windows are all part of the same form.
When you open a window, Microsoft Dynamics GP opens all windows in

the windows form invisibly, then displays the first window in the form (the
parent window). The child windows in the form remain invisible, but
loaded (their IsLoaded property is True).
If you open a forms child window through VBA, Microsoft Dynamics GP

displays the forms parent window as well as the child window. Any other
child windows remain loaded and invisible.
When you display a record in the parent window, Microsoft Dynamics GP

updates data in the invisible child windows so each contains data specific
to the current record. Since these child windows are loaded, you can
reference data in these fields using VBA.
For instance, when you open the Customer Maintenance window and
display a customer record, you can reference fields in the Customer
Maintenance Options window for that customer. In the following example,
the event procedure stops the user from saving a customer record in the
Customer Maintenance window if the user hasnt entered a currency ID in
the Customer Maintenance Options window:
Private Sub Save_BeforeUserChanged(KeepFocus As Boolean, _

CancelLogic As Boolean)
If CustomerMaintenanceOptions.CurrencyID.Empty = True Then
'Cancel the save
CancelLogic = True
'Prompt the user to enter a currency ID
MsgBox "You must enter a currency ID for this customer."
CustomerMaintenanceOptions.Visible = True
CustomerMaintenanceOptions.CurrencyID.Focus
End If
End Sub
Use the Modifiers Form Definition window to find out which windows are
part of a form.
Activating a window
The VBA Activate method activates a visible, open window, making it the
frontmost window, or expands it if its minimized. The Activate method
also causes the windows activate event to occur. In the following example,
the event procedure activates the Invoice Entry window after closing the
Invoice Batch Entry window:
If InvoiceEntry.Visible = True Then
InvoiceEntry.Activate
End If
End Sub
Hiding windows
The VBA Hide method hides a window youve opened, making it invisible.
The Visible property, when set to False, also makes a window invisible.
While invisible, the window is open (its IsLoaded property is True) and
data in the window is accessible.
Making a window invisible is useful if you need to reference data contained

in the window without necessarily displaying the window to the user. For
example, when the user enters a transaction amount in the Receivables
Transaction Entry window, the following event procedure compares the
amount with the maximum batch total in an invisible Receivables Batch
Entry window:
Private Sub SalesAmount_BeforeUserChanged(KeepFocus As Boolean, _

If BatchID.Empty = False Then
'The user selected a batch
'Click the expansion button to open the Batch Entry window
ExpansionButtons = 1
'Make the window invisible
ReceivablesBatchEntry.Visible = False
'Compare the batch total to the trx amount entered
If CCur(SalesAmount) >CCur(ReceivablesBatchEntry _
.BatchTotal) Then
MsgBox "Amount exceeds batch limit. Select another batch."
'Clear the batch ID field and move the focus there
BatchID.Empty = True
BatchID.Focus
End If
'Close the window
ReceivablesBatchEntry.Close
End If
End Sub

The Show method displays an invisible window. Setting the windows

Visible property to True also displays an open window. You can open a
window invisibly by setting the OpenVisible parameter of the windows
BeforeOpen event to False.
Moving and resizing a window

You can resize or reposition a window using the Height property,
Left property, Top property and Width property. Resizing and
repositioning a window is useful for organizing windows more efficiently
within the visible workspace. In the following example, the event
procedure runs before the Customer AddressMaintenance window opens.
The event procedure verifies the Customer Maintenance window is open,
then positions the Customer Address Maintenance window below and to
the right:

If CustomerMaintenance.Visible = True Then
'The Customer Maintenance window is open
CustomerAddressMaintenance.Left = CustomerMaintenance.Left + 25
CustomerAddressMaintenance.Top = CustomerMaintenance.Top + 100
End If
End Sub
Changing a window title

The Caption property allows you to set the windows caption (title). The
following example changes the title of the CustomerMaintenance window
when the window opens. It also changes the prompt for one of the fields in
the window.

'Change the title of the window
CustomerMaintenance.Caption = "Client Maintenance"
CustomerMaintenance.CustomerID.Caption = "Client ID"
End Sub
Using modified or original windows

You can choose whether window events occur for the modified or original
version of a window using the EventMode property. If you modify a
window using the Modifier, you can change the windows EventMode
property to emModifiedOnly. This allows VBA events to occur for the
modified window only.
If you make no modifications to the window using the Modifier, you can set
the EventMode property to emOriginalOnly. This allows VBA events to
occur for the original window only.
Renaming a window
The Name property allows you to change VBAs internal reference to a
window object. Note that this is not the same as the Caption property,
which allows you to change the windows title. If you change the windows
Name property using the Visual Basic Properties window, the name will
change in your project. You should then recompile your project to replace
any references to that window with the new name. Youll find it necessary
to rename a window if its name conflicts with other object names in your
project, such as reserved words in VBA.

Chapter 3: Programming Window Fields
Programming window fields using VBA involves adding a window or a
grid to your project, then adding selected field objects from that window or
grid. Programming window fields also involves determining which
window field events youll use to execute VBA code, and using window
field methods and properties to customize field display characteristics, or to
change business logic in a window. Information about programming
window fields is divided into the following sections:
Working with window fields in your VBA project

Programming a window field object
Using window field events
Got focus events
User changed events
Changed event
Lost focus events
Using window field properties and methods
Working with field values
Verifying field values
Window field type reference

Working with window fields in your VBA project

To use window fields with VBA, youll first need to add a window and its
window fields to your project.
Adding window fields to your project

To add window fields, switch to Microsoft Dynamics GP and display the
window. On the Tools menu, point to Customize, then choose Add Window
To Visual Basic. This adds the active (topmost) window to your project.
With the window displayed, point to Customize on the Tools menu and
choose Add Field To Visual Basic. This will activate field selection mode,
and a selection pointer will appear. The following illustration shows the
selection pointer:
Position the selection

pointer on the field (not
the prompt) and click.
Using the mouse, click on each data entry field, push button or list field
youll use in your project. Be sure to click on the field itself, and not the
fields prompt. When youve finished adding fields, point to Customize on
the Tools menu, and choose Add Fields to Visual Basic to deactivate field
selection mode.
Field selection mode also deactivates when you switch to the Visual Basic Editor.
Window fields youve added to a project wont appear in the Visual Basic
Project Explorer like a window, report or grid object. Instead, they will
appear in the Visual Basic Code window for a window object.
C H A P T E R 3 P R O G R A M M I N G W I N D O W F I E L D S
The following illustration shows window field objects for the Receivables
Customer Maintenance window object:
The windows fields

appear in the Code
window for the
window object.
At this point, you can write VBA code for the window field object using a
window field event, or you can reference the window field from other VBA
procedures in your project.
Removing window fields from your project

You cannot remove individual field objects from your project, only window
objects. When you remove a window object from your project, VBA also
removes the all window field objects associated with the window.
To remove a window object from your project, switch to Microsoft

Dynamics GP and display the window you want to remove. On the Tools
menu, point to Customize, then choose Remove Current Window From
Visual Basic. VBA will remove the window and any window fields
associated with it.

Programming a window field object

There are two primary ways you can write VBA code for a window field
object: using a window field event procedure, and referencing the window
field in procedures throughout your project.
Using window field event procedures

A window field event lets you execute VBA code when the user moves to,
changes or moves out of a specific field. This is useful when you want to
perform actions based on entries made in the field. The following section,
Using window field events, explains window field events in more detail.
Referencing the window field

To reference a windows fields, the field must be an object in your project,
and the fields window must be open (the windows IsLoaded property is
True).
If the field youre referencing is not in the current window, you must
reference the field using a qualified field name. A qualified name explicitly
specifies the location of the field youre referencing. In the following
example, an event procedure for a VBA user form opens the Invoice Batch
Entry window, then clicks a lookup button using the lookup button fields
qualified name:
Private Sub CommandButton1_Click()

'Open the batch entry window
InvoiceBatchEntry.Open
'Click the lookup button to display the lookup
InvoiceBatchEntry.LookupButton1 = 1
UserForm1.Hide
End Sub
Using window field events

Refer to Chapter 9, Window field events execute VBA procedures when a user moves to,
Field Object, for changes, or moves out of a window field, or a field youve added using the
more examples of Modifier. To view field events, choose a field object in the Code windows
window field events. Object list; all the window field events will appear in the Procedure list.
Select the window field

object in the Object list.
Event syntax appears
automatically when you
choose an event.
Window field events

appear in the
Procedure list.
When you choose an event, VBA automatically adds the event procedure
syntax to the Code window. You can then write the event procedure using
that event syntax.
There are four basic kinds of field events youll work with in VBA: got focus,
user changed, changed and lost focus. Each event occurs relative to when the
user moves the focus into a field (a got focus event), when the value of a field
changes (a user changed or changed event) or when the user moves the focus
out of a field (a lost focus event).
These events are useful when you want to respond to data the user enters in
a field by performing other operations in the window. For example, the
following AfterUserChanged event procedure runs when the user changes
information in the State field:
Private Sub State_AfterUserChanged()
If State = "NJ" Then
'Default the salesperson and territory
SalespersonID = "MARILYN H."
TerritoryID = "TERRITORY 4"
End If
End Sub

Field events also respond to actions performed by the user, such as clicking
a button. In the following example, a new button (OpenMSWord) added to
a window using the Modifier uses the AfterUserChanged event to open
Microsoft Word:
Private Sub OpenMSWord_AfterUserChanged()

Dim App As Word.Application
Set App = CreateObject("Word.Application")
App.Visible = True
End Sub
Each window field event you define occurs either before or after the
Microsoft Dynamics GP code for the field event runs. Therefore, field
events have names like BeforeUserChanged to indicate that the event
runs when the user changed the contents, but before the Microsoft Dynamics
GP application code runs.
Got focus events

VBA got focus events occur when the user initially enters a field, using the
TAB key or the mouse. You can use two VBA events, BeforeGotFocus and
AfterGotFocus, to execute VBA event procedures before and after the code
for the got focus event runs.
For information about The BeforeGotFocus, AfterGotFocus and BeforeUserChanged events are the
setting fields from a only three window field events where VBA allows you to set the value of the
field event procedure, current field (the field whose events are running).
refer to Setting field
values on page 50. The following illustration shows the progression of got focus events:
User moves the focus to the Name field:

1. VBA BeforeGotFocus event occurs for the Name field.
2. Microsoft Dynamics GP got focus event occurs.
3. VBA AfterGotFocus event occurs.
If Microsoft Dynamics GP runs application code during the got focus event,
it typically checks the value of the field thats gaining focus, and performs
calculations or sets other field values based on that value. However,
Microsoft Dynamics GP uses this event infrequently to do such operations.
BeforeGotFocus event
The BeforeGotFocus event occurs before the Microsoft Dynamics GP code
for the got focus event. Use this event to set or evaluate the contents of the
field gaining focus, and cancel any further got focus events from running
(the Microsoft Dynamics GP got focus event and the VBA AfterGotFocus
event). When set to True, the CancelLogic parameter will cancel the fields
other got focus events. In this example, the BeforeGotFocus event
procedure cancels the AfterGotFocus event for the Batch ID field (shown in
the description of the AfterGotFocus event below):
Private Sub BatchID_BeforeGotFocus(CancelLogic As Boolean)

If DocumentType = 7 Then
'The document type is a return. Dont use a batch
'Cancel the AfterGotFocus event, which opens the lookup
CancelLogic = True
MsgBox "Post returns individually, not in a batch."
DocumentDate.Focus
End If
End Sub
AfterGotFocus
The AfterGotFocus event occurs after the Microsoft Dynamics GP code runs
for the got focus event. Use this event to set or evaluate the contents of a
field gaining focus. In the following example, the AfterGotFocus event for
the Batch ID field checks whether the field is empty when the user moves to
it. If it is, the event procedure opens the batch lookup window:
Private Sub BatchID_AfterGotFocus()

If BatchID.Empty = True Then
'The field is empty. Click the lookup button
LookupButton3 = 1
End If
End Sub

User changed events

VBA user changed events occur when the user changes the contents of a
field, then moves the focus out of the field, using the TAB key or the mouse.
In fields that toggle, such as push buttons and visual switches, the user
changed event occurs when the user clicks the field. In list fields, the user
changed event occurs when the user selects an item in the list.
You can use two VBA events, BeforeUserChanged and AfterUserChanged,

to execute VBA events either before or after the Microsoft Dynamics GP code
for the user changed event runs.
For information about The BeforeGotFocus, AfterGotFocus and BeforeUserChanged events are the
setting fields from a only three window field events where VBA allows you to set the value of the
field event procedure, current field (the field whose events are running).
refer to Setting field
values on page 50. The following illustration shows the progression of user changed events in
an editable field:
User enters information in the Name field and presses the TAB key:
1. VBA BeforeUserChanged event occurs for the Name field.
2. Microsoft Dynamics GP user changed event occurs for the Name field.
3. VBA AfterUserChanged event occurs for the Name field.
Its common for Microsoft Dynamics GP to use the user changed event to
verify the contents of a field when the field changes; however, this isnt
done for all fields.
In fields that toggle, such as push buttons and visual switches, the user
changed event occurs when the user clicks the field. Microsoft Dynamics
GP always executes application code during the user changed event for
these fields.
User clicks the Save button:

1. VBA BeforeUserChanged event occurs for the button.
2. Microsoft Dynamics GP user changed event occurs for the button.
3. VBA AfterUserChanged event occurs for the button.
In list fields, such as button drop lists and list boxes, user changed events
occur when the user selects an item from the list, or presses the up arrow or
down arrow keys to move to a different list item.
User selects an item in the list:

1. VBA BeforeUserChanged event occurs
for the list.
2. Microsoft Dynamics GP user changed event
occurs for the list.
3. VBA AfterUserChanged event occurs for
the list.
BeforeUserChanged
The BeforeUserChanged event occurs before the Microsoft Dynamics GP
code runs for the user changed event. Use this event to evaluate the value of
the field and bypass, or cancel, any Microsoft Dynamics GP processing that
occurs for the same field.
Use caution when canceling Microsoft Dynamics GP processing for a fields user
changed event. Canceling the user changed event processing inhibits the
accounting systems ability to verify the contents of a field.
In the following example, the BeforeUserChanged event procedure runs

for the Invoice Entry windows Trade Discount field. Using the CancelLogic
parameter, it cancels processing for the Trade Discount field if the user
enters an amount greater than 4% of the invoice subtotal. It also uses the
KeepFocus parameter to place the focus in the same field, allowing the user
to enter a lower amount:
Private Sub TradeDiscount_BeforeUserChanged(KeepFocus As Boolean, _

If TradeDiscount > Subtotal * 0.04 Then
'The trade discount is greater than 4% of the subtotal
'Cancel the invoice calculation
CancelLogic = True
TradeDiscount.Value = Subtotal * 0.04
KeepFocus = True
MsgBox "You cannot enter a discount greater than 4% of " + _
"the subtotal."
End If
End Sub

AfterUserChanged
The AfterUserChanged event occurs after the Microsoft Dynamics GP code
for the user changed event runs. Use this event to evaluate information the
user entered in a field. The following example uses the AfterUserChanged
event to check the value of the Customer ID field in the Invoice Entry
window, then disable the Trade Discount field:
Private Sub CustomerID_AfterUserChanged()

If CustomerID = "ADVANCED0002" Then
'Don't offer a trade discount
TradeDiscount.Enable = False
End If
End Sub
Changed event
The VBA Changed field event always occurs for a field when its contents
change. This includes:
When the user changes the field directly

WhenMicrosoft Dynamics GP application code updates the window
field
When a fields value changes using an external tool, such as VBA
The most common situation to use the Changed event is when you want to
execute VBA code for window fields that Microsoft Dynamics GP updates.
This occurs most often when the accounting system retrieves a record from
a table, then displays the records contents in window fields. The
AfterUserChanged and BeforeUserChanged events wont occur for these
fields, since the application, not the user, changes the contents of the field.
Exercise caution when using the Changed event. In many cases, Microsoft
Dynamics GP may cause the Changed event to occur numerous times for the same
field even though the value of the field may not visibly change. This will execute the
associated VBA event procedure each time the event occurs.
For example, as the user browses through records in the Receivables

Transaction Entry window, Microsoft Dynamics GP sets window field
values for each record. The following Changed event procedure runs for
the Document Date field. Each time the user moves to a new record, it
checks the value of the document date, and displays a message if the
document is older than 30 days:
Private Sub DocumentDate_Changed()

Dim DaysOld As Integer
'Check the document date using the VBA Date function
If CDate(DocumentDate) < Date - 30 Then
'The document is at least 30 days old
DaysOld = Date - CDate(DocumentDate)
MsgBox "This document is " + Str(DaysOld) + " days old." + _
"Please post."
End If
End Sub
Lost focus events

VBA lost focus events occur when the user exits a field, using the TAB key or
the mouse, regardless of whether the fields contents changed. You can use
two VBA events, BeforeLostFocus and AfterLostFocus, to execute VBA
event procedures before and after the Microsoft Dynamics GP code for the
lost focus event runs.
The following illustration shows the progression of lost focus events:
User exits the Name field:

1. VBA BeforeLostFocus event occurs for the Name field.
2. Microsoft Dynamics GP lost focus event occurs.
3. VBA AfterLostFocus event occurs.
Microsoft Dynamics GP rarely uses the lost focus event. When it is used, it
typically locks control fields (fields that control the display of a record).
BeforeLostFocus
The BeforeLostFocus event occurs before the Microsoft Dynamics GP code
for the lost focus event. You can use the BeforeLostFocus event to cancel
any subsequent lost focus events for the field. When set to True, the
CancelLogic parameter cancels the Microsoft Dynamics GP lost focus and
VBA AfterLostFocus events.

The following BeforeLostFocus event procedure runs for the Document

Number field in the Receivables Transaction Entry window. This is a
control field, and normally the lost focus event locks this field. In this case,
the procedure cancels all other lost focus events, and the Document
Number field remains unlocked and editable:
Private Sub Number_BeforeLostFocus(KeepFocus As Boolean, _

CancelLogic = True
Description.Focus = True
End Sub
When set to True, the KeepFocus parameter allows you keep the focus in the
current field.
AfterLostFocus
The AfterLostFocus event occurs after the Microsoft Dynamics GP code
runs for the lost focus event. You can use the AfterLostFocus event to
evaluate the value of the field losing focus, and perform any additional
operations in the window. The following AfterLostFocus event procedure
checks whether the Payment Terms field is empty. If it is, the procedure
displays a VBA dialog that asks the if the user wants to enter a payment
term. If the user clicks Yes, the procedure opens the Payment Terms Lookup
window:
Private Sub PaymentTerms_AfterLostFocus()

If PaymentTerms.Empty = True Then
'Set a default payment term
Response = MsgBox("Do you want to enter a payment term?", _
vbYesNo)
LookupButtons = 1
End If
End If
End Sub
Using window field properties and methods

Refer to Chapter 9, The following table explains the available methods and properties for
Field Object, for window fields. The remainder of this section explains some of the more
detailed explanations common methods and properties youll use when working with window
and examples of each fields.
window field property
and method. Property/Method Description
Caption property Specifies the fields caption (prompt).
Empty property Specifies whether the field is empty.
Enabled property Specifies whether the field is enabled.
Focus method Moves the focus to a field.
FocusSeg method Moves the focus to a segment in a composite.
Height property Specifies the height of the field (in pixels).
Left property Specifies the horizontal position of a field (in pixels).
Locked property Specifies whether the current field is locked.
Move method Moves the field to a specified set of coordinates within the
window's client area.
Name property Specifies the internal name VBA uses to reference the field.
Object property Returns a field object without the standard properties and
methods extended to it by Visual Basic.
Parent property Returns a window or report object containing a specified field
object.
Required property Specifies whether the field requires data for the window to
save the record properly.
TabStop property Specifies whether the field is in the windows tab sequence.
Top property Specifies the vertical position of a field (in pixels).
Value property Specifies the value of a field.
ValueSeg method Specifies the value of a segment in a composite field.
Visible property Specifies whether the field is visible.
Width property Specifies the width (in pixels) of the field.
Disabling and locking fields

The Enabled property and Locked property allow you to make a field
read-only and inaccessible to the user. To disable a field, set the Enabled
property to False. A disabled field will appear dimmed, and any related
controls (such as lookup or expansion buttons) will be inaccessible. To lock
a field, set its Locked property to True. A locked field will appear with a
gray background, and its related controls will still be accessible.

In the following example, an event procedure for the Account Maintenance

window disables the Delete button and locks the Account Number field:

If UserInfoGet.UserID = "LESSONUSER1" Then
Delete.Enabled = False 'Disable the Delete button
Account.Locked = True 'Lock the account number
End If
End Sub
In this case, the user can browse information in the window, but not create
new account records or delete existing ones.
You can use VBA to set the value of a field youve locked or disabled using
VBA. However, you cannot set the value of a field locked or disabled by
Microsoft Dynamics GP, nor can you unlock or enable these fields.
Microsoft Dynamics GP disables fields when they dont apply in a given
situation, and lock fields to preserve the integrity of accounting data (such
as document totals).
Controlling the focus

The Focus method and FocusSeg method let you control the movement of
the focus in a window.
The Focus method moves the focus to a specified field. This will also
activate the fields BeforeGotFocus and AfterGotFocus events. In the
following example, the Focus method moves the focus to the Check field if
the current customer uses Check as the payment term:
Private Sub Tax_AfterLostFocus()

If PaymentTerms = "Check" Then
'The customer pays with checks. Move to the Check field
Check.Focus
End If
End Sub
The FocusSeg method moves the focus between segments in a composite.

This method uses an index corresponding to the segment you want the
focus to move to. The following example uses both the ValueSeg property
and FocusSeg method to set a default value for an account number field:
Private Sub CashAccount_AfterGotFocus()

If CheckbookID = "PAYROLL" Then
'Default payroll account segments
CashAccount.ValueSeg(1) = "100"
'Move the focus to the third segment
CashAccount.FocusSeg(3)
End If
End Sub
When working with windows, you cannot move the focus using the
windows BeforeOpen event. Since the window isnt open yet, theres no
place for the focus to be placed. You can, however, move the focus using the
windows AfterOpen event.
Showing and hiding fields

The Visible property allows you to show and hide fields in a window. To
hide a field, set the Visible property to False; the field and its caption will
still be in the window, but wont be visible to the user.
The following example hides sales fields when a given user opens the
Salesperson Maintenance window:

CommissionedSales.Visible = False
CostofSales.Visible = False
NonCommissionedSales.Visible = False
TotalCommissions.Visible = False
End If
End Sub
You can still return or set the values of fields you make invisible with VBA.
However, you cannot set the value of fields hidden by Microsoft Dynamics
GP, nor can you show these fields.

Renaming fields
The Name property allows you to change the name you use in VBA code to
reference the field. Note that this is not the same as the Caption property,
which allows you to change the fields caption. You can change a fields
name using the Visual Basic Properties window, and the name will change
in your project. You should then recompile your project to replace any
references to that field with the new name.
Youll find it necessary to rename fields if the fields name conflicts with a
reserved word in VBA. For example, the Date field has the same name as a
reserved word in VBA. You may also want to rename fields to make code
more readable.
Making fields required

The Required property specifies whether the field must contain data before
the user can save information in the window. To make a field required, set
its Required property to True. The following example sets fields in the
Customer Maintenance window to required:

Name.Required = True
ShortName.Required = False
StatementName.Required = True
End Sub
Microsoft Dynamics GP will prompt the user to enter data in a required

field if the field is empty when the user attempts to save the record. Fields
marked as required by VBA are displayed with the same caption styles as
fields marked as required by the accounting system.
You cannot set the Required property to False for fields already marked as
required by Microsoft Dynamics GP. These are fields necessary for the
accounting system to store the record properly.
Working with field values

The section Window You return and set window field values using the Value property. If your
field type reference on code specifies the field name, but omits the Value property, VBA assumes
page 54 explains how youre returning or setting the value of the field. The following example
to work with specific explicitly uses the Value property:
field types using VBA.
BatchID.Value = "DEBITMEMOS"
The same code can also omit the Value property and have the same effect:
BatchID = "DEBITMEMOS"
The majority of the examples in this manual use the abbreviated form of
this syntax. You can choose to use or ignore the Value property in your
own project.
Using the ValueSeg property

The ValueSeg property specifies the value of a given segment in a
composite field (typically, an account number field). This is useful when
you want to evaluate only a single segment of the composite. The
Value property can evaluate the value of the entire composite, but not a
single segment.
In the following example, if 600 is entered as the first segment in the Cash
Account field, the event procedure locks the maximum amount for checks
with this account:
Private Sub CashAccount_AfterLostFocus()

If CashAccount.ValueSeg(1) = "600" Then
'This is an expense account
'Set the maximum payables amount for this account
Amount = "1000.00"
Amount.Locked = True
End If
End Sub

You can also use the ValueSeg property to set individual segments in a
composite. However, theres little difference in using the Value and
ValueSeg properties to do this. In the following example, the ValueSeg
property is used to set the first and second segments in the Account field.
Private Sub Account_AfterGotFocus()

'Set the second segment
End Sub
The following event procedure has the same effect, but uses the Value
property to set the composites value:
Private Sub Account_AfterGotFocus()

CashAccount.Value = "100-1100"
CashAccount.FocusSeg (3)
End Sub
Using the Empty property

The Empty property specifies whether a fields value is empty. If you set a
fields Empty property to True, VBA clears the field. Using the Empty
property in this manner is the same as setting the fields Value property to
a null value (""). The following example uses the Empty property to
automatically open a lookup window if the Salesperson ID field is empty:
Private Sub SalespersonID_AfterGotFocus()

If SalespersonID.Empty = True Then
'Click the lookup button to display the lookup window
LookupButton8 = 1
End If
End Sub
Returning field values

You can use the Value property to return window fields value, providing
the window that contains the field is open (the windows
IsLoaded property is True). If the window is open but invisible, you can
return field values from that window. If youve disabled, locked or hidden
the field using VBA, you can still return the fields value. If Microsoft
Dynamics GP hides the field, you cannot return the fields value.
VBA returns all field values as strings. For instance, VBA returns the values
of a currency field as $30.75, a date field as 5/1/00, and an integer field
as 100.
Performing numeric calculations

Since all field values returned to VBA are strings, numeric calculations or
comparisons wont function properly unless you convert string values to
the appropriate numeric data type first.
For example, if you compare two integer fields, Quantity1 (value of 70), and
Quantity2 (value of 100), VBA compares the string values of those fields,
not their integer values. VBA uses alphanumeric precedence in comparing
strings, and compares the 7 in 70 to the 1 in 100. Since 7 is greater
than 1, the expression results in 70 being the larger value, which is
incorrect:
If Quantity1 > Quantity2 Then
'Quantity1 (70) in this case is greater than Quantity2 (100)
To avoid this problem, you must convert these values using VBAs numeric
conversion functions prior to performing the comparison. In the following
example, VBAs CInt() function converts the ItemQuantity1 and
ItemQuantity2 fields, resulting in a correct comparison:
If CInt(Quantity1) > CInt(Quantity2) Then

'Quantity1 (70) is now less than Quantity2 (100)
Likewise, when performing a calculation using a Microsoft Dynamics GP

value and a VBA value, you must convert the value from the accounting
system before performing the calculation. For example, to calculate the
number of days between a Microsoft Dynamics GP date value (Document
Date) and the current system date returned using the VBA Date function,
convert the Microsoft Dynamics GP date using the CDate() function:
"Please post."
End If
End Sub

The following table shows the VBA functions available for converting
string values to a specific data type:
Function Description
CInt() Converts a Microsoft Dynamics GP string value to an integer.
CDate() Converts a Microsoft Dynamics GP string value to a date.
CCur() Converts a Microsoft Dynamics GP string value to a currency.
CLng() Converts a Microsoft Dynamics GP string value to a long integer.
Setting field values

The following section, You can use the Value property to set a fields value for any field in a
Window field type Microsoft Dynamics GP window, providing the window that contains the
reference, explains the field is open (the windows IsLoaded property is True). If the window is
values you can set for open but invisible, you can set field values from that window. If youve
each field type. disabled, locked or hidden the field using VBA, you can still set the fields
value. If the accounting system disables, locks or hides the field, you cannot
set the fields value.
Each type of field accepts specific values from VBA. For setting data entry
fields, such as string, date and currency fields, you typically use a string
value from VBA:
'Set a the Batch ID string field

'Set the Document Date field
DocumentDate = "02/07/97"
'Set the Discount Amount currency field
DiscountAmount = "120.95"
Other fields, such as list fields, check boxes, push buttons and radio
buttons, accept numeric values:
'Set the Document Type drop-down list to item 2

DocumentType = 2
'Mark the Hold check box
Hold = 1
'Push the Save button
Save = 1
'Select the first option in the Posting Type radio button group
PostingType = 0
Verifying field values

Microsoft Dynamics GP verifies data entered in many fields to check
whether the data is valid. When you enter data in a field manually,
verification takes place in the Microsoft Dynamics GP user changed event
(when the user enters the data, then moves out of the field).
When you set the value of a field using VBA, this verification will still
occur, but has different results depending on whether you set the field from
inside the field, or outside the field. The following sections describe
data verification issues in more detail.
Setting a value from inside the field

If you set a value from inside a field (after the field gains focus), using the
fields BeforeGotFocus, AfterGotFocus, or BeforeUserChanged events,
Microsoft Dynamics GP field verification can perform normally. This is the
recommended method for setting a field value, since it most closely
matches how the user enters data, and how the accounting system verifies
that data. The following illustration shows the progression of events when
setting a value from inside the field:
Field event order:

1. VBA BeforeGotFocus Use these events to
2. VBA AfterGotFocus set the field value.
3. VBA BeforeUserChanged
The accounting system
4. Microsoft Dynamics GP user
changed
5. VBA AfterUserChanged
6. VBA Changed
7. VBA BeforeLostFocus Use these events to
8. VBA AfterLostFocus read or reverify the field
In the following example, the AfterGotFocus event procedure for the

Shipping Method field sets the value of the Shipping Method field:

ShippingMethod = "NEW"
End If
End Sub

When the user moves out of the Shipping Method field, the Microsoft
Dynamics GP code for the user changed event checks whether the fields
data is valid. In this case, it will make sure NEW is an existing shipping
method. Since this is a new shipping method, a dialog will appear asking
whether the user wants to add it.
You cannot set the fields value using events that follow the Microsoft Dynamics
GP user changed event (AfterUserChanged, AfterLostFocus or
BeforeLostFocus events). Microsoft Dynamics GP doesnt have the opportunity
to verify values set in these events, and a VBA error will occur. You can use these
events to read the value of the field.
Setting a value from outside the field

If you set a fields value from outside the field (before the field gains
focus), such as by using the windows BeforeOpen or AfterOpen event, or
another fields BeforeUserChanged or AfterUserChanged event, VBA
automatically runs the Microsoft Dynamics GP user changed event for the
field youre setting. This is necessary so the application code associated
with these events can verify the fields value.
For many fields, Microsoft Dynamics GP does little or no field verification,

and setting the fields value from outside the field using VBA will not
generate errors. However, Microsoft Dynamics GP will perform verification
for fields that affect business logic (such as an invoice discount percent, or a
tax amount) or for add-on-the-fly fields. Typically, these are fields that
generate Microsoft Dynamics GP alert dialogs when you enter invalid data,
indicating that the value entered is incorrect. If the field is an add-on-the-fly
field, a dialog typically appears asking whether you want to add a new
record.
If you set a field value from outside the field using VBA, and Microsoft
Dynamics GP determines that its value is invalid, the accounting system
will first display its alert dialog. This will be followed by a VBA error
dialog, shown in the following illustration.
Refer to Appendix A, The VBA error occurs because the accounting system attempts to place the
VBA Errors, for an focus in the field and restore the fields previous value. Since the current
explanation of each field does not have focus, Microsoft Dynamics GP cannot place the focus
VBA error you may and the VBA error results.
encounter.
This type of error will commonly occur when you set an add-on-the-fly
field to a new value from outside the field. The following AfterOpen
event procedure for the Receivables Transaction Entry window sets the
value of an add-on-the-fly field (Shipping Method):
Private Sub ReceivablesTransactionEntry_AfterOpen()

'Set the Shipping Method field to a value that doesn't exist.
End Sub
In this case, the accounting system will display a dialog asking whether you
want to add the new shipping method. When you dismiss the dialog, VBA
generates an error, since the system cannot place the focus in the Shipping
Method field.
There are two ways to avoid this type of error:
Whenever possible, set a fields value from inside the field, after its
gained focus, using the fields AfterGotFocus or BeforeGotFocus field
event. If your event procedure sets an invalid value, the accounting sys-
tem will still display a dialog, but VBA wont generate the error:

End Sub
If you set the value outside the field, before the field has gained
focus, use the Focus method with the setvalue parameter in your event
procedure. The Focus method moves the focus to the field, then sets its
value to the setvalue:

'Move the focus to the field, then set the value
ShippingMethod.Focus("NEW")
End Sub

Window field type reference

This section describes the common window field type in Microsoft
Dynamics GP, as well as those you can create using the Modifier.
Finding additional field information

Use the Resource Descriptions tool for locating additional information
about a Microsoft Dynamics GP field. To access this tool, switch to
Microsoft Dynamics GP window. On the Tools menu, point to Resource
Descriptions, then choose Fields. Choose the field you want additional
information for, then click Field Info.
This information can help you understand the type of field youre working
with (string, integer, list box) as well as the fields keyable length, the
format applied to the field, and any static values applied to the field.
Field list
The fields described are listed below. Detailed explanations of each follow.
Button drop list

Check box
Combo box
Composite
Currency
Date
Drop-down list
Integer
List box
Multi-select list box
Push button
Radio button
String
Text
Visual switch
Button drop list
Description A button drop list allows a user to select one item from the list. The
following illustration shows a button drop list.
Button drop list
List items
Events The BeforeUserChanged and AfterUserChanged events occur when the

user selects an item from the list. The BeforeGotFocus and AfterGotFocus
events occur as the user presses the button. The BeforeLostFocus and
AfterLostFocus events occur when the button returns to its unpressed
state. Setting the value of a button drop list through VBA runs the lists
Changed event.
VBA usage VBA uses a numeric value (1 to n) when referencing an item in a button
drop list. In most cases, the value corresponds to the order of the selected
item in the list. You cannot reference the name of an item in the list, nor can
you rearrange, remove or add items to a button drop list using VBA.
Comments In certain instances, the position of an item in a button drop list doesnt
necessarily to its numeric value. This is especially true if the list is sorted in
alphanumeric order. To determine the correct value, select the item in the
list, then view the fields Value property using the Visual Basic Editors
Property sheet.
Example The following event procedure chooses the first item in the Write Letters
button drop list in the Customer Maintenance window.
Private Sub PrintCollections_Click()

'Print a collections letter
CustomerMaintenance.coWriteLettersBDL = 1
End Sub

Check box
Description A check box allows the user to mark or unmark an item. The following
illustration shows a check box.
Check box caption
Events All VBA field events function for a focusable check box field.
VBA usage VBA uses numeric values when referencing a check box field. If 1, the check
box is marked; if 0, the check box is unmarked.
Comments You can change a check box caption using the Caption property. For two or
more check boxes linked to a single caption (such as the Calendar Year and
Fiscal Year check boxes linked to the Maintain History caption), you can
change only the check box group caption, not the captions for individual
check boxes.
Example The following event procedure runs when the Sales Territory Maintenance
window opens. It marks the first check box (Calendar Year) in the Maintain
History group, and unmarks the second check box (Fiscal Year):

'Mark this check box when the window opens
MaintainHistory = 1
'Unmark this check box when the window opens
End Sub
Combo box
Description A combo box allows the user to enter a text item or choose one from the
combo box list. The following illustration shows a combo box.
Caption
Combo box list items
Events The BeforeUserChanged and AfterUserChanged events run each time the
user selects an item in the combo box list, or presses the up arrow or down
arrow key to move to a different list item. All other VBA field events
function normally for a focusable combo box field.
VBA usage VBA uses string values for each item in a combo box. When you set the
value of a combo box, VBA sets the value to the combo box field. If the
value doesnt exist in the item list, VBA wont add it to the list. However,
Microsoft Dynamics GP application code typically asks the user if they
want to save a new item in the combo box field when the user dismisses the
window.
Example The following event procedure checks the value of the Budget Year combo
box field in the Budget Maintenance window, then enables or disables the
Display radio group:
Private Sub BudgetYear_AfterUserChanged()

'Check the Budget Year combo box
If BudgetYear = "2004" Then
'Disable the Display radio group
Display.Enabled = False
Else
Display.Enabled = True
End If
End Sub

Composite
Description A composite field displays information from multiple fields called

segments. Microsoft Dynamics GP primarily uses composite fields for
account numbers. The following illustration shows a composite field.
Composite field
Segment
Events The BeforeUserChanged and AfterUserChanged events occur for the

composite field when the user changes information in any segment, then
moves the focus out of the composite. No events occur when the user
changes the value of a segment, then moves to another segment in the same
composite. All other VBA field events occur when you move the focus into
or out of the composite.
VBA usage You can return the value of a composite using either the Value property or
the ValueSeg property. If you use the Value property, VBA returns a
formatted string value. If you use the ValueSeg property, VBA returns the
unformatted value of the segment you specify.
You can also set the value of a composite using either the Value property or
the ValueSeg property. Use the Value property to set the value of the entire
composite, including any formatting characters, such as dashes. Use the
ValueSeg property to set the value of individual segments of the composite,
without including any formatting. Use the FocusSeg method to move the
focus between segments of a composite field.
Examples The following example uses the Value property to set the Cash Account
composite field to an existing account number:
Private Sub CheckbookID_AfterUserChanged()

If CheckbookID = "FIRST NATIONAL" And CashAccount.Enabled _
= True Then
CashAccount = "100-5100-00"
CashAccount.Enabled = False
Else
CashAccount.Enabled = True
End If
End Sub
The following event procedure uses the ValueSeg property to set the
default value of the first segment in the Cash Account composite field. It
then uses the FocusSeg method to place the focus on the second segment in
the composite:

End Sub

Currency
Description A currency field displays a value as a currency amount. The following

illustration shows a currency field.
Caption
Currency field
Events All VBA field events function for a focusable currency field.
VBA usage VBA uses a formatted string value when referencing a currency field. The
value can have a maximum of 14 characters to the left of a decimal
separator and 5 to the right.
When you set a currency value, specify the location of the decimal
separator; the accounting system automatically provides all other
formatting. When you return a currency value, VBA returns the formatted
string value that appears in the window, including the currency symbol,
thousands separator and the decimal separator.
Example The following VBA code defaults the value of a currency field to a fixed
amount in the Checkbook Maintenance window:

If NextCheckNumber = 1 Then
'This is a new checkbook.
'Set the max check amount to $2,000.00
Amount = "2000.00"
End If
End Sub
Date
Description A date field displays a date, in a format specified by your operating system
settings for date and time. The following illustration shows a date field.
Caption
Date field
Events All VBA field events function for a focusable date field.
VBA usage VBA uses a formatted string value when referencing a date field. When you
set a date value, the text value must match the operating system settings for
date and time, such as 12/31/96 (using MM/DD/YY format) or
31-12-96 (using DD-MM-YY format).
Examples In the following example, VBA code sets the value of a date field to a fixed
string value:

PostingDate = "07/28/97"
End Sub
In the following example, VBA code combines a string with a date field to
construct a new batch ID in the Invoice Entry window:
Private Sub DocumentType_AfterGotFocus()

'The user selected returns
'Place the focus in the Batch ID field and set the value
BatchID.Focus("RET-" + Str(UserInfoGet.UserDate))
'Constructs "RET-07/28/97" as the batch ID
End If
End Sub

Drop-down list
Description A drop-down list field expands to show a list of items, then collapses to
show only the selected item. The following illustration shows a drop-down
list.
Caption
Drop-down list items
user selects an item in the drop-down list, or presses the up arrow or down
arrow key to move to a different list item. All other VBA field events
function normally for a focusable drop-down list field.
VBA usage VBA uses a numeric value (1 to n) when referencing items in a drop-down
list. In most cases, the value corresponds to the position of the item in the
list. You cannot reference the name of the item in the list, nor can you
rearrange, remove or add items to a drop-down list using VBA.
Comments In certain instances, the position of an item in a drop-down list doesnt

necessarily correspond to its numeric value. This is especially true if the list
is sorted in alphanumeric order. To determine the correct value, select the
item in the list, then view the fields Value property using the Visual Basic
Editors Property sheet.
Example In the following example, an event procedure sets the default position of
the sort list and the Document Type drop-down list fields in the Receivables
Transaction Entry window:

SortBy = 4 'Sets the sort list to "By Batch ID"
DocumentType = 7 'Sets the Document Type to "Returns"
End Sub
Integer
Description An integer field displays a number between -32,768 and 32,767. The
following illustration shows an integer field.
Caption
Integer field
Events All VBA events function for a focusable integer field.
VBA usage VBA uses a string value when referencing an integer field. If the integer
field includes a format (such as a percent field), VBA returns the formatted
string value, including the decimal separator and percent sign (such as
3.15%). To set the value of a formatted integer field, only include the
decimal separator (3.15). The accounting system adds any other
formatting characteristics.
Examples In the following example, VBA code sets the Transaction Total integer field
to 50 when the user enters a new batch in the Sales Batch Entry window:
Private Sub BatchID_AfterUserChanged()

If Origin = 0 Then
'No batch origin specified. This is a new batch.
TransactionTotal = "50"
End If
End Sub
This example sets an integer field (Percent) thats formatted with two
decimal places. It calculates a new commission percent based on
commissioned sales:
Private Sub CommissionedSales_BeforeUserChanged(KeepFocus _

As Boolean, CancelLogic As Boolean)
If CCur(CommissionedSales) + CCur(NonCommissionedSales) > _
200000 Then
Percent = "4.50" 'Set the percent to 4.50%
Else
Percent = "3.00" 'Set the percent to 3.00%
End If
End Sub

List box
Description A list box displays up to 32,767 items in a list, one of which the user can
select. The following illustration shows a list box.
Caption
List box field
user selects an item in the list box, or presses the up arrow or down arrow
key to move to a different list item. All other VBA field events function
normally for a focusable list box field.
VBA usage VBA uses a numeric value (1 to n) when referencing list box fields. In most
cases, the value corresponds to the position of an item in the list. You cannot
reference the name of the item in the list, nor can you rearrange, remove or
add items to a list box using VBA.
Comments In certain instances, the position of an item in a list box doesnt necessarily
correspond to its numeric value. This is especially true if the list is sorted in
alphanumeric order. To determine the correct value, select the item in the
list, then view the fields Value property using the Visual Basic Editors
Property sheet.
Example The following example sets the default selection in the Currencies list box
when the Multicurrency Access Setup window opens:

Currencies = 8
'Selects Z-US$
End Sub
Multi-select list box
Description A multi-select list box displays up to 32 items in a list, from which the user
can choose multiple items. The following illustration shows a multi-select
list box.
Caption
Multi-select list box field
user selects an item in the multi-select list box, or presses the up arrow or
down arrow keys to move to a different list item. All other VBA field events
function normally for a focusable multi-select list box field.
VBA usage VBA uses a 32-bit numeric value when referencing the items selected in a
multi-select list box. The numeric value takes into account both the number
of items selected and their position in the list. The following table shows the
position of an item in a multi-select list box, the items corresponding
numeric value, and the calculation that derives the value:
List item Numeric value Calculated as...

1 1 20
2 2 21
3 4 22
4 8 23
31 1,073,741,824 230
The value of the list is the sum of the selected items numeric values. If you
select items 1, 3 and 4, the value of the multi-select list box is 13 (total = 1 +
4 + 8). An easier way to determine the value of the list is to select multiple
items, then view the fields Value property in the Visual Basic Properties
window.

Examples To select a single item in a multi-select list box, set the multi-select list boxs
value to the items numeric value (noted in the previous table). The
following example selects list item 4 by setting the list boxs value to 8:

'Select Payroll in the list
IncludeinLookup = 8
End Sub
To select multiple items in a multi-select list box, add the list items numeric
values together. The following example selects list items 1, 3 and 4 by
setting the field to the sum of the items integer values (1 + 4 + 8 = 13):

'Select Sales, Purchasing and Payroll
IncludeinLookup = 13
End Sub
Push button
Description A push button performs actions, such as executing Microsoft Dynamics GP

application code or VBA code. The following illustration shows a push
button.
Push button
Events The BeforeUserChanged and AfterUserChanged events occur when the

user clicks a push button. The Changed event occurs when you set a push
button using VBA. No other VBA field events occur for push button fields.
VBA usage VBA uses numeric values when referencing push buttons. The value
indicates the state of the push button. The up, or normal state of the
button is 0; the down, or pushed state is 1. Setting the buttons value to 1
in effect pushes the button, and performs the same operation as if the
user clicked the button.
Comments You can change a text push buttons caption using the Caption property.
Examples The following example displays a lookup window when the user moves to
the Batch ID field and the field is empty. To display the lookup window, the
procedure sets the lookup button field to 1:

'The field is empty. Press the lookup button.
LookupButton3 = 1
End If
End Sub

Radio button
Description A radio button field appears within a radio button group. You can select
only one button in the group. The following illustration shows a radio
button group.
Radio button group

caption
Radio button group
Radio button field
Events When you select a radio button in a radio button group, the
BeforeUserChanged and AfterUserChanged events occur for the entire
group. All other VBA field events occur for the entire radio button group, as
you move the focus to and from the group.
VBA usage VBA uses numeric values when referencing a radio button group. The
numeric value indicates the selected radio button in the group and
corresponds to the order each radio button appears in the tab sequence,
starting with 0 for the first field in the sequence. In the Typical Balance
radio button group pictured above, the Debit field is 0 and the Credit field
is 1.
Comments You can change the radio button groups caption using the
Caption property. You cannot change the captions for individual radio
buttons.
Example The following example selects the Code radio button control in the Method
Of Entry radio button group when the window opens:
Private Sub Window_BeforeOpen

'Set the Code radio button
MethodofEntry = 1
End Sub
String
Description A string field allows you to enter and view up to 255 text characters. The
following illustration shows a string field.
Caption
String field
Events All VBA field events function for a focusable string field.
VBA usage VBA uses a string value when referencing string fields. If you set the value
of a string field that uses a format (such as a phone number field), include
all formatting characters, including parentheses, static text, dashes and
spaces. When you return the value of a formatted string value, VBA returns
the formatted string value.
Example The following example sets the value of the Batch ID string field when the
user chooses a document type from the Document Type drop-down list in
the Receivables Transaction Entry window:
Private Sub DocumentType_AfterUserChanged()

Select Case DocumentType
'Move the focus to the Batch ID field and set the value
Case 1
BatchID.Focus("DAILYSLS")
Case 7
BatchID.Focus("DAILYRET")
Case Else
BatchID.Focus("DAILYMISC")
End Select
End Sub
In the following example, the procedure sets the value of the Phone 1 field
using a formatted string:
Private Sub CustomerID_Changed()

If CustomerID = "AARONFIT0001" Then
Phone1 = "(701) 555-7890 Ext. 1234"
End If
End Sub

Text
Description A text field displays up to 32,000 text characters. The following illustration
shows a text field.
Text field
Events All VBA field events function for a focusable text field.
VBA usage VBA uses a string value when referencing a text field. The string value
cannot exceed 32,000 characters.
Comments Microsoft Dynamics GP uses text fields primarily in Note windows.
Example The following example adds a note to an Invoice record when the customer
purchases over $2,000. The message added to the text field in the Note
window explains that the customer received a 4% trade discount:
Private Sub TradeDiscount_AfterGotFocus()

If Subtotal >= 2000 And TradeDiscount = 0 Then
'Click the note button to open the Note window
NoteAbsentButtonWindowArea = 2
'Add a message to the text field
Note.TextField = "Customer " + Name1 + " purchased " + _
"over $2,000. The trade discount for Customer " + Name1 + _
" was calculated and applied at 4%."
'Click the Attach button to save the note
Note.Attach = 2
'Set the trade discount to 4% of the subtotal
InvoiceEntry.TradeDiscount = Subtotal * 0.04
End If
End Sub
Visual switch
Description A visual switch displays a series of text or picture items. Clicking the field
displays the next item in the series. The following illustration shows a
visual switch field.
user selects an item a visual switch. All other VBA field events function
normally for a focusable visual switch field.
VBA usage VBA uses numeric values when referencing visual switch fields. The
numeric value corresponds to the currently-displayed item in the series,
starting with 1 and incremented by 1. For a visual switch with two pictures
in the series, the first picture in the list has a value of 1 and the second has a
value of 2.
Example The following example expands the scrolling window in the Invoice Entry
window when the window initially opens:

ScrollingWindowExpandButton2 = 2
End Sub

Chapter 4: Programming Grids
VBA refers to Microsoft Dynamics GP scrolling windows as grids.
Programming grids involves adding a grid to your project, determining
which grid events youll use to execute application code, and working with
the window fields that appear in the grid.
Information about grids is divided into the following sections:
Working with grids in your VBA project

Programming a grid object
Types of grids
Using grid events
Using grid properties and methods

Working with grids in your VBA project

Grids display multiple lines of data. Each line in a grid corresponds to one
record in a Microsoft Dynamics GP table. Conversely, a Microsoft Dynamics
GP window displays only a single record at a time. Since the functionality
provided by a window is quite different from that provided by a grid, VBA
references a window and a grid that appears in it as separate objects.
The grid and the window

that contains it are
separate objects in your
VBA project.
A grid displays multiple

lines of data.
Its also important to note that Microsoft Dynamics GP grids do not

function like traditional grids in VBA. You can reference fields on only the
current line in a Microsoft Dynamics GP grid, and grid events occur only
for the current line. VBA grids typically allow you to work with specified
rows and cells within the grid.
When you expand a grid, each line displays two or more rows of data for
each record. You expand and shrink a grid using the expand and shrink
buttons.
When you expand a grid,

each line displays
multiple rows.
C H A P T E R 4 P R O G R A M M I N G G R I D S
Adding a grid object

When you add a window containing a grid to your project, VBA adds both
the window and the grid. Although the two work together to display
information in the accounting system, they are independent objects in your
VBA project.
To add a grid object to your project, switch to Microsoft Dynamics GP and

display the window containing the grid you want to add. On the Tools
menu, point to Customize, then choose Add Current Window To Visual
Basic. This will automatically add the currently active (topmost) window
and the windows grid to your project.
When you switch back to Visual Basic, the Project Explorer will display
both the grid and window object.
VBA adds the grid object

and its window to the
project at the same time.
Removing a grid object

To remove a grid object from your project, switch to Microsoft Dynamics
GP and display the window containing the grid you want to remove. On
the Tools menu, point to Customize, then choose Remove Current Window
From Visual Basic. VBA will remove the window and grid object, as well as
any window field objects associated with the window and grid objects.
Be sure you remove all references to a grid after youve removed it from the project.
Adding fields
Refer to Chapter 3, Fields that appear within a grid use the same properties, methods and
Programming events as fields that appear in a window. The only difference is that the
Window Fields, for VBA references the grids fields within the context of the grid, and
more information references the windows fields within the context of the window.
about working with
window fields.

To add a grids fields to your project, switch to Microsoft Dynamics GP and

display the window containing the grid.
Click the Expand button if you want to add fields from a line when its expanded.
The expanded line will show two or more rows, each containing multiple fields.
Be sure to select a line in the grid. On the Tools menu, point to Customize,
then choose Add Field To Visual Basic. This will activate field selection
mode, and a selection pointer will appear. The following illustration shows
the selection pointer.
Position the
selection pointer on
the field and click.
Using the mouse, click on the fields youll use in your project. You only
need to add fields from one line to your project. References you make to the
field in your VBA project will be for the line currently focused by the user,
so its not necessary to add the same field from multiple lines in the grid.
When youve finished adding fields, point to Customize on the Tools menu
and choose Add Fields to Visual Basic to deactivate field selection mode.
Field selection mode also deactivates when you switch to the Visual Basic Editor.
Programming a grid object

When programming the grid object, you can access only the current line in
a grid through VBA. This means that grid events occur only for the current
line, and you can set or return the values of fields that appear in the current
line. Keep in mind that you wont know which line in the grid is actually
the current line; you must rely on the data values of the fields in the line to
ascertain which line is selected. There are several ways you can use VBA to
interact with a grid object in your project.
Use grid event procedures

Grid events execute a procedure when the accounting system fills a grid,
when the user moves to a line, changes the contents of a line or exits the
line. Youll find grid events especially useful if you want to filter the
information displayed in a grid, or if you want to set or return field values
in a line as the user interacts with that line. The section titled Using grid
events explains each type of grid event you can use to execute VBA code.
Reference fields that appear in the grid

Like windows, grids contain window fields that you can reference and
manipulate through VBA. For grids whose fields are editable, window field
events occur when the user moves the focus between fields in a line.
If you reference window fields in windows or grids outside the current

grid, you must use a qualified field name. A qualified name explicitly
specifies the location of the field youre referencing. Refer to Chapter 3,
Programming Window Fields, for more information about using window
fields.
Reference the grid from other procedures

After you define a grid as an object in your project, any VBA code you write
in your VBA project has full access to the grid object, its properties and its
methods. You reference a grid in the same manner as a window, using the
grids name as a qualifier for any grid fields you reference.
Types of grids
Three types of grids can be found in Microsoft Dynamics GP: browse-only,
editable and adds-allowed. Each type has unique characteristics.
Browse-only grids
Browse-only grids allow the user to view information but not change it.
Microsoft Dynamics GP uses browse-only grids in lookup windows.
These are captions for each

field in a grid line, and are
not part of the grid.
A browse-only grid
contains non-editable
lines.

Editable grids
Editable grids allow the user to change the contents of the selected line.
Microsoft Dynamics GP uses these types of grids to change multiple
options for one or more lines.
You can change the

information in an
editable grid.
Adds-allowed grids
Adds-allowed grids let the user add additional lines of information to the
grid. The grid stores the new information in a table. Microsoft Dynamics GP
commonly uses adds-allowed grids in transaction entry windows, where
the user can add multiple line items for a transaction.
An adds-allowed grid has

a blank line that allows
users to add items.
Using grid events

A grid event executes a specific VBA procedure (an event procedure) only for
the current line in a grid. The current line is the line that has the focus. To
view the grid events available, select a grid object in your project, then
display the Visual Basic Code window. Select Grid in the Object list;
window events will appear in the Procedure list.
Select Grid in the

Object list.
choose an event.
Grid events appear

in the Procedure
list.
There are four basic kinds of grid events youll work with in VBA: line got
focus, line changed, line lost focus and line populate events. Events occur when
the user displays a new line in a grid (a line populate event) moves the focus
into a grid line (a line got focus event), when the value of a line changes (a
line changed event), or when the user moves the focus out of a line (a line lost
focus event).
Using modified or original windows

If you use the Modifier to modify a window containing a grid (such as a
lookup window), VBA grid events will occur only if you set both the
windows and the grids EventMode property to emModifiedOnly.
Changing this property allows events to occur only for the modified
version of the window and the grid. To change the EventMode property,
use the Visual Basic Properties window.
Line got focus events

VBA line got focus events occur when the user moves to a line in a grid. The
VBA BeforeLineGotFocus and AfterLineGotFocus events execute event
procedures before or after Microsoft Dynamics GP code runs for the got focus
event. Microsoft Dynamics GP typically uses the got focus event to verify
whether the user can enter the line. Since you cannot cancel the Microsoft
Dynamics GP got focus event from VBA, the VBA got focus event you
choose may be of little consequence.
Line got focus events are useful for checking the value of a field in the line
gaining focus. In the following example, the BeforeLineGotFocus event
checks the value of the Item Number field in the Invoice Entry grid. If the
field is empty, the event procedure opens the Items lookup window:
Private Sub Grid_BeforeLineGotFocus()

If ItemNumber.Empty = True Then
'Open the lookup window
InvoiceEntry.LookupButton6 = 1
End If
End Sub
Line change events

VBA line change events occur when the user changes the contents of a line
in an editable or adds-allowed grid, then moves the focus out of the line.
The VBA BeforeLineChange and AfterLineChange events occur before or
after Microsoft Dynamics GP code runs for the line change event.

Microsoft Dynamics GP uses the line change event to save data in the line to
a table when the user leaves the line. An example of this is the Invoice Entry
window, where each grid line represents a separate transaction record in
the invoice. As the user moves to a new line, the line change event saves the
invoice line item to a table.
BeforeLineChange
The BeforeLineChange event occurs before Microsoft Dynamics GP code
runs for the line change event. Use this event when you want to check the
value of fields in a line, then cancel the Microsoft Dynamics GP line change
event if specified criteria arent met. The KeepFocus parameter cancels the
line change event that normally saves the contents of the line, and moves
the focus to the field that last had focus in the line.
In the following example, the BeforeLineChange event checks the value of

the Markdown Amount field in the Invoice Entry grid. If the user attempts
to enter a markdown amount greater than 20%, the KeepFocus parameter
stops the Microsoft Dynamics GP line change event and moves the focus
back to the current line:
Private Sub Grid_BeforeLineChange(KeepFocus As Boolean)
If CCur(MarkdownAmount) > CCur(UnitPrice) * 0.2 Then
'The markdown was greater than 20%
KeepFocus = True
MsgBox "You cannot enter a markdown greater than 20% " + _
"of the unit price."
End If
End Sub
AfterLineChange
The AfterLineChange event occurs after Microsoft Dynamics GP code runs
for the line change event. Use this event to perform other actions in the
window after the accounting system saves data in the line. For instance,
when the user enters line item information in the Invoice Entry grid, then
moves to the next line item, the following AfterLineChange event
procedure checks the Subtotal field. If the invoice subtotal is greater than
$1000, it assigns a specific batch ID to the transaction:
Private Sub Grid_AfterLineChange()
If CCur(InvoiceEntry.Subtotal) > 1000 Then
'Set the batch ID to an existing batch
InvoiceEntry.BatchID = "BIGSALES"
InvoiceEntry.BatchID.Locked = True
End If
End Sub
Line lost focus events

VBA line lost focus events occur when the user moves the focus out of a
line. The VBA BeforeLineLostFocus and AfterLineLostFocus events occur
before or after the Microsoft Dynamics GP code runs for the lost focus event.
Microsoft Dynamics GP typically uses the lost focus event to prepare the
next line to accept data. Since you cannot cancel the got focus event from
VBA, the VBA line lost focus event you choose may be of little consequence.
In the following example, an AfterLineLostFocus event shrinks the grid

in the Invoice Entry window when the user moves to the next line.
Private Sub Grid_AfterLineLostFocus()

InvoiceEntry.ScrollingWindowExpandButton = 1
End Sub
Line populate event

The VBA BeforeLinePolulate event occurs each time Microsoft Dynamics
GP displays a new line in a grid. When the accounting system initially
displays a grid, the BeforeLinePopulate event occurs repeatedly until the
grid is full. It also occurs each time the user displays a new line in the grid,
by scrolling up or down in the grid.
The primary reason to use the BeforeLinePopulate event is to filter out any
lines you dont want to display in a grid. For instance, the following event
procedure displays only Illinois customers in the Customers and Prospects
lookup window:
Private Sub Grid_BeforeLinePopulate(RejectLine As Boolean)

If State <> "IL" Then
RejectLine = True
End If
End Sub
The RejectLine parameter lets you selectively filter records from the grid
when its filled. Limit use of the RejectLine parameter, since it can have an
impact on application performance.

A more elaborate use of the BeforeLinePopulate event could make use of a

new field added to a lookup window using the Modifier. For example, you
could use the Modifer to add a Fill By State field to the Customers and
Prospects lookup window. A VBA event procedure for the Fill By State field
fills the window by clicking the Redisplay button in the lookup window:
Private Sub FillByState_BeforeUserChanged(KeepFocus As Boolean, _
Redisplay = 1
End Sub
As the fill occurs, the following procedure uses the BeforeLinePopulate

events RejectLine parameter to reject records not indicated in the Fill By
State field:

If State <> CustomersandProspects.FillByState Then
RejectLine = True
End If
CustomersandProspects.FillByState.Focus
End Sub
Using grid properties and methods

Refer to Chapter 10, There are two properties available for the grid object: the Name property
Grid Object, for and the EventMode property.
detailed explanations
and examples of each Changing a grids name
grid property. The Name property allows you to change the name you use in VBA code to
reference the grid. You can change a grids name using the Visual Basic
Properties window, and the name will change in your project. You should
then recompile your project to replace any references to the previous grid
name. You may want to rename a grid to make it more readable.
Using the EventMode property

You can choose whether window events occur for the modified or original
version of a grid using the EventMode property. If you use the Modifier to
modify a window containing a grid, and you want VBA grid events to
occur for the modified window, change the EventMode property for both
the window and the grid object to emModifiedOnly. If you make no
modifications to a Microsoft Dynamics GP window or grid using the
Modifier, the default value for the EventMode property is
emOriginalOnly.
Chapter 5: Programming Reports
Refer to the Report Programming reports using VBA involves adding the report and report
Writer documentation fields to your project, choosing the report events youll use to execute VBA
for additional code, and working with methods and properties to customize report
information about display. Information about programming reports is divided into the
customizing reports. following sections:
Working with reports in your VBA project

Using report events
Start/End events
Band events
Using report properties and methods
Working with report fields
Exporting data to other applications
Working with reports in your VBA project

To use VBA with a report, youll first need to add the report to your project.
Adding a report creates a corresponding report object in your project,
which you can reference in VBA.
Adding a report object

To add a report to your project, launch Report Writer. Create a new or
modified version of the report you want to work with, then display the
reports layout. With the Report Layout window active, choose Add Report
To Visual Basic from the Tools menu.
Once youve added a report, switch to the Visual Basic Editor and display
the Project Explorer. It should look similar to the following:
The Project Explorer

displays the report
objects you have added.
Although you created a modified report using Report Writer, this was only
necessary to access the reports layout and create the report object in VBA.

You can determine whether you want VBA code to run for either the
modified or the original version of the report using the reports EventMode
property. See the section titled Using modified or original reports on page 85
for more information about the EventMode property.
Removing a report object

To remove a report object from your project, launch Report Writer and open
the report layout for the report you want to remove. From the Tools menu,
point to Customize, then choose Remove Current Report From Visual Basic.
VBA will remove the report and any report fields associated with the report
from your project.
Adding report field objects

For more information You can add two types of report fields to your VBA project: table fields and
about using VBA with calculated fields. To add a report field to your project, select the field in the
report fields, refer to report layout using the arrow tool, then choose Add Fields To Visual Basic
Working with report from the Tools menu.
fields on page 92.
If the same field appears multiple times on a report, its important that you
select the field located in the report section from which you are going to
reference the field. For example, a report field may appear in the report
body and in the page footer. If you will be referencing the field from the
BeforePF event, be sure youre adding the field located in the page footer.
If the field is not a table field or a calculated field, the Add Fields To Visual
Basic menu item will appear disabled. To add several fields at once, hold
down the SHIFT key and select the fields, then choose Add Fields To Visual
Basic.
Use the SHIFT key with the

arrow tool to select
multiple fields in the
report layout.
C H A P T E R 5 P R O G R AM M I N G R E P O R T S
After youve added a report field to a project, you can reference it only from
within a report event procedure. Report fields, unlike window fields, have
no associated field events. Therefore, you cannot write VBA code
specifically for a report field.
Using report events

A report event executes a specific procedure (an event procedure) when a
report prints. To view the report events available, select a report object in
the Project Explorer and display the Visual Basic Code window. Select
Report in the Object list; report events will appear in the Procedure list.
Select Report in the

Object list.
choose an event.
Report events
appear in the
Procedure list.
There are two kinds of report events youll work with: start/end events and
band events. A Start event always occurs at the beginning of a report and an
End event always occurs at the end of a report. Band events occur when a
particular section of a report, or a band, prints.
Using modified or original reports

Keep in mind that you only need to use Report Writer to add report and report field
objects to VBA. If you dont modify the report directly using Report Writer, you
can use VBA with the original report in Microsoft Dynamics GP.

Start/End events
Start/end events occur when the report starts and the report ends. The only
report data you have access to from start/end events are report legends,
which you can set or return in the Start event. To access report fields, you
must use band events.
Start event
For more information The Start event occurs just before the report starts to print, before any data
about using VBA with actually prints. The primary use of the Start event is to set report legends
legends, refer to using the Legend property. Legends are fields whose data is persistent
Working with legend throughout the report, and which must be passed to the report as it starts.
fields on page 92. The following example sets the value of a legend field from the Start event:
Private Sub Report_Start()

RMCustomerReport.Legend(2) = "Aging Period Amount"
End Sub
You can also use the reports Start event to initialize any module-level
variables youll use for the report. The following examples use a module-
level variable named Count to restrict a report to 10 customer records. The
Start event sets the counter to 0, then the BeforeAH event increments the
counter. After 10 records print, the BeforeAH event cancels the report using
the Cancel method.
'Declare a module-level variable

Private Count As Integer
---------------------------------------------------------------
'Initialize the count
Count = 0
End Sub
---------------------------------------------------------------
Private Sub Report_BeforeAH(ByVal Level As Integer, _
SuppressBand As Boolean)
'Increment the count
Count = Count + 1
If Count = 11 Then
RMCustomerReport.Cancel
End If
End Sub
End event
The End event occurs after a report prints. Use this event to perform any
clean-up activities for the report, launch other applications, or open and
close other windows. For example, the following End event procedure
launches Microsoft Outlook after the RM Customer Report prints:
Private Sub Report_End()
Dim RetVal As Variant
Response = MsgBox("Do you want to launch MS Outlook?", vbYesNo)
RetVal = Shell("C:\Program Files\Microsoft Office\ + _
"Office\Outlook.exe", vbNormalFocus)
End If
End Sub
Band events
The report band A report is composed of several sections called bands. In VBA, each report
explained in this band has a corresponding band event. As a report prints, each band event
section is the same as occurs just before the corresponding data within the band prints. The
the report section following illustration shows the different bands that compose a report:
thats explained in
Report Writer
documentation.
Page header
(BeforePH event)
Report header
(BeforeRH event)
Additional headers
(BeforeAH event)
Body
(BeforeBody event)
Additional footers
(BeforeAF event)
Report
Report footer
footer
(BeforeRF
(BeforeRF event)
event)
Page footer
(BeforePF event)

For more information The primary use of a band event is to return or set the value of a field in a
about setting and corresponding band using the Value property. You can use a band event to
returning report fields, return a value for any report table field or calculated field. You can set a
refer to Working with value only for a user-defined calculated field youve added using the
report fields on Report Writer.
page 92.
In the following illustration, the Customer Name table field and
EMailAddress user-defined calculated field appear within the RM
Customer Reports additional header. In this case, only the BeforeAH event
can reference these fields:
These fields are in the

additional header. The
BeforeAH event procedure
can reference these fields.
The BeforeAH event procedure can return the value of the Customer Name
table field, and set EMailAddress user-defined calculated field:
Private Sub Report_BeforeAF(By Val Level As Integer, SuppressBand _

As Boolean)
If CustomerName = "Aaron Fitz Electric" Then
'Set the user-defined calculated field
EMailAddress = "[email protected]"
End If
End Sub
Each band event includes a SuppressBand parameter. When set to True, the
SuppressBand parameter stops the current instance of the corresponding
band from printing. If a band prints multiple times in a report (such as the
report body), you can conditionally suppress a given instance of the band.
For example, the following BeforeBody procedure for the RM Salesperson
Report suppresses the current instance of the report body if the value of the
Commissioned Sales To Date field is less then $200,000:
Private Sub Report_BeforeBody(SuppressBand As Boolean)

If CCur(CommissionedSalesToDate) < 200000 Then
SuppressBand = True
End If
End Sub
If the report uses an accumulator field to calculate report totals or count the
number of bodies in a report, the accumulator field will still sum or count data from
fields in a suppressed band.
BeforePH event
The BeforePH event occurs before items in the page header print. Items in
the page header are placed at the top of every report page. Page number,
date and time fields are commonly placed in this section of a report.
BeforeRH event
The BeforeRH event occurs before items in the report header print. Items in
the report header appear only on the first page of a report. The title of the
report and introductory information are often included in this section. If a
page header is also included on the first page, the report header will appear
after the page header.
BeforeAH event
The BeforeAH event occurs before the reports additional header prints. A
report may have none, one or several additional headers, each indicated on
the report layout by H1, H2 and so on. Each prints when the data in the
field it is based on changes.
If a report uses multiple additional headers, use the BeforeAH events Level
parameter to specify an index corresponding to the number of the
additional header the event occurs for. In the following example, the
BeforeAH event procedure runs for the second additional header on a
report. The procedure also returns the value of the Checkbook ID field in
the second additional header:

Private Sub Report_BeforeAH(By Val Level As Integer, SuppressBand _

As Boolean)
If Level = 2 Then
BankDepositPostingJournal.Cancel
End If
End If
End Sub
If the report has only one additional header, the BeforeAH event occurs
only for that additional header, and you dont need to specify a value for
the Level parameter.
BeforeBody event
The BeforeBody event occurs before each instance of the reports body
prints. Microsoft Dynamics GP uses the report body for the bulk of a report,
which typically is made up of table fields. A report prints the body
repeatedly until all records in the report have printed.
BeforeRF event
The BeforeRF event occurs before the report footer prints. Items in the
report footer appear only on the last page of a report. Summary information
is often included the report footer. If a page footer is also included on the
last page, the report footer will print before the page footer.
BeforePF event
The BeforePF event occurs before the reports page footer prints. Items in
the page footer are placed at the bottom of every report page. The page
footer often includes administrative information, such as the name of the
person running the report.
BeforeAF event
The BeforeAF event occurs before the reports additional footer prints. A
report may have none, one or several additional footers, each indicated on
the report layout by F1, F2 and so on. Each prints when the data in the field
it is based on changes. Microsoft Dynamics GP uses the additional footer to
display summary data, such as a total of all records in the reports body.
If a report uses more than one additional footer, use the BeforeAF events
Level parameter to specify an index corresponding to the number of the
additional header you want the event to occur for. In the following
example, the BeforeAF event procedure runs for the second additional
footer that appears on the report:

As Boolean)
If Level = 2 Then
'Set the user-defined calculated field
EMailAddress = "[email protected]"
End If
End If
End Sub
If the report has only one additional footer, the BeforeAF event occurs only
for that additional footer, and you dont need to specify a value for the Level
parameter.
Using report properties and methods

Refer to Chapter 11, The following table explains the available report methods and properties.
Report Object, for The remainder of this section explains some of the more common methods
detailed explanations and properties youll use in when working with reports:
and examples of report
properties and Property/Method Description
methods described Cancel method Cancels the report from any report event.
here.
EventMode property Specifies whether report events occur for the original or
modified version of the report.
Legend property Specifies the value of a report legend.
Name property Specifies the internal name VBA uses for the report.
Canceling a report
You cancel a report using the Cancel method. The following example
cancels a report from the reports BeforeBody event:

If SalespersonID = "ERIN J." Then
RMSalespersonReport.Cancel
End If
End Sub
If you cancel a report from a reports band event, the report stops at that
band. If you cancel a report from a reports Start event, no data prints for
the report. In all cases, the reports End event will occur for a canceled
report. If the report is printed to the screen, the Cancel method closes the
Screen Output window automatically.

Working with legend fields

Use the Legend property to set or return the value of a legend field in a
report. You dont add a legend field to your project; instead, you use the
Legend propertys index parameter to refer to a specific legend field on the
report. In addition, you can set or return the value of a legend only in the
reports Start event.
A legend field contains data thats passed to the report at runtime, before it
prints. These fields typically include information about the report, such as
the range of records the user chose for the report. The following illustration
shows legend fields used to show the range of customer records that print
for the RM Customer Report:
This is the legends index.

The Legend property
references the legends
index, not the legend field.
For example, to return the value of the Customer Class legend field, the
following Start event procedure includes a reference to the fields index:

If RMCustomerReport.Legend(5) = "AARONFIT0001 - AARONFIT0001" Then
'Cancel the report
End If
Working with report fields

You can use the Value property to return the value of a table field, a
Microsoft Dynamics GP calculated field, or a user-defined calculated field.
You can also use the Value property to set the value of a user-defined
calculated field. For any field, the report event you use must correspond to
the report band containing the field.
Table fields
Table fields are fields whose values derive directly from a Microsoft
Dynamics GP table. You can return only the value of table fields.
Refer to the Report Calculated fields

Writer manual for Calculated fields are defined using table fields, constants and operators.
more information Microsoft Dynamics GP typically uses calculated fields to conditionally
about creating and print data on a report. You can only return the value of a Microsoft
using calculated fields. Dynamics GP calculated field. You can set or return the value of a
calculated field you added to the report using Report Writer.
Accumulator fields
You can return the values of accumulator fields in a report. You can also
set the value of calculated fields you add to the report that function as
accumulator fields. An accumulator field is a table field or calculated field
that performs a specific function in the report, and whose field type is not
DATA. The field type for an accumulator field determines its function. For
instance, an accumulator field can count the number of occurrences of a
field (a COUNT field type), or calculate the sum total of each occurrence of
a numeric field (a SUM field type). Use the Report Writers Report Field
Options window to determine the field type for a selected field.
Field formats
With the exception of composite fields, VBA returns report field values
without any formatting. For instance, VBA returns the phone number (701)
555-0100 Ext. 1772 as 70155501001772. Likewise, VBA returns the currency
value $10.56 as 10.56000.
To format a report field value, use VBAs Format function. The Format
function allows you to define a format string for a specific field type (string
or numeric). The following example uses the Format function to format the
fax number string field:
MsgBox Fax
'Displays 70155501001772
'Use the format function to format the string
Format(Fax, "(@@@) @@@-@@@@ Ext. @@@@")
MsgBox Fax
'Displays (701) 555-0100 Ext. 1772
Hiding and showing report fields

Use the field objects Visible property to hide and show report fields. You
can hide any table field or calculated field on a report. However, you can
only show fields youve hidden using VBA. If invisible, a fields value is
still available to VBA, but will not appear in the report.

The following example uses the Visible property to hide the Total Sales
YTD field in the RM Customer Report if the Territory ID field is
TERRITORY 1:
Private Sub Report_BeforeAH(ByVal Level As Integer, SuppressBand As _

Boolean)
If SalesTerritory = "TERRITORY 1" Then
'Hide the YTD sales amount
TotalSalesYTD.Visible = False
Else
TotalSalesYTD.Visible = True
End If
End Sub
Returning fields from multiple bands

Since you only have access to field values as the fields band prints, youll
likely find it necessary to use module-level variables to store report
information from multiple bands. As each band prints, you can store
selected values from the band using the module-level variables.
The following example exports data from the Microsoft Dynamics GP Item
Price List to a text file. The procedure declares several module-level
variables to store report data. It then uses VBA events (the BeforeAH and
BeforeBody events) to return field values from their respective bands and
set module-level variables:
'Declare module-level variables

Private QTY As Integer
Private ItmDesc, ItmNum, VenName As String
--------------------------------------------------------------------
Private Sub Report_BeforeAH(ByVal Level As Integer, SuppressBand _
As Boolean)
If CInt(QTYOnHand) < 10 Then
'Set the module-level variables for fields in this band
ItmDesc = ItemDescription
ItmNum = ItemNumber
QTY = QTYOnHand
Else
QTY = 0
End If
End Sub
--------------------------------------------------------------------

'Check the value of the QTY variable
If QTY <> 0 Then
'Set the module-level variable for the field in this band
VenName = VendorName
'Create a text file. You could also export these to Excel
Open "ItemQuantities.TXT" For Append As #1
Print #1, "Item Number: " + ItmNum
Print #1, "Item Description: " + ItmDesc
Print #1, "Avail. QTY: " + Str(QTY)
Print #1, "Vendor Name: " + VenName
Print #1, ""
Close #1
End If
End Sub
Exporting data to other applications

Reports are useful for exporting multiple records from the accounting
system to other VBA-compliant applications, such as Microsoft Excel,
Outlook or Word. A reports output can include several records, such as
customer, item or transaction records. You can use VBA to analyze each
record in the report as the report prints, then export specific field values to
another application.
Before you can work with another applications objects, you must set a reference to
that applications object library using the References dialog box in the Visual Basic
Editor.
The following example uses the RM Customer Report to create customer

contacts in Microsoft Outlook. The example first declares two module-level
variables used to create Outlook contact objects. The reports Start event
then creates and returns a reference to Outlook using VBAs CreateObject()
function.
The RM Customer Reports additional header contains the majority of

customer information, so the procedure uses the BeforeAH event to return
customer information. As Report Writer prints each additional header (one
per customer record), the procedure checks the Sales Territory field. For
each customer in TERRITORY1, the procedure creates a contact object in
Microsoft Outlook, and sets properties in the contact object to fields in the
report:

'Declare module-level variables in the general section

Dim DynItem, DynOlApp As Object
---------------------------------------------------------------------
Report_Start()
'Create the Outlook object
Set DynOlApp = CreateObject("Outlook.Application")
End Sub
---------------------------------------------------------------------
Private Sub Report_BeforeAH(ByVal Level As Integer, _
SuppressBand As Boolean)
If SalesTerritory = "TERRITORY 1" Then
'Add customer information to Outlook
Set DynItem = DynOlApp.CreateItem(olContactItem)
'Set contact object properties to window field values

DynItem.FullName = ContactPerson
DynItem.CompanyName = CustomerName
DynItem.BusinessAddressStreet = Address1
DynItem.BusinessAddressCity = City
DynItem.BusinessAddressState = State
DynItem.BusinessAddressPostalCode = Zip
'Format report fields

DynItem.BusinessTelephoneNumber = Format(Phone1, _
"(@@@) @@@-@@@@ Ext. @@@@")
DynItem.BusinessFaxNumber = Format(Fax, _
"(@@@) @@@-@@@@ Ext. @@@@")
'Save the contact object
DynItem.Save
End If
End Sub
Chapter 6: Storing Additional Data
The Dynamic User Object Store (DUOS) lets you use VBA to create, store
and retrieve user-definable data objects. You can use the DUOS to store data
entered in existing Microsoft Dynamics GP fields, new fields added using
the Modifier, or fields entered in a VBA user form. You can then retrieve a
data object from the DUOS and display it in a VBA user form or in a
Microsoft Dynamics GP window. Information about the DUOS is divided
into the following sections:
Understanding the DUOS

Structure of the DUOS
Working with DUOS data objects
Retrieving a DUOS data object
Deleting a DUOS data object
Updating a DUOS data object
DUOS properties and methods
Using the DUOS
Understanding the DUOS

Refer to Part 2, VBA The VBA object model uses two collections and two objects to define DUOS
Object Library, for data objects. The DUOSObjects collection contains one or more user-
detailed information definable collections you create to store related data objects, such as
about the methods and customer, vendor or item collections. The DUOSObject object represents a
properties available for single data object within a collection, such as a customer object within a
the DUOS objects and customer collection. The following illustration shows the DUOS portion of
collections. the VBA object model:
DUOSObjects
DUOSObject
DUOSProperties
DUOSproperty
Object
Collection Object

The second collection, the DUOSProperties collection, contains all the

properties for the data objects in the DUOSObjects collection. The
DUOSProperty object represents a single property for a single object in the
DUOSProperties collection.
Structure of the DUOS

The DUOS is composed of user-defined collections, each of which can store
several data objects. Each data object can contain several properties and
property values. The following table shows the structure of the DUOS that
contains two user-defined collections (Customers and Items):
Collection Object ID Property name Property value

name
Customers ALTONMAN0001 URL Address www.altonman.com
A collection named Contact E-Mail [email protected]

"Customers" Address
ADVANCED0001 URL Address www.advanced.com
Contact E-Mail [email protected]

A data object within the Address
collection.
Customer Type RETAIL
Items ITM001 Item Weight 2.45
Item Color Blue
ITM004 Item Weight 3.50
The Collection name is a string specifying the user-defined collection

where youre storing the data object. This name cannot exceed 30 char-
acters. You can create or specify the collection you want to work with
using the global DUOSObjectsGet method.
The Object ID is a unique value for a data object within its collection.
This ID cannot exceed 60 characters. You can specify the object ID using
the Item property from the DUOSObjects collection.
The Property name is a string that specifies the name of the property for
the object. The property name cannot exceed 30 characters. You can
define several property names for a data object. Each object in a collec-
tion may contain different property names. You can specify the prop-
erty name using the Item property in the DUOSProperties collection.
A data object must have at least one property name to remain persistent in the
DUOS.
C H A P T E R 6 S T O R I N G A DD IT IO N A L DA T A
The Property value is a string that specifies the value of the property.
This value cannot exceed 132 characters. The DUOS stores all property
values as strings. You can specify a property value using the
Value property from the DUOSProperty object.
Microsoft Dynamics GP stores DUOS data objects in a table named

SY_User_Object_Store (SY90000.*). This table is company-specific, so
Microsoft Dynamics GP stores data objects you create for each company in
separate tables, located in separate directories. The combination of the
collection name, object ID, property name and property value all make up a
single record in this table:
Each column heading is

Collection Object ID Property Property
a field in the
name name value
SY_User_Object_Store
table. Items ITM000 Item Weight 3.5
Each row represents a Items ITM000 Item Color Red

record in the Items ITM001 Item Weight 2.45
SY_User_Object_Store Items ITM001 Item Color Blue
table.
If two additional properties and property values are added to the ITM001
data object, the accounting system adds two records to this table:
Collection Object ID Property Property

name name value
Items ITM000 Item Color Red
Items ITM001 Item Color Blue
Two new properties
Items ITM001 Item Height 4.5
added to an item creates
two new records. Items ITM001 Item Width 2.75
Since Microsoft Dynamics GP stores DUOS data objects in a table, you can
use table maintenance windows to perform routine table maintenance.

Working with DUOS data objects

To create a DUOS data object, use the DUOS global
DUOSObjectsGet method to specify a collection. If the collection doesnt
exist, this method creates it. The following example specifies a collection
named Additional Item Info.
The example then uses the collections Item property to assign a unique ID
to the data object (ITM002). If an object with that ID already exists, the Item
property specifies an existing object in the collection with that ID. Finally,
this example creates two new properties for the data object using the
DUOSObjects collections Item property, and assigns values to each:
Dim ItemCollection As DUOSObjects

Dim ItemObject As DUOSObject
'Specify the collection

Set ItemCollection = DUOSObjectsGet("Additional Item Info")
'Specify an object in the collection with a unique object ID

Set ItemObject = ItemCollection.Item("ITM002")
'Create properties and property values for this object

ItemObject.Properties.Item("Item Weight") = "3.5"
ItemObject.Properties.Item("Item Color") = "Red"
If youre storing values entered from window fields (either in a Microsoft

Dynamics GP window or from a VBA user form), set the objects property
values to the values of the window fields. A portion of the previous
example would then look like this:
'Set the object ID using the ItemID field

Set ItemObject = ItemCollection.Item(ItemID)
'Set property values using two window fields

ItemObject.Properties.Item("Item Weight") = ItemWeight
ItemObject.Properties.Item("Item Color") = ItemColor

To retrieve a DUOS data object, you return an object from the objects
collection, then set window fields to the property values for the object:

'Specify the object to display in the window
Set ItemObject = ItemCollection("ITM002")
'Set two window fields
ItemWeightField = ItemObject.Properties.Item("Item Weight")
ItemColorField = ItemObject.Properties.Item("Item Color")

You delete a DUOS object using the collections Remove method. In the
following example, the procedure removes the data object with the ID
ITM002 from the ItemCollection:

ItemCollection.Remove("ITM002")
Updating a DUOS data object

You can update a DUOS data object when window field values change. In
this example, the procedure updates a data objects properties, and adds a
property named Date Changed:

'Set property values from window fields for this object

ItemObject.Properties.Item("Item Weight") = ItemWeight
ItemObject.Properties.Item("Item Color") = ItemColor
'Set the date changed property to the VBA system date

ItemObject.Properties.Item("Date Changed") = Date

You can also globally update DUOS data objects by looping through each
object in the collection. In this example, the For...Next statement in VBA
checks the Item Color property for each item in the ItemCollection. If the
value is Red, the collections Remove method deletes the object:


For Each ItemObject In ItemCollection
If ItemObject.Properties.Item("Item Color") = "Red" Then
'Delete the object
ItemCollection.Remove(ItemObject.ID)
End If
Next
DUOS properties and methods

Refer to Part 2, VBA Properties and methods youll use for the DUOS are members of three
Object Library, for objects and two collections in VBA. The following table lists each object, its
detailed explanations member properties and methods, and a brief description of each:
and examples of DUOS
properties and Object/ Property/ Method Description
methods described Collection
here. Global object DUOSObjectCombineID Combines two strings to generate a
method unique object ID.
DUOSObjectExtractID Extracts two strings from a combined
method object ID.
DUOSObjectsGet method Returns or creates a user-defined
collection in the DUOS.
DUOSObjects Exists property Returns whether a data object exists
collection in a user-defined collection.
Item property Returns a data object from a user-
defined collection.
SortByExisting property Specifies the property used to sort
the data objects in a user-defined
collection.
Type property Returns the name of a user-defined
collection the data object belongs to.
Remove method Removes a data object from a user-
defined collection.
Object/ Property/ Method Description

Collection
DUOSObject ID property Returns the object ID for a data
object object.
Properties property Returns properties for a data object.
DUOSProperties Count property Specifies the number of properties in
collection a data object.
Exists property Specifies whether a property exists
for a data object
Item property Returns or creates a user-defined
property in a data object.
Remove method Removes a user-defined property
from a data object.
DUOSProperty Name property Specifies the name of a user-defined
object property.
Value property Specifies the value of a user-defined
property.
Using the DUOS

Using the DUOS typically involves adding fields to a window using the
Modifier, and writing VBA code that saves, displays or deletes the data
object in the DUOS when the user saves, displays or deletes a
corresponding record in the window. The remainder of this section explains
how to address each of these issues in more detail.
A URL Address field and Contact E-mail Address field were added to the
Customer Maintenance window with the Modifier. The examples in the
remainder of this section will create a DUOS customer collection and data
objects to store and display information in these fields.

When the user saves,

deletes, or displays a record,
youll need to save, delete,
or display the corresponding
DUOS data object.
To display data from the

DUOS, add fields using
the Modifier.
Saving a DUOS data object

There are two situations where youll need to save a DUOS data object:
when the user clicks the Save button in a window, and when the user
attempts to close the window or display another record without saving
changes in the window (such as when using browse buttons). When you
store a DUOS data object, youll need to address both of these situations.
Using the Save button

The following BeforeUserChanged field event procedure runs when the
user clicks the Save button in the Customer Maintenance window. It first
checks whether the user entered all required fields in the window using the
windows Required property. It then specifies the collection where it will
store the object using the DUOSObjectsGet method.
To ensure the object has a unique ID, the ObjectID parameter of the
Item property uses the value of the Customer ID field. The procedure
defines the DUOS data objects property names (URL Address and
Contact E-Mail Address) and sets its property values to the values
entered in the new fields:

Dim CustomerCollection As DUOSObjects
Dim CustomerObject As DUOSObject
If CustomerMaintenance.Required = True Then

'The user entered all required fields. Create/get the collection
Set CustomerCollection = DUOSObjectsGet("CustomerCollection")
'Create the object, using the customer ID as the object ID

Set CustomerObject = CustomerCollection.Item(CustomerID)
'Set the objects property names and values

CustomerObject.Properties("URL Address") = URLAddress
CustomerObject.Properties("Contact E-Mail Address") _
= ContactEMailAddress
End If
End Sub
Using the Save dialog

The Microsoft Dynamics GP save dialog appears when the user makes
changes to a record, then attempts to move to another record or close the
window without saving changes. This dialog appears in the following
illustration.
The user can click the Save button to save the changes, the Discard button
to ignore the changes, or the Cancel button to close the dialog and cancel
the save operation. In this situation, youll need to know when the user
clicks the Save button, and save any changes to the corresponding DUOS
data object. To do this, use a window AfterModalDialog event.

In the following example, the AfterModalDialog event procedure runs

when a modal dialog appears for the Customer Maintenance window. It
uses the PromptString parameter to ascertain whether the Microsoft
Dynamics GP save dialog appeared. If the user clicks the Save button, the
procedure specifies the collection, then specifies the data object using the
collections Item property:



"customer?" Then
'The save dialog appeared, asking if the user wants to save
'changes
If Answer = dcButton1 Then
'The user clicked Save. Get the collection
Set CustomerCollection = DUOSObjectsGet _
("CustomerCollection")
'Return the correct customer object

'Save the values from the window fields

End If
End If
End Sub
Youll also use the windows AfterModalDialog event to respond to the

Microsoft Dynamics GP delete dialog. See Deleting a DUOS data object on
page 101 for more information.

After youve saved a DUOS data object, youll need to display it when the
user displays its associated record. To do this, add a Changed event
procedure for the windows control field (the field that controls the display
of the record in the window). This field also provides the record with a
unique value, such as an item or customer ID, or a document number.
In the following example, the Customer Maintenance windows control

field is the Customer ID field. Whenever this field changes (such as when
the user browses records in the Customer Maintenance window), the
Changed event procedure runs. It uses the collections Item property to
return the data object matching the new value in the Customer ID field. The
procedure then updates window fields using the customer objects
Properties property:

If CustomerID.Empty = False Then
'There's a new value in the field. Retrieve the customer
'object from the collection using the value in the
'Customer ID field
'Update the window fields

URLAddress = CustomerObject.Properties("URL Address")
ContctEMailAddress = CustomerObject.Properties _
("Contact E-Mail Address")
End If
End Sub

Youll likely want to delete a DUOS data object from the collection when the
user deletes its corresponding record in the accounting system. This ensures
that you dont have an orphaned DUOS data object after the user deletes
the corresponding record.
Instead of writing VBA code that deletes a DUOS data object when the user
clicks the Delete button, you delete a DUOS data object based on how the
user responds to the delete dialog. This modal dialog appears after the user
clicks the Delete button.

The user can either click Delete to delete the record, or click Cancel and
cancel the operation. Youll want to delete a DUOS object only if the user
clicks Delete in response to the dialog. Similar to saving DUOS objects, you
can accomplish this by using the AfterModalDialog event. The code that is
added to this event will then track whether the user selected the delete
button.
In some situations, theres one other condition youll need to address when
deleting a DUOS object. A second message dialog may appear if the
accounting system was unable to delete the record. For example, an
additional message will be displayed if a customer record has any
outstanding transactions corresponding to it.
The second message dialog needs to be handled differently than the delete
dialog. This is because theres no AfterModalDialog event available for the
secondary message. Instead, youll need to handle the message dialog as a
separate Microsoft Dynamics GP window and add it to your VBA project.
Once added, you use VBA code in the windows AfterOpen event to
ascertain whether the message prevented the record from being deleted.
The following series of examples show how to do this for DUOS data
objects stored with customer information.
Example: Customer Maintenance window

The following example shows the VBA code for the Customer Maintenance
window thats necessary to correctly delete a DUOS data object. This
example is intended to work in conjunction with the example for the
Microsoft Dynamics GP message dialog box, which follows this example.
Together, these two examples allow you to correctly handle DUOS delete
operations for the Customer Maintenance window.
Notice that there are three different variables (WanttoDelete, OktoDelete and
CustIDtoDelete) used throughout these examples. These are declared as
public variables and then initialized and set in the appropriate events:
'Declare module-level variables in the General section of the

'Customer Maintenance window object
Public WanttoDelete As Boolean
Public OktoDelete As Boolean
Dim CustIDtoDelete As String
---------------------------------------------------------------------
If CustomerID.Empty = False Then
'Initialize variables
CustIDtoDelete = CustomerID
OktoDelete = True
WanttoDelete = False
End If
End Sub
---------------------------------------------------------------------
PromptString As String, Control1String As String, Control2String As _
String, Control3String As String, Answer As Long)
If PromptString = "Are you sure you want to delete this + _

"customer record?" Then
If Answer = dcButton1 Then
'The user clicked Delete on the delete dialog message
WanttoDelete = True
End If
End If
End Sub
---------------------------------------------------------------------
Private Sub Delete_AfterUserChanged()
'The user clicks the Delete button and no transactions exist

If WanttoDelete And OktoDelete Then
'Create the collection
Set CustomerCollection = DUOSObjectsGet("Customer _
Information")
'Create the object using the CustomerID that was on the
'window
Set CustomerObject = CustomerCollection.Item(CustIDtoDelete)
'Remove the object
CustomerCollection.Remove (CustIDtoDelete)
End If
End Sub

Example: Dynamics1 message dialog window

The following example is attached to the Dynamics1 window object (the
second message dialog). This example works with the example for the
Customer Maintenance window (shown in the previous example). In this
case, the public variable declared in the General section of the Customer
Maintenance window code (OktoDelete) is set to False, since Microsoft
Dynamics GP cannot delete the customer record:

CustomerMaintenance.OktoDelete = False
End Sub
Printing data from the DUOS

Refer to Chapter 5, After youve used the DUOS to display additional information in a
Programming window, you can use VBA to print DUOS information on a report. Printing
Reports, for more data from the DUOS involves adding calculated fields to the report, adding
information about the report and the calculated fields from the report to your project, then
working with reports using VBA to set the calculated fields from the DUOS.
and using calculated
fields on a report. In the following illustration, the report layout for the RM Customer Report
includes two new calculated string fields. The VBA example later in this
section will use these fields to display values from a DUOS data object.
To print data from the

DUOS, add calculated
fields to the report.
In the following example, the event procedure runs when the user prints
the RM Customer Report. It updates two calculated string fields on the
report (DUOSCustomerWebAddress and DUOSCustomerEMailAddress)
with the data object in the customer collection. Since the new calculated
fields are in the reports additional header, this procedure uses the
BeforeAH event to set the field values before data in the additional header
prints.
Note that the RM Customer Report uses a field named Customer Number.
This is the same field as the Customer ID field referenced in the Customer
Maintenance window:
Private Sub Report_BeforeAH(ByVal Level As Integer, SuppressBand _

As Boolean)
'Return the customer collection

Set CustomerObject = CustomerCollection(CustomerNumber)
'Update the report fields

DUOSCustomerWebAddress = CustomerObject.Properties("URL Address")
DUOSCustomerEMailAddress = CustomerObject.Properties _
("Contact E-Mail Address")
End Sub

Chapter 7: Distributing a Project
After youve developed and tested your project, you can distribute it to
individual workstations. This portion of the documentation describes
issues you need to be aware of when packaging and distributing VBA
projects. It contains the following sections:
Enabling VBA
References to external components
Distributing project files
Package files
Package file import/export issues
Enabling VBA
To use VBA, an installation of Microsoft Dynamics GP must have the
appropriate registration keys. These registration keys must provide access
to one of the following:
The Modifier with VBA

The Customization Site Enabler
Refer to the System documentation for Microsoft Dynamics GP to learn

more about entering registration keys. You can obtain registration keys for
the Customization Site Enabler module from Microsoft.
References to external components

You can reference external components, such as ActiveX controls, from
within your VBA project. When you distribute the VBA customization to
other workstations, be sure that any additional components you have used
are also installed.
If you will be distributing other components with your VBA customization, be sure
you arent violating the license agreement by distributing those components.
To avoid problems referencing external components from your VBA

project, do the following:
Refer only to components you need. Dont make references to compo-

nents that arent being used in your project.

Watch for hidden references, such as those created when you add a
control to the Visual Basic toolbox.
Be sure you have installed and registered needed components before

running the VBA project.
Keep external components in known locations, such as next to the VBA

project or in the Windows system directory.
Distributing project files

One method of distributing a finished VBA customization is to copy the
VBA project file to the destination machine. The primary reason to use this
method is when you have created an extensive VBA project that contains
proprietary code you dont want others to see. You can lock the VBA project
before you distribute it, preventing others from examining your code. Do
this by viewing the properties for the project and displaying the Protection
tab.
There are disadvantages to locking a VBA project:
Other VBA developers customizations cant be added to the VBA

project.
End-users cant add any of their own functionality with VBA.
Also, distributing an entire VBA project doesnt allow you to package any
modified forms or modified reports that may be part of your customization.
For all these reasons, we recommend that you use package files to distribute
your VBA customizations.
C H A P T E R 7 D I S T R I B U T I N G A P R O J E C T
Package files
Package files are special text files used to deliver customizations made with
the Modifier, VBA, and the Report Writer. A developer can create a package
file ontaining their customizations, move the package file to the destination
workstation, then import the customizations into the installation.
Package file contents

A package file can contain the following items:
Modified forms Forms that have been customized with the Modifier.
New or Modified reports Reports that have been created or

customized with the Report Writer.
VBA forms Forms that have VBA code attached.
VBA reports Reports that have VBA code attached.
VBA components User forms, code modules or class modules created

with the VBA development environment.
References References to external components used by VBA. A package

file cannot contain the actual components referenced by the VBA
customization. Those components must be delivered separately.
Exporting a package file

Package files are created using the Customization Maintenance window.
Complete the following procedure to create a package file.
1. Open the Customization Maintenance window.

Open this window by pointing to Customize in the Tools menu and
choosing Customization Maintenance.

2. Select the components needed for the customization.

The Customization Maintenance window lists all of the components
that have been customized with the Modifier, Report Writer or VBA.
Select all of the components that are required for your customization.
Select all of the

components that are part
of the customization.
You cannot export

components that are part
of locked VBA projects.
To select non-contiguous items in the list, hold down the CTRL key and click the
items.
Click Export. A file dialog will appear, allowing you to specify the
name of the package file. Be sure the file has the .package extension.
The results of the export operation will be displayed in the status area
at the bottom of the window.
Note that some global changes you make with the Modifier and Report Writer
cant be included in a package file. For instance, changes to picture resources or
global data types wont be included in package files.
Importing a package file

To import the contents of a package file, complete the following procedure.
1. Open the Customization Maintenance window.

Open this window by pointing to Customize in the Tools menu and
choosing Customization Maintenance.
2. Open the Import Package File window.

Click Import in the Customization Maintenance window to display the
Import Package File window.
C H A P T E R 7 D I S T R I B U T I N G A P R O J E C T
3. Select the package to import.

Click Browse to open a file dialog that allows you to select the package
file you want to import. The contents of the package will be displayed
in the Import Package File window.
An X in the Overwrite column indicates that a customized version of

a component already exists for the system, and will be overwritten by
the contents of the package file. Refer to Package file import/export issues
on page 118 for details about overwriting existing customizations.
If any of the package file items contain VBA code, the user importing them
must have appropriate user privileges to update the .vba files in the Microsoft
Dynamics GP installation. Typically, this means being part of the
Administrators group or the Power Users group on Windows XP. On
Windows Vista, it means launching Microsoft Dynamics GP with
Administrative privileges.
Click OK to start the import process. If any errors occur during the
import process, the Errors window will be displayed. The results of the
import operation will also be displayed in the status bar of the
Customization Maintenance window. To view the list of the last errors
that occurred, click the Errors button in the status bar.
4. Set access to any modified forms or reports that are part of

the customization.
If necessary, use the security features in Microsoft Dynamics GP to
grant access to any modified forms or modified reports that are part of
your customization.

Package file import/export issues

There are some additional issues you need to be aware of when importing
and exporting package files, concerning how customized resources are
stored by Microsoft Dynamics GP.
Microsoft Dynamics GP contains forms, which are groups of windows,

menus and other resources that work together for a common purpose. A
form can have several windows, but you can make customizations to
individual windows with the Modifier and VBA. When you export a form
to a package file, you are exporting all of the windows in that form, not just
the windows you modified or applied VBA code to.
This fact is important to keep in mind when you import a package file that
contains customized forms. If a customized version of the form already
exists in the system and you import another set of customizations for that
same form, the original customizations will be overwritten. This occurs
even if the customizations are made for different windows in the form.
A similar issue occurs for reports. If youve made customizations to a

report, then import a package that contains customizations for that same
report, the existing customizations will be overwritten.
A warning message is automatically displayed allowing you to cancel an import

operation that will overwrite existing customizations.
PART 2: VBA OBJECT LIBRARY
Part 2: VBA Object Library
This part describes the objects that Microsoft Dynamics GP makes available
to VBA. It provides detailed descriptions of the events, properties and
methods for each object. The following topics are discussed:
Chapter 8, Window Object, describes the events, properties and

methods for window objects.
Chapter 9, Field Object, describes the events, properties and methods

for window and report fields.
Chapter 10, Grid Object, describes the events and properties for grids
(scrolling windows).
Chapter 11, Report Object, describes the events, properties and meth-
ods for reports.
Chapter 12, VBAGlobal Object, describes the global methods avail-

able for the Dynamic User Object Store (DUOS).
Chapter 13, DUOSObjects Collection, describes the properties and

methods for a collection in the DUOS.
Chapter 14, DUOSObject Object, describes the properties for a data

object in the DUOS.
Chapter 15, DUOSProperties Collection, describes the properties and

methods for a property collection in the DUOS.
Chapter 16, DUOSProperty Object, describes the properties for a

property object in the DUOS.
Chapter 17, UserInfo Object, describes the properties and method for
retrieving information about the current user.
The syntax descriptions and programming style used in this part are the
same as those used in VBAs documentation.
Chapter 8: Window Object
Your project uses the window object to perform several tasks related to
windows. The events, methods and properties that apply to the window
object are listed below. A detailed explanation of each follows.
Activate method
AfterActivate event
AfterClose event
AfterOpen event
BeforeActivate event
BeforeClose event
BeforeOpen event
Caption property
Changed property
Close method
EventMode property
Height property
Hide method
IsLoaded property
Left property
Move method
Name property
Open method
PullFocus method
Required property
Show method
Top property
Visible property
Width property

A C T I V A T E M E T H O D
Activate method
Description The Activate method activates a window, making it the frontmost.
Syntax window.Activate
Parameters window A window object.
Comments If the window is minimized, the Activate method expands the window.
The BeforeActivate and AfterActivate events occur when you activate a

window.
Examples This example uses the Activate method to activate the Customer
Maintenance window:
CustomerMaintenance.Activate
Related items Events

The window objects BeforeActivate event and AfterActivate event.
A F T E R A C T I V A T E E V E N T
AfterActivate event
Description The AfterActivate event occurs when a window is activated. It occurs after
the Microsoft Dynamics GP window activate event.
Syntax window_AfterActivate()
Comments A window is activated when its moved from the background to the
foreground in an application, becoming the frontmost window.
Microsoft Dynamics GP rarely uses its window activate event. Whether you choose
to use the AfterActivate event or BeforeActivate event is of little consequence.
Examples The following AfterActivate event procedure runs when the Customers
And Prospects lookup window is activated. As the user browses through
records in the Customer Maintenance window, the lookup window remains
open, but deactivated. When the user activates the lookup window, this
procedure places the focus on the same record in the lookup window as
was displayed in the Customer Maintenance window:
Private Sub Window_BeforeActivate()

'Set the lookup sort list to item 2, "by Name"
CustomerSortBy = 2
'Open the find dialog and make it invisible

FindDialog.Open
Dynamics.FindDialog.Visible = False
'Set the sort by list and locate the customer record displayed in
'the Customer Maintenance window
FindDialog.CustomerSortBy = 2
FindDialog.SearchText = CustomerMaintenance.Name1
'Press the find button

FindDialog.Find = 1
End Sub
Related items Methods and properties

The window objects Activate method.

A F T E R C L O S E E V E N T
AfterClose event
Description The AfterClose event occurs when the window closes. It occurs after the
Microsoft Dynamics GP window close event.
Syntax window_AfterClose()
Comments Microsoft Dynamics GP typically uses the window close event to check for
any unsaved changes, or whether the user entered all required fields in the
window, and display the appropriate dialog.
Examples In this example, the AfterClose event closes a lookup window after the
Customer Maintenance window closes:
Private Sub CustomerMaintenance_AfterClose()

End If
End Sub

The window objects Close method.
A F T E R M O D A L D I A L O G E V E N T
Description The AfterModalDialog event occurs after the user dismisses a modal
dialog.
Syntax window_AfterModalDialog(ByVal DlgType As Long, PromptString As

String, Control1String As String, Control2String As String, Control3String
As String, Answer As Long)
ByVal DlgType As Long Returns the type of dialog displayed. The

following constants specify the dialog type:
Constant Description
dtModalAskDialog An ask dialog. It contains one or more buttons, and
displays message text.
dtModalGetStringDialog A getstring dialog. It contains a data entry field and OK
and Cancel buttons.
PromptString As String The message text. Since multiple dialogs can

appear for a single window, use the PromptString parameter to ascertain
which modal dialog appeared.
Control1String As String...Control3String As String Returns the

corresponding button text in the modal dialog. For getstring dialogs,
Control3String returns the text the user entered in the data entry field.
Answer As Long A constant specifying the button the user clicked:
dcButton1 The first button in an ask dialog.
dcButton2 The second button in an ask dialog.
dcButton3 The third button in an ask dialog.
dcCancel The Cancel button in a getstring dialog.
dcOK The OK button in a getstring dialog.

Comments The most common use of the AfterModalDialog event is when saving or
deleting data objects from the Dynamic User Object Store (DUOS). For
instance, if the user clicks the Delete button in the Customer Maintenance
window, a modal dialog will appear, asking if the user wants to delete the
customer record. Using the AfterModalDialog event, you can find out
whether the user clicked the dialogs Delete button. If so, you can delete the
corresponding DUOS data object for that customer record.
The AfterModalDialog event wont occur for all dialogs displayed in Microsoft
Dynamics GP. Dialogs that display a help button and whose title is Microsoft
Dynamics GP will function like standard window objects in your project, and will
not invoke modal dialog events when displayed.
Ask dialogs
The dtModalAskDialog constant of the DlgType parameter specifies an ask
dialog. An ask dialog displays one or more buttons and message text. The
following illustration shows an ask dialog and the corresponding
parameters in the AfterModalDialog event:
PromptString
Control1String
The Answer parameter of the AfterModalDialog event returns which

button the user clicked: the first, second or third button in the dialog
(represented by the constants dcButton1, dcButton2 and dcButton3).
Getstring dialogs
The dtModalGetStringDialog constant of the DlgType parameter specifies a
getstring dialog. Getstring dialogs typically contain a message, a data entry
field, and OK and Cancel buttons:
PromptString
Control3String
Control1String
Control2String
The Answer parameter of the AfterModalDialog event returns which

button the user clicked: OK or Cancel (represented by the constants
dcCancel and dcOK).
Examples This procedure runs when the accounting system displays an ask dialog
that prompts the user to save changes to a customer record in the Customer
Maintenance window. If the user clicks the Save button in the save dialog,
this procedure saves the corresponding DUOS object:

PromptString As String, Control1String As String, _
Control2String As String, Control3String As String, Answer As Long)
Dim Customers As DUOSObjects
Dim Customer As DUOSObject

"customer?" Then
'The user is trying to save the record using the save dialog
If Answer = dcButton1 Then'The user clicked Save
Set Customers = DUOSObjectsGet("Customer Info")
Set Customer = Customers(CustomerID)
Customer.Properties("URL Address") = URLAddress
Customer.Properties("Contact E-Mail Address") = _
ContactEMailAddress
End If
End If
End Sub

A F T E R O P E N E V E N T
AfterOpen event
Description The AfterOpen event occurs when a window opens. It occurs after the
Microsoft Dynamics GP window open event.
Syntax window_AfterOpen()
Comments Microsoft Dynamics GP uses the window open event to set default field
values in the window, such as a default document date or a sort list
selection.
Since the AfterOpen event occurs after the Microsoft Dynamics GP open
event, use this event to override any default values that the accounting
system sets for window fields.
Examples In this example, the AfterOpen event procedure for the Sales Territory
Maintenance window marks two check box controls when the window
opens, overriding the default values that the accounting system sets in its
open event:

'Set both check boxes when the window opens
MaintainHistory = 1
End Sub

The window objects Open method.
B E F O R E A C T I V A T E E V E N T
BeforeActivate event
Description The BeforeActivate event occurs when a window is activated. It occurs
before the Microsoft Dynamics GP window activate event.
Syntax window_BeforeActivate()
Comments A window is activated when its moved from the background to the
foreground in an application, becoming the frontmost window.
Microsoft Dynamics GP rarely uses the window activate event. Whether you
choose to use the AfterActivate event or BeforeActivate event is of little
consequence.
Examples See the example for the AfterActivate event.

The window objects Activate method.

B E F O R E C L O S E E V E N T
BeforeClose event
Description The BeforeClose event occurs when the window closes. It occurs before the
Microsoft Dynamics GP window close event.
Syntax window_BeforeClose(AbortClose As Boolean)
AbortClose As Boolean If True, this parameter stops the window from

closing, and stops the Microsoft Dynamics GP window close event from
occurring.
Comments Use this event is to cancel the window close if the contents in the window
dont meet certain criteria youve defined.
Examples In the following example, the BeforeClose event procedure for the Invoice
Entry window checks whether the user entered a comment ID. If not, it
displays a message dialog using VBAs MsgBox() function. If the user clicks
Yes, the procedure cancels the close using the AbortClose parameter, and the
user can enter a comment ID:
Private Sub Window_BeforeClose(AbortClose As Boolean)

If CommentID.Empty = True Then
Response = MsgBox("Do you want to enter a Comment?", vbYesNo)
AbortClose = True
CommentID.Focus
End If
End If
End Sub

The window objects Close method.
B E F O R E M O D A L D I A L O G E V E N T
Description The BeforeModalDialog event occurs when a modal dialog opens, but
before its displayed.
Syntax window_BeforeModalDialog(ByVal DlgType As Long, PromptString As

String, Control1String As String, Control2String As String, Control3String
As String, Answer As Long)
ByVal DlgType As Long Returns the dialog type. The following constants
specify the dialog type:
dtModalAskDialog An ask dialog. It contains one or more buttons, and
displays message text.
dtModalGetStringDialog A getstring dialog. It contains a data entry field and OK
and Cancel buttons.
PromptString As String The messages text. Since multiple dialogs can

appear for a single window, use the PromptString parameter to ascertain
which modal dialog appeared. You can also change the PromptString text
before Microsoft Dynamics GP displays the dialog.
Control1String As String...Control3String As String Returns the

corresponding button text in the modal dialog. You can also change the
buttons text before Microsoft Dynamics GP displays the dialog. For
getstring dialogs, use the Control3String to programmatically enter the text
in the data entry field.
Answer As Long A constant that specifies the buttons in the dialog:
dcButton1 The first button in an ask dialog.
dcButton2 The second button in an ask dialog.
dcButton3 The third button in an ask dialog.
dcCancel The Cancel button in a getstring dialog.
dcOK The OK button in a getstring dialog.

Comments Since the BeforeModalDialog event occurs before Microsoft Dynamics GP

displays the modal dialog, you can change the contents of the modal dialog.
To change the message text, set the PromptString parameter. To change the
button text, set the Control1String, Control2String and Control3String
parameters.
The AfterModalDialog event wont occur for all dialogs displayed in Microsoft
Dynamics GP. Dialogs that display a help button and whose title is Microsoft
Dynamics GP will function like standard window objects in your project, and will
not invoke modal dialog events when displayed.
Ask dialogs
The dtModalAskDialog constant of the DlgType parameter specifies an ask
dialog. Ask dialogs display one or more buttons and message text. The
following illustration shows an ask dialog and the corresponding
parameters in the BeforeModalDialog event:
PromptString
Control1String
The Answer parameter of the BeforeModalDialog event lets you

programmatically click a button, and dismiss the dialog automatically. To
answer the ask dialog, set the Answer parameter to dcButton1 (clicks the
first button), dcButton2 (the second button) or dcButton3 (the third button).
Getstring dialogs
The dtModalGetStringDialog constant of the DlgType parameter specifies a
getstring dialog. Getstring dialogs typically contain a message, a data entry
field, and OK and Cancel buttons:
PromptString
Control3String
Control1String
Control2String
The Answer parameter of the BeforeModalDialog event lets you

programmatically click a button and dismiss the dialog automatically. To
answer the getstring dialog, set the Answer parameter to dcCancel or dcOK.
Prior to answering the dialog, you can also set the Control3String data entry
field.
Examples In this example, the BeforeModalDialog event procedure

programmatically answers a dialog for the user. The dialog opens when the
user enters a nonexistent shipping method. Before the accounting system
can display this dialog, the procedure automatically clicks the Add
button, allowing the user to add the new shipping method:
Private Sub Window_BeforeModalDialog(ByVal DlgType As Long, _

If PromptString = "Do you want add this Shipping Method?" Then
'Click the first button, the Add button
Answer = dcButton1
End If
End Sub

B E F O R E O P E N E V E N T
BeforeOpen event
Description The BeforeOpen event occurs when a window opens. It occurs before the
Microsoft Dynamics GP window open event.
Syntax window_BeforeOpen(OpenVisible As Boolean)
OpenVisible As Boolean If True, the window opens invisibly.
Comments Microsoft Dynamics GP typically uses the window open event to set default
field values in the window, such as a default document date or a sort list
selection. You can use this event to set default field values in the window,
while still allowing default values set by the accounting system to override
your defaults.
Examples The following event procedure for the Customer Maintenance window
checks the IsLoaded property to ascertain whether the Reminders window
is open. If it is, the procedure sets the opening position of the Customer
Maintenance window so it appears to the right of the Reminders window:

If Reminders.IsLoaded = True Then
'The Reminders window is open
CustomerMaintenance.Left = Reminders.Left + 50
CustomerMaintenance.Top = Reminders.Top + 50
End If
End Sub

The window objects Open method.
C A P T I O N P R O P E R T Y
Caption property
Description The Caption property specifies the windows title thats displayed to the
user.
Syntax window.Caption [= string]
string The windows caption.
Comments Captions for data entry windows cannot exceed 80 characters. You cannot
change the caption for modal dialogs.
Windows modified using the Modifier include a period (.) at the beginning
of the windows caption. Windows that invoke VBA events include a
period at the end of the windows caption. These are visual indicators that
help technical support ascertain which windows youve modified. We
recommend you leave the period in the windows title.
Examples The following example sets the title when the window opens:

CustomerMaintenance.Caption = "Clients"
End Sub

The field objects Caption property.

C H A N G E D P R O P E R T Y
Changed property
Description The Changed property indicates whether any non-button field values in
the window have changed.
Syntax window.Changed [= boolean]
boolean If True, a non-button field value in the window changed.
Comments A fields value changes when the user makes an entry in a field, or when
the fields value changes using VBA. In both of these instances, the
Changed property will return True for the current window.
The Changed property is useful for determining whether the contents of a

window changed, and performing an action based on those changes.
The Changed event for a field always runs whenever a new record is
displayed in a window (such as when the user is browsing records using
browse buttons). However, only the windows Changed property
ascertains whether the user actually modified the contents displayed in the
window.
Examples The following example displays a message containing the date and time
when a customer record was changed. This information could also be
added to the DUOS or to another database (such as Microsoft Access) and
stored with the customer record.

If CustomerMaintenance.Changed Then
'The user made a change to the current record.
MsgBox "This user record was last changed on " & Date & _
" at " & Time & "."
End If
End Sub

The grid objects Changed property.
C L O S E M E T H O D
Close method
Description The Close method closes an open window.
Syntax window.Close
Comments Use the Close method to close any open window in Microsoft Dynamics
GP (a window whose IsLoaded property is True). An open window may
not necessarily be visible.
The Close method invokes the VBA BeforeClose event and AfterClose
event, and the Microsoft Dynamics GP close event for the window.
Examples The following example uses the BeforeClose event to close the Customers
and Prospects lookup window when the Customer Maintenance window
closes:
Private Sub Window_BeforeClose()

If CustomersandProspects.IsLoaded = True Then
CustomersandProspects.Close
End If
End Sub

The window objects Open method, Activate method, BeforeClose event and
AfterClose event.

E V E N T M O D E P R O P E R T Y
EventMode property
Description The EventMode property specifies whether VBA window events occur for
the original or modified version of the window.
Syntax window.EventMode [= mode]
mode A constant specifying when events occur:
emOriginalOnly Window events occur only for the original version of
the window.
emModifiedOnly Window events occur only for the modified version of
the window.
emNever Window events dont occur for the window.
Comments If you modify a window using the Modifier, VBA window events will occur
for the modified window only if you set the EventMode property to
emModified. To change the EventMode property for the window object,
use the Visual Basic Properties window.
If you modify a window containing a grid (such as a lookup window), you

must change the EventMode property to emModifiedOnly for both the
window and grid objects. Window and grid events can then occur for both
objects.
period at the end of the windows caption.
Examples Typically, you set the windows EventMode property using the Visual Basic
Properties window. You can also set it through an event procedure, as
shown in the following example:

If CustomerMaintenance.Caption = ".CustomerMaintenance" Then
'This is a modified window. Shut off VBA events for this user
CustomerMaintenance.EventMode = emOriginalOnly
End If
End Sub

The grid objects EventMode property.
The report objects EventMode property.

H E I G H T P R O P E R T Y
Height property
Description The Height property specifies the height of the window (in pixels).
Syntax window.Height [= integer]
integer The height of the windows client area, measured in pixels.
Comments The Height property specifies only the space within the windows client
area. The client area is the window less the windows title bar.
Examples This example uses the Height property to set the height of the Invoice Entry
window:
Private Sub Window_BeforeOpen

'Set the height to 500 pixels
InvoiceEntry.Height = 500
End Sub

The window objects Top property, Left property and Width property.
H I D E M E T H O D
Hide method
Description The Hide method makes an open window invisible.
Syntax window.Hide
Comments Use the Hide method to make any open window invisible. While invisible,
the window is open (its IsLoaded property is True) and data in the window
is still accessible. Use this method when you want to reference data
displayed in a window without making the window visible. You can also
make a window invisible using its Visible property, or by using the
OpenVisible parameter of the windows BeforeOpen event.
Examples The following example compares a transaction amount a user enters in the
Receivables Transaction Entry window with the batch limit displayed in an
invisible Receivables Batch Entry window:

'Open the window and make it invisible
ReceivablesBatchEntry.Hide
'Compare the batch total to the transaction amount entered
If CCur(SalesAmount)>CCur(ReceivablesBatchEntry _
.BatchTotal) Then
MsgBox "Amount exceeds batch limit."
BatchID.Focus
End If
'Close the window
End If
End Sub

The window objects Visible property, IsLoaded property, Show method and
BeforeOpen event.

I S L O A D E D P R O P E R T Y
IsLoaded property
Description The IsLoaded property returns whether the window is loaded (opened). A
window can be loaded, but not visible.
Syntax window.IsLoaded[= boolean]
boolean If True, the window is loaded.
Comments Use the IsLoaded property when you want to be sure a window is
available, either visibly or invisibly. If you want to check only for the visible
version of a window, use the windows Visible property.
When you open a window, Microsoft Dynamics GP implicitly open all the
windows in the form invisibly, then displays the first window in the form
(the parent window). The child windows in the form remain invisible, but
loaded. You can use the Show method to selectively display these child
windows without explicitly opening them.
Examples The following event procedure runs when the Customer Maintenance
window closes. It closes the Customers And Prospects lookup window if
its loaded:
Private Sub CustomerMaintenance_AfterClose()

End If
End Sub

The window objects Open method and Visible property.
L E F T P R O P E R T Y
Left property
Description The Left property specifies the horizontal position of the window (in
pixels).
Syntax window.Left [= integer]
integer The distance the windows left border is from the left border of the
main Microsoft Dynamics GP window, measured in pixels.
Examples In the following example, the event procedure uses the Left property to
open the Customer Maintenance window at a specified position:

CustomerMaintenance.Left = 100
CustomerMaintenance.Top = 100
End Sub

The window objects Height property, Top property and Width property.

M O V E M E T H O D
Move method
Description The Move method changes the position of a window.
Syntax window.Move([left [, top [, width [, height]]]])
left An integer specifying the distance (in pixels) from the left edge of the
window to the left edge of the application border.
top An integer specifying the distance (in pixels) from the top edge of the
main Dynamics GP windows client area. The client area is the window area
less the windows title bar.
width An integer specifying the width (in pixels) of the window.
height An integer specifying the height (in pixels) of the windows client
area.
Comments You can use named arguments for the Move method, or specify arguments
by position. If you use positional arguments, enter each in the order shown,
using commas and empty string values ("") to indicate the relative position
of arguments you dont specify.
Examples The following example uses named arguments to move the left position of
and the top position of the window:

InvoiceEntry.Move Left:=200, Top:=150
End Sub
The following example positions the Sales Prospects Maintenance window

using positional arguments. It sets only the first two parameters:

CustomersandProspects.Move 200,200,"",""
End Sub

The window objects Left property, Height property, Top property and
Width property.
The field objects Move method.
N A M E P R O P E R T Y
Name property
Description The Name property specifies the internal name VBA uses to reference a
window.
Syntax window.Name
Comments You cannot set the Name property at runtime. We recommend that you
change a windows Name property using the Visual Basic Properties
window. Be sure to replace all referenced occurrences of the window with
the new name.
Use the Name property to change the window name when you need to
resolve naming conflicts between windows and other objects in your
application. Naming conflicts typically arise between names in your project
and reserved words in VBA.
You can also use the Name property when you want to make an windows
name more readable in VBA code.
Examples To change a windows Name property, use the Visual Basic Properties
window.

The field objects Name property.
The grid objects Name property.
The report objects Name property.

O P E N M E T H O D
Open method
Description The Open method opens a window.
Syntax window.Open
Comments There are two ways of opening Microsoft Dynamics GP windows in VBA:
Use the Open method to open windows that initially appear empty,
with no existing record displayed.
Programmatically click a navigational control to open windows that

display existing information, such as lookup windows. The application
code attached to a navigational control (such as the lookup button) pre-
pares the window to display existing data correctly. Clicking these
controls ensures that this processing occurs.
If you use the Open method in your VBA code to open a window, but the
window cannot be opened, a VBA exception will be thrown. You can
handle this exception using the On Error statement in VBA.
Examples The following procedure opens the Receivables Transaction Entry window
when using the Open method when the user initially logs into the
accounting system.

On Error GoTo ErrorHandler
ReceivablesTransactionEntry.Open
End If
Exit Sub
ErrorHandler:
MsgBox Receivables Transaction Entry could not be opened.
End Sub
O P E N M E T H O D
The following procedure clicks the lookup button to display the Shipping
Methods lookup window:

'No shipping method specified. Click the lookup button
LookupButtons = 1
End If
End Sub

The window objects Close method, IsLoaded property, BeforeOpen event and
AfterOpen event.

P U L L F O C U S M E T H O D
PullFocus method
Description The PullFocus method removes the focus from a window and specifies
whether data for the currently-focused field is valid.
Syntax window.PullFocus
Return value A boolean indicating whether the method succeeded in pulling the focus
from the window:
Value Description
True The focus was pulled from the window. Microsoft Dynamics GP field
events (user changed and lost focus) verified that the focused field
contained valid data.
False The focus was not pulled from the window. Microsoft Dynamics GP
field events determined that the focused field contained invalid data,
then displayed a message dialog.
Comments Use the PullFocus method with windows youre programmatically

controlling through VBA. This includes using VBA to open the window, set
window fields, then close the window.
You cannot use the PullFocus method with a window where VBA window events
or window field events are occuring. If you do, a VBA error will occur.
The primary use of the PullFocus method is to check whether the currently-
focused field contains valid data. The accounting system verifies data in
each field when the focus moves out of the field. However, when youre
controlling a window remotely, the focus remains in the last field youve
set using VBA, and the accounting system cannot verify its contents. To
manually verify the contents of this field, use the PullFocus method.
The PullFocus method moves the focus off the window, which runs the
Microsoft Dynamics GP user changed and lost focus events for the focused
field. The accounting system uses these field events to verify the contents of
the field. If the field contains invalid data, a message dialog will appear and
the PullFocus method will return False. If the focused field contains valid
data, the PullFocus method will return True.
P U L L F O C U S M E T H O D
We recommend that you use the PullFocus method just prior to

programmatically clicking the windows Save button. This allows you to
conditionally save the contents of the window if the focused field contains
valid data.
Examples The following procedure runs when the user clicks a button in a VBA user
form. It saves the contents of the Receivables Transaction Entry window by
programmatically clicking the Save button. In this case, the save occurs
even though the user entered a non-existent shipping method in the
currently focused field in the window (Shipping Method). No warning
dialog appeared, and the partial shipping method wasnt saved:

ReceivablesTransactionEntry.Save = 1
ReceivablesTransactionEntry.Close
End Sub
Using the PullFocus method, the same example can conditionally save the
contents of the window only if data in the focused field is valid. In this case,
when the PullFocus method moves the focus out of the Receivables
Transaction Entry window, the Microsoft Dynamics GP user changed and
lost focus events verify the currently-focused field (Shipping Method). If
the field contains invalid data, the PullFocus method returns False, and the
save isnt performed:

If ReceivablesTransactionEntry.PullFocus = True Then
ReceivablesTransactionEntry.Save = 1
ReceivablesTransactionEntry.Close
End If
End Sub

R E Q U I R E D P R O P E R T Y
Required property
Description The Required property ascertains whether the user entered data in all
fields whose Required property is True.
Syntax window.Required [= boolean]
boolean If True, the user entered data in all required fields.
Comments Required fields are those in which an entry is necessary to store the record
properly. You can make additional fields required using the field objects
Required property.
Use the window objects Required property when saving data objects to
the Dynamic User Object Store (DUOS). Since the accounting system wont
permit the user to save a record in a window without entering all required
fields, checking the Required property from VBA lets you save the DUOS
data object only when the accounting system permits the save.
Examples In the following example, an event procedure for the save button saves
DUOS data objects in the Customer Maintenance window only if the user
entered all required fields (the Required property is True):

If CustomerMaintenance.Required = True Then

'The user entered all required fields. Create/get the collection
'Create the object, using the customer ID as the object ID
'Set the properties in the collection
End If
End Sub
S H O W M E T H O D
Show method
Description The Show method displays a window thats open, but invisible.
Syntax window.Show
Comments A window can be open, but still invisible. To check whether a window is
open, but not necessarily visible, use the windows IsLoaded property.
You can make a window invisible using the windows Visible property, the
windows Hide method, or the OpenVisible parameter of the windows
BeforeOpen event.
When you open a window, the accounting system implicitly opens all the
loaded. You can use the Show method to selectively display these child
windows without explicitly opening them.
Examples The following example shows a window thats open, but invisible. In this
case, the invisible window (Customer Maintenance Options) is from the
same form as the parent window (Customer Maintenance) from which this
event procedure is run:
Private Sub Country_AfterUserChanged()

If Country <> USA Then
MsgBox "Please choose a currency ID."
CustomerMaintenanceOptions.Show
CustomerMaintenanceOptions.CurrencyID.Focus
End If
End Sub

The window objects Hide method, Visible property and BeforeOpen event.

T O P P R O P E R T Y
Top property
Description The Top property specifies the vertical position of the window.
Syntax window.Top [= integer]
integer The distance from the top of the main Microsoft Dynamics GP
windows client area, measured in pixels.
Examples In the following example, the event procedure ascertains the position of the
Reminders window, then uses the Top property to align the top border of
the Customer Maintenance window with the top border of the Reminders
window:

If Reminders.Visible = True Then
'The Reminders window is open and visible
CustomerMaintenance.Top = Reminders.Top
End If
End Sub

The window objects Left property, Height property and Width property.
V I S I B L E P R O P E R T Y
Visible property
Description The Visible property specifies whether an open window is visible.
Syntax window.Visible [= boolean]
boolean If True, the window is visible. If False, the window is invisible.
Comments You can make any window invisible, provided its open (its
IsLoaded property is True). While invisible, data in the window is still
accessible. Use this property when you want to reference data displayed in
a window without making the window visible.
You can also make a window invisible using the Hide method or the
OpenVisible parameter of the windows BeforeOpen event.
When you open a window, the accounting system implicitly opens all the
loaded. You can use the Visible property to selectively display invisible
child windows without explicitly opening them.
Examples When the user enters a transaction amount in the Receivables Transaction
Entry window, the following event procedure compares the amount with
the maximum batch total in an invisible Receivables Batch Entry window:

'Open the Batch Entry window invisibly
ReceivablesBatchEntry.Visible = False
'Compare the batch total to the transaction amount entered
If CCur(SalesAmount)>CCur(ReceivablesBatchEntry _
.BatchTotal) Then
MsgBox "Amount exceeds batch limit."
BatchID.Focus
End If
'Close the window
End If
End Sub


The window objects Show method, Hide method and BeforeOpen event.
W I D T H P R O P E R T Y
Width property
Description The Width property specifies the width of a window (in pixels).
Syntax window.Width [= integer]
integer The width of the window, measured in pixels.
Examples The following event procedure runs when the Customer Maintenance
window opens. The event procedure checks if the Reminders window is
open, then uses the Width and Left properties for the Reminders window
to position the Customer Maintenance window to the right and below:

If Reminders.Visible = True Then
'The Reminders window is open
CustomerMaintenance.Left = Reminders.Left + 50
CustomerMaintenance.Top = Reminders.Top + 50
End If
End Sub

The window objects Show method, Hide method and BeforeOpen event.

Chapter 9: Field Object
Your project uses field objects to perform several tasks related to working
with fields in windows, grids and reports. The events, methods and
properties that apply to the field object are listed below. A detailed
explanation of each follows:
AfterGotFocus event
AfterLostFocus event
AfterUserChanged event
BeforeLostFocus event
BeforeUserChanged event
Caption property
Changed event
Empty property
Enabled property
Focus method
FocusSeg method
Height property
Left property
Locked property
Move method
Name property
Object property
Parent property
Required property
TabStop property
Top property
Value property
ValueSeg property
Visible property
Width property

A F T E R G O T F O C U S E V E N T
AfterGotFocus event
Description The AfterGotFocus event occurs when the user moves the focus into a field,
using the TAB key or the mouse. It occurs after the Microsoft Dynamics GP
got focus event.
Syntax field_AfterGotFocus()
Parameters field A window field object.
Comments Use the AfterGotFocus event to set or evaluate the contents of a field
gaining focus. Microsoft Dynamics GP rarely uses the got focus event.
When it does, the accounting system typically checks the value of the field
thats gaining focus, and performs calculations or sets other field values
based on that value.
Examples In the following example, the AfterGotFocus event for the Batch ID field
checks whether the field is empty when the user moves to it. If it is, the
event procedure opens the batch lookup window:

'The field is empty. Press the lookup button
LookupButton3 = 1
End If
End Sub
A F T E R L O S T F O C U S E V E N T
AfterLostFocus event
Description The AfterLostFocus event occurs when the user moves the focus out of a
field, using the TAB key or the mouse. It occurs after the Microsoft Dynamics
GP lost focus event.
Syntax field_AfterLostFocus()
Comments Use the AfterLostFocus event to evaluate the value of the field losing focus,
and perform any additional operations in the window. You cannot set the
value of the field losing focus using the AfterLostFocus event. This event
follows the Microsoft Dynamics GP user changed event, which is typically
used to verify the contents of the field.
The AfterLostFocus event occurs immediately after the Microsoft

Dynamics GP lost focus event. Microsoft Dynamics GP rarely uses the lost
focus event. When they do, they typically lock control fields (fields that
control the display of a record).
Examples In the following example, the AfterLostFocus event checks whether the
Payment Terms field is empty. If it is, it displays a VBA dialog that asks the
user if they want to enter one. If the user clicks Yes, the procedure opens the
Payment Terms Lookup window:
Private Sub PaymentTerms_AfterLostFocus()

If PaymentTerms.Empty = True Then
'Set a default payment term
Response = MsgBox("Do you want to enter a payment term?", _
vbYesNo)
'Click the payment term lookup button
LookupButtons = 1
End If
End If
End Sub

A F T E R U S E R C H A N G E D E V E N T
AfterUserChanged event
Description The AfterUserChanged event occurs when the user changes the contents of
a field, then moves the focus out of the field, using the TAB key or the
mouse. In fields that toggle, such as push buttons and visual switches, this
event occurs when the user clicks the field. For list fields, this event occurs
when the user selects an item in the list. In all instances, the
AfterUserChanged event occurs after the Microsoft Dynamics GP user
changed event.
Syntax field_AfterUserChanged()
Comments Use the AfterUserChanged event to evaluate the value in the field losing
focus. You cannot set the value of the field losing focus using the
AfterUserChanged event. This event occurs after the Microsoft Dynamics
GP user changed event, which is used to verify the contents of the field.
Examples The following example uses the AfterUserChanged event to check the
value of the Customer ID field in the Invoice Entry window. It disables the
Trade Discount field:

If CustomerID = "ADVANCED0002" Then
'Don't offer a trade discount
TradeDiscount.Enabled = False
End If
End Sub
B E F O R E G O T F O C U S E V E N T
Description The BeforeGotFocus event occurs when the user moves the focus to a field,
using the TAB key or the mouse. It occurs before the Microsoft Dynamics GP
got focus event.
Syntax field_BeforeGotFocus(CancelLogic As Boolean)
field A window field object.
CancelLogic As Boolean If True, the event cancels the Microsoft Dynamics

GP got focus event, and the VBA AfterGotFocus event.
Comments Use the BeforeGotFocus event to set or evaluate the contents of the field
gaining focus, and cancel any further got focus events for the field from
running (the Microsoft Dynamics GP got focus event and the VBA
AfterGotFocus event).
If Microsoft Dynamics GP uses its got focus event, it typically checks the
value of the field thats gaining focus, and performs calculations or sets
other field values based on that value. However, the accounting system
uses this event infrequently to do such operations.
Examples In the following example, the procedure checks whether the document type
is a return. If so, this procedure cancels the VBA AfterGotFocus event
procedure, which automatically opens a lookup window for the Batch ID
field:
Private Sub BatchID_BeforeGotFocus(CancelLogic As Boolean)

'The document type is a return. Dont use a batch
'Cancel the VBA AfterGotFocus event, which opens a lookup
CancelLogic = True
MsgBox "Post returns individually, not in a batch."
DocumentDate.Focus
End If
End Sub

B E F O R E L O S T F O C U S E V E N T
BeforeLostFocus event
Description The BeforeLostFocus event occurs when the user moves the focus out of a
field, using the TAB key or the mouse. It occurs before the Microsoft
Dynamics GP lost focus event.
Syntax field_BeforeLostFocus(KeepFocus As Boolean, CancelLogic As Boolean)
KeepFocus As Boolean If True, the focus returns to the current field.

GP lost focus event, and the VBA AfterLostFocus event.
Comments Use the BeforeLostFocus event to evaluate the value of the field losing
focus, and perform any additional operations in the window. You cannot
set the value of the field losing focus using the BeforeLostFocus event. This
event follows the Microsoft Dynamics GP user changed event, which is
used to verify the contents of the field losing focus.
The BeforeLostFocus event occurs immediately before the Microsoft

Dynamics GP lost focus event. The accounting system rarely uses its lost
focus event. When it does use this event, it typically locks control fields
(fields that control the display of a record).
Examples In the following example, the BeforeLostFocus event procedure runs for
the Number field (document number) in the Receivables Transaction Entry
window. Normally, the Microsoft Dynamics GP lost focus event locks this
field. In this case, the procedure cancels subsequent lost focus events, and
the Number field remains unlocked and editable:
Private Sub Number_BeforeLostFocus(KeepFocus As Boolean, _

CancelLogic = True
'Move the focus to the next field
Description.Focus = True
End Sub
B E F O R E U S E R C H A N G E D E V E N T
BeforeUserChanged event
Description The BeforeUserChanged event occurs when the user changes the contents
of a field, then moves the focus out of the field, using the TAB key or the
mouse. In fields that toggle, such as push buttons and visual switches, this
event occurs when the user clicks the field. For list fields, this event occurs
when the user selects an item in the list. In all instances, the
BeforeUserChanged event occurs before the Microsoft Dynamics GP user
changed event.
Syntax field_BeforeUserChanged(KeepFocus As Boolean, CancelLogic As Boolean)
KeepFocus As Boolean If True, the focus returns to the current field.

GP user changed event, and the VBA AfterUserChanged event.
Comments Use the BeforeUserChanged event to set or evaluate the value of field
thats losing focus. You can also use this event to bypass, or cancel, the
Microsoft Dynamics GP user changed event that occurs for the field.
For many data entry fields, the Microsoft Dynamics GP user changed event
verifies the value entered in the field. For push buttons, such as a Save or
Delete button, the user changed event saves or deletes the record displayed
in the window.
Use caution when canceling a data entry fields user changed events using the
BeforeUserChanged event. Canceling the Microsoft Dynamics GP user changed
event for these fields inhibits the accounting systems ability to verify the contents
of the field.

B E F O R E U S E R C H A N G E D E V E N T
Examples In the following example, the BeforeUserChanged event procedure runs

for the Invoice Entry windows Trade Discount field. Using the CancelLogic
parameter, it cancels processing for the Trade Discount field if the user
enters an amount greater than 4% of the invoice subtotal. It also uses the
KeepFocus parameter to place the focus in the same field, allowing the user
to enter a lower amount:
Private Sub TradeDiscount_BeforeUserChanged(KeepFocus As Boolean, _

If TradeDiscount > Subtotal * 0.04 Then
'The trade discount is greater than 4% of the subtotal
MsgBox "You cannot enter a discount greater than 4% of " + _
"the subtotal."
'Cancel the invoice calculation
CancelLogic = True
TradeDiscount.Empty = True
KeepFocus = True
End If
End Sub
C A P T I O N P R O P E R T Y
Caption property
Description The Caption property specifies the caption for a window field.
Syntax field.Caption [= string]
string The caption for the field.
Comments The following list explains the caption for each field type:
Field type Caption

String, composite, currency, integer, The text thats linked to the field.
long integer, date, time, text, list
box, drop-down list, multi-select list,
combo box
Check box The text thats linked to the check box group. If
the check box does not appear in a check box
group, or if theres no caption for the check box
group, the caption is the text for the individual
check box.
Push button, button drop list, visual The text appearing on the button face or switch.
switch The Caption property has no effect on a button
or visual switch with a picture.
Radio button The text thats linked to the radio button group. If
theres no caption for the radio button group, the
caption is the prompt for the individual radio
button.
If you make a caption longer than the existing caption, keep in mind that
you may need to resize or rearrange fields to view the entire caption.
Examples In the following example, the event procedure changes the caption for the
Customer ID field to Patient ID, then changes the windows caption:

'Set the field caption
CustomerID.Caption = "Patient ID"
'Set the window caption
CustomerMaintenance.Caption = "Patient Maintenance"
End Sub

C H A N G E D E V E N T
Changed event
Description The Changed event always occurs when a fields value changes.
Syntax field_Changed()
Comments The Changed event will always occur in the following instances:
When the user changes the field directly. This also activates the fields
BeforeUserChanged and AfterUserChanged events, as well as the
Microsoft Dynamics GP user changed event.
When Microsoft Dynamics GP application code updates the window

field.
When a fields value changes using an external tool, such as VBA.
Use the Changed event to execute VBA code for window fields that
Microsoft Dynamics GP updates. This occurs most often when the
accounting system retrieves a record from a table, then displays the records
contents in the window. The AfterUserChanged and BeforeUserChanged
events wont occur for a field in this case, since the accounting system, not
the user, changes the contents of the field.
Exercise caution when using the Changed event. In many cases, Microsoft
Dynamics GP causes the Changed event to occur numerous times for the same
field even though the value of the field may not visibly change. This will execute the
associated VBA event procedure each time the event occurs.
C H A N G E D E V E N T
Examples In the following example, the Changed event procedure runs for the
Document Date field. As the user browses records in the Receivables
Transaction Entry window, the accounting system sets window field values
for each record browsed. This procedure checks the value of the Document
Date field, and displays a message if the document is older than 90 days:

"Please post."
End If
End Sub

E M P T Y P R O P E R T Y
Empty property
Description The Empty property specifies whether a field contains a value.
Syntax field.Empty [= boolean]
boolean If True, the field is empty. If False, the field contains a non-zero
value.
Comments To clear a fields value, set the fields Empty property to True. You cannot
clear a field that the accounting system locked or disabled, but you can
clear fields youve locked or disabled using VBA.
VBA considers numeric fields empty if they contain a value of 0. String

fields are empty if they contain nothing or only spaces. Date fields are
empty when the date is 00/00/00. Time fields are empty when the time is
12:00:00 AM.
Examples The following example uses the Empty property to automatically open a
lookup window if the Salesperson ID field is empty:
Private Sub SalespersonID_AfterGotFocus()

If SalespersonID.Empty = True Then
'Click the lookup button to display the lookup window
LookupButton8 = 1
End If
End Sub
E N A B L E D P R O P E R T Y
Enabled property
Description The Enabled property specifies whether a window field is enabled. The
user cant change the contents of a disabled field.
Syntax field.Enabled [= boolean]
boolean If True, the field is enabled and editable. If False, the field is
disabled.
Comments A disabled field appears dimmed, along with its caption, the fields value,
and any related controls.
You can set the value of a field youve disabled using VBA. You cannot set
the value of a field disabled by the accounting system, nor can you enable
the field. For most windows, Microsoft Dynamics GP application code
disables and enables fields based on entries made by the user. You can
always return a disabled fields value.
Keep in mind that a disabled field is not the same as a locked field (a field
whose Locked property is True). If True, the Locked property makes the
field non-editable, but doesnt dim the fields value, prompt and related
controls.
Examples In the following example, the event procedure disables a field in the
Salesperson Maintenance window for a specific user:

If UserInfoGet.UserName = "LESSONUSER2" Then
'Disable the Commission Percent field for this user
Percent.Enabled = False
End If
End Sub

The field objects Locked property.

F O C U S M E T H O D
Focus method
Description The Focus method moves the focus to a field.
Syntax field.Focus([setvalue])
setvalue The value you can set for the field gaining focus.
Comments Use the Focus method to skip unnecessary fields in a window, or place the
focus in a specific field based upon a user entry. The Microsoft Dynamics
GP got focus event and the VBA BeforeGotFocus and AfterGotFocus
events occur when you move the focus to a field using the Focus method.
You cannot place the focus using a windows BeforeOpen or AfterOpen

event. By default, Microsoft Dynamics GP places the focus in the first field
in the tab sequence after these events occur.
Examples In the following example, the Focus method redirects the focus to the
Shipping Method field when the user moves out of the Customer ID field:

'Move the focus to the field.
ShippingMethod.Focus
End Sub
Using the setvalue parameter, the Focus method redirects the focus and sets
the value of the Shipping Method field:

'Move the focus to the Shipping method field, then set the value
ShippingMethod.Focus("UPS BLUE")
End Sub

The field objects FocusSeg method and ValueSeg property.
F O C U S S E G M E T H O D
FocusSeg method
Description The FocusSeg method moves the focus to a segment in a composite field.
Microsoft Dynamics GP account number fields are composite fields.
Syntax field.FocusSeg (index), [setvalue]
Parameters field A composite window field object.
index An integer specifying the segment youre moving the focus to.
setvalue The value you can set for the segment gaining focus.
Comments Use the FocusSeg method to move the focus to a composite segment from
another field in the window, or from one segment to the next within the
same composite.
You can use the setvalue of the FocusSeg method to set the value of a
segment gaining focus. Based on whether youre setting the value from
inside or outside the field, there are two primary ways to set segment
values:
If you set the segments value from outside the composite field (from
another fields event procedure), use the setvalue parameter of the
FocusSeg method to set the segments value. In this case, you can set
only one segments value.
If you set the segments value from inside the composite field (from
the composite fields BeforeGotFocus, AfterGotFocus or BeforeUser-
Changed events), you can use the ValueSeg method to set values for
each segment of the composite. Use the FocusSeg method to move the
focus to a segment, but not set the segments value.
Examples The following example sets an account number segment from outside the
Account field (using the Checkbook ID fields AfterUserChanged event).
The procedure moves the focus to the Account field, then sets the first
segment using the FocusSeg method:

'Move to the Account field and set the first segment
Account.FocusSeg (1), "100"
End Sub

F O C U S S E G M E T H O D
The following example sets account segments from inside the Account
field. In this case, the Account field already has the focus. The
ValueSeg property sets the first two segment values. The FocusSeg
method then moves the focus to the third segment:

'Set default payroll account segments
End If
End Sub

The field objects Focus method and ValueSeg property.
H E I G H T P R O P E R T Y
Height property
Description The Height property specifies the height of a window field (in pixels).
Syntax field.Height [= integer]
integer The height of the field, measured in pixels.
Comments For data entry fields, the default height is 20 pixels. For push buttons, such
as Save and Delete, the default height is 24 pixels.
List box and multi-select lists require 20 pixels per item to display the item
properly. Changing the height of drop lists and combo boxes does not
change the height of the list in the undropped position. Instead, changing
the height of these lists determines the height of the list in the dropped
position.
Examples In the following example, the event procedure changes the height of a list
box field in the Account Maintenance window so that it shows two items
rather than four:

'Change the list to display only two items
IncludeinLookup.Height = 36
End Sub

The field objects Left property, Top property, Width property and Move method.

Left property
Description The Left property specifies the horizontal position of a field (in pixels).
Syntax field.Left [= integer]
integer The distance from the fields left border to the windows left
border, measured in pixels. Your operating systems settings for the active
window border specifies the width of the border.
Comments The Left property moves the field and the fields caption. It does not move
any buttons associated with the field, such as a lookup button. You must
move those fields separately.
Setting the Left property to 0 will align the field with the left edge of the
window. However, the fields caption will move off the window area.
Examples In the following example, the event procedure runs when the Account
Maintenance window opens. It first hides the Budget button, then uses the
Left property to move the Currency button to the same position as the
Budget button:

'Hide the Budget button
Budget.Visible = False
'Move the Currency button to the left
CurrencyButton.Left = Budget.Left
End Sub

The field objects Top property, Width property, Height property and
Move method.
L O C K E D P R O P E R T Y
Locked property
Description The Locked property locks a field. The user cant change the value of a
locked field, but they can view data in the field.
Syntax field.Locked [= boolean]
boolean If True, the field is locked and not editable. If False, the field is not
locked.
Comments A locked field appears with a light gray background, indicating that the
user cant change the contents of the field.
You can set the value of a field youve locked using VBA. You cannot set the
value of a field locked by the accounting system, nor can you unlock a field
locked by the accounting system. Typically, Microsoft Dynamics GP
application code locks fields whose values are necessary to preserve the
integrity of accounting data, such as document totals. You can always
return a locked fields value.
Keep in mind that a locked field is not the same as a disabled field (a field
whose Enabled property is False). If False, the Enabled property makes the
field non-editable, and also dims the fields value, prompt and related
controls.
Examples The following event procedure runs when the Account Maintenance
window opens. It locks the Account Number field for a specific user:

Account.Locked = True
End If
End Sub

The field objects Enabled property.

M O V E M E T H O D
Move method
Description The Move method moves and resizes a window field.
Syntax field.Move ([Left [,Top [,Width [,Height]]]])
left An integer specifying the distance from the fields left border to the
windows border, measured in pixels. Your operating systems settings for
the active window border determines the width of the border.
top An integer specifying the distance from the fields top border to the
top edge of the windows client area, measured in pixels. The client area is
the area of the window, less the windows title bar.
width An integer specifying the width of the field (measured in pixels).
height An integer specifying the height of the field (measured in pixels).
Comments You can use named arguments for the Move method, or enter arguments by
position. If you use positional arguments, enter each in the order shown,
using commas and empty string values ("") to indicate the relative position
of arguments you dont specify. Any unspecified arguments remain
unchanged.
Examples The following example uses positional arguments to change the position of
a Customer ID field when the Customer Maintenance window opens:
CustomerID.Move 10, 10, 50, ""
End Sub
The following example uses named arguments to move the left position of
the field and change the width of the field:
'Set the left distance and the field width
CustomerID.Move Left: = 10, Width: = 70
End Sub

The field objects Left property, Top property, Width property and
Height property.
The window objects Move method.
Name property
window field or report field object.
Syntax field.Name
Parameters field A window field or report field object.
change a fields Name property using the Visual Basic Properties window.
Be sure to replace all referenced occurrences of the field with the new name.
Use the Name property to change the field name when you need to resolve
naming conflicts between fields and other objects in your application.
Naming conflicts typically arise between names in your project and
reserved words in VBA. For instance, if you add the Account Maintenance
windows Currency button to your project, you cant compile VBA code
referencing that field until you rename the field. Currency in VBA is a
reserved word.
You can also use the Name property to make a fields name more readable
in VBA code.
Examples Use the Visual Basic Properties window to change a fields Name property.

The window objects Name property.

O B J E C T P R O P E R T Y
Object property
Description The Object property returns a field object without the standard properties
and methods extended to it by Visual Basic.
VBA requires host applications to define an Object property within an object

model. For your applications, its unlikely that youll need to use this property.
Syntax field.Object [.property | .method]
[.property | .method] The Microsoft Dynamics GP custom property or

method for the field object youre referencing. This cannot be a standard
property or method assigned to it by VBA.
Comments Use the Object property to reference custom properties and methods
assigned to the field object exclusively for Microsoft Dynamics GP. For field
objects, custom properties and methods include:
Method/property Method/property
Caption property Locked property
Empty property Required property
Enabled property Value property (report and window fields)
FocusSeg method Visible property (report and window
fields)
In addition to custom properties and methods, VBA assigns each field

object standard properties and methods. (VBA sometimes calls these
extender properties and methods). In the field object library, these are the
methods and properties not shown in the above table. You cannot reference
VBAs standard properties and methods using the Object property.
The primary use of the Object property is to resolve naming conflicts

between custom properties and methods supplied by a VBA host
application for an object, and standard properties and methods supplied by
VBA for the same object. If a custom property or method supplied by a VBA
host application uses the same name as a standard property or method
supplied by VBA, VBA automatically uses the standard property or
method.
O B J E C T P R O P E R T Y
In these cases, the Object property allows you to bypass the VBA-supplied
standard property or method and use the identically-named property or
method defined by the host application.
Since there are no inherent naming conflicts with VBA methods and properties for
field objects, you dont need to use this property when working with field objects.
Examples The Object property is not relevant for field objects at this time. Refer to the
Visual Basic online help for additional information and examples of the
Object property.

P A R E N T P R O P E R T Y
Parent property
Description The Parent property returns a window or report object containing a
specified field object.
Syntax field.Parent
Comments Use the Parent property to access the methods or properties of a window or
report object containing a given field object. This is especially useful if
youre passing field objects to procedures as arguments. In these cases, you
can use the Parent property to obtain information about the window or
report containing the field object you passed to the procedure.
Examples In the following example, two procedures illustrate how to use the Parent
property. The first procedure uses the Call statement to call a sub procedure
named FieldCaption after a Microsoft Dynamics GP window opens. It
passes the windows Customer ID field as an object to the procedure.
The second procedure is a new sub procedure defined for the module. It
receives the Customer ID field object passed from the first procedure. The
procedure then uses the Parent property to ascertain the name of the
window where the field was passed from, and changes the fields caption
based on the windows name:

'Pass a window field to the FieldCaption procedure
Call FieldCaption(CustomerID)
End Sub
--------------------------------------------------------------------
Public Sub FieldCaption(FieldObj As Object)
If FieldObj.Parent.Name = "CustomerMaintenance" Then
CustomerMaintenance.CustomerID.Caption = "Customer No."
ElseIf FieldObj.Parent.Name = "InvoiceEntry" Then
InvoiceEntry.CustomerID.Caption = "Cus. No."
End If
End Sub
R E Q U I R E D P R O P E R T Y
Required property
Description The Required property specifies whether the field must contain data before
the user can save information in the window.
Syntax field.Required [= boolean]
boolean If True, the field is required. If False, the field is not required.
Comments Microsoft Dynamics GP will prompt the user to enter data in a required
field if the field is empty when the user attempts to save the record. Fields
marked as required by VBA are displayed with the same caption, font style
and color as fields marked as required by the accounting system.
A field required by the

accounting system.
Fields made required by
VBA.
You cannot set the Required property to False for fields already marked as
required by the accounting system. These are fields necessary for the
system to store the record properly.
If you make a field required, be sure the field is enabled (its

Enabled property is True) and unlocked (its Locked property is False).
Examples The following example sets the Required property for the Phone 1 field in
the Customer Maintenance window:
Private Sub UserDefined1_AfterUserChanged()

If UserDefined1 = "RETAIL" Then
Phone1.Required = True
Elseif UserDefined1 = "WHOLESALE" Then
Phone1.Required = False
End If
End Sub

T A B S T O P P R O P E R T Y
TabStop property
Description The TabStop property specifies whether a field is in the windows tab
sequence.
Syntax field.TabStop [= boolean]
Parameters field A field object.
boolean If True, the field is in the windows tab sequence. If False, the field
is not in the tab sequence.
Comments The tab sequence is the order in which the focus moves through fields when
the user presses the TAB key. Removing a field from the tab sequence
bypasses the field when you press the TAB key. If you add the field back to
the sequence, it maintains its original order in the sequence.
Removing a rarely-used field from the tab sequence allows users to move
from field to field more efficiently. Once you remove a field from the tab
sequence, the user can still place the focus in the field using the mouse. This
setting doesnt affect the users ability to enter data in the field.
Since you cannot place the focus in hidden, locked or disabled fields, the
accounting system ignores these fields in the tab sequence.
Examples The following example removes three fields from the tab sequence in the
Invoice Entry window:

Hold.TabStop = False
BatchID.TabStop = False
CustomerPONumber.TabStop = False
End If
End Sub
Top property
Description The Top property specifies the vertical position of a field.
Syntax field.Top [= integer]
integer The distance from the fields top border to the top edge of the
windows client area, measured in pixels. The client area is the area of the
window, less the windows title bar.
Examples The following example uses the Top property and Left property to move
the Currency1 button field to the same window position as the invisible
Budget button field:

Budget.Visible = False
Currency1.Top = Budget.Top
Currency1.Left = Budget.Left
End Sub

The field objects Left property, Width property, Height property and
Move method.

V A L U E P R O P E R T Y
Value property
Description The Value property specifies the value of a window or report field. For
window fields, the Value property is a read/write property. For report
fields, the Value property is a read-only property unless the field is a user-
defined calculated field.
Syntax field.Value [= string_value]
string_value A string specifying the value of the field.
Comments If you omit the Value property from your code, VBA assumes youre
returning or setting the value of the field. The following example explicitly
uses the Value property:
BatchID.Value = "DEBITMEMOS"
The same code can also omit the Value property and be written like this:
The following table lists each field type for which you can set or return a
value using the Value property, as well as a description of the string value
used for the field type:
Field type Description

Button drop list A numeric value identifying the item selected in the list.
Check box The value 0 indicating an unmarked check box. The
value 1 indicating a marked check box.
Combo box The text of the item selected in the combo box.
Composite The value of the composite field, including any
formatting.
Currency A currency value for the field, including the decimal
separator.
Date The date value of the field, including any formatting.
Drop-down list A numeric value identifying the item selected in the list.
Integer The numeric value of the field, including any formatting.
List box A numeric value identifying the item selected in the list.
Long integer The numeric value of the field, including any formatting.
Field type Description

Multi-select list box A 32-bit numeric value identifying the selected items in
the list.
Push button The value 0 indicating the unpressed state of the push
button. The value 1 indicating the pressed state.
Radio group A numeric value identifying the radio button selected in
the group.
String The string value for the field, including any formatting.
Time The time value for the time field, including any
formatting.
Visual switch A numeric value identifying the item selected in the
visual switch.
Examples The following example sets the Sort By list field in the Customer
Maintenance window when the window opens:

'Set the Sort By list to "By Salesperson ID"
SortBy.Value = 5
End Sub
The following example sets the value of the Batch ID string field when the
user chooses a document type from the Document Type drop-down list:
Private Sub DocumentType_AfterUserChanged()

Select Case DocumentType
'Set the batch ID to one of three existing batches
Case 1
BatchID.Value = "DAILYSLS"
Case 7
BatchID.Value = "DAILYRET"
Case Else
BatchID.Value = "DAILYMISC"
End Select
End Sub

The following example checks the value of the Checkbook ID field, then
sets the value of the Cash Account composite field to an existing account
number. Note that the syntax omits the Value property:
Private Sub CheckbookID_Changed()

If CheckbookID="FIRST NATIONAL" And CashAccount.Enabled=True Then
CashAccount = "100-5100-00"
CashAccount.Enabled = False
ElseIf CheckbookID <> "FIRST NATIONAL" Then
CashAccount.Enabled = True
End If
End Sub

The field objects ValueSeg property and Empty property.
Additional information
Working with field values and Window field type reference in Chapter 3, Programming
Window Fields.
V A L U E S E G P R O P E R T Y
ValueSeg property
Description The ValueSeg property specifies the value of a segment in a composite
field.
Syntax field.ValueSeg (index) = [string_value]
Parameters field A composite window field object.
index An integer specifying the segment.
string_value A string specifying the value of the segment.
Comments Use the ValueSeg property to set or return segment values after the
composite gains focus (using the BeforeGotFocus, AfterGotFocus or
BeforeUserChanged events). The composite gains focus when the user
moves to the composite field, or when you programatically move the focus
using the Focus method or FocusSeg method.
Examples The following procedure moves the focus to the Cash Account field using
the FocusSeg method:
Private Sub CheckbookID_BeforeUserChanged(KeepFocus _

As Boolean, CancelLogic As Boolean)
End Sub
Once the Cash Account has focus, a BeforeGotFocus event procedure sets
the value of the segments in the composite using the ValueSeg property:
Private Sub CashAccount_BeforeGotFocus(CancelLogic As Boolean)

If CheckbookID = "CO. PAYROLL" Then
End If
End Sub

The field objects FocusSeg method.

Visible property
Description The Visible property specifies whether the field is visible.
Syntax field.Visible [= boolean]
Parameters field A window or report field object.
boolean If True, the field is visible. If False, the field is invisible.
Comments If you hide a window field using the Visible property, VBA hides both the
field and its caption. You can still return or set the values of fields you make
invisible with VBA. However, you cannot set the value of fields hidden by
the accounting system, nor can you show these fields.
Examples The following example hides sales fields when a user opens the Salesperson
Maintenance window:

CommissionedSales.Visible = False
CostofSales.Visible = False
NonCommissionedSales.Visible = False
TotalCommissions.Visible = False
End If
End Sub

The window objects Visible property and Hide method.
Events
The window objects BeforeOpen event.
W I D T H P R O P E R T Y
Width property
Description The Width property specifies the width of a field (in pixels).
Syntax field.Width [= integer]
Parameters field A field object.
integer Specifies the width of the field (measured in pixels).
Comments The Width property calculates the fields width starting at the left edge of
the field, and sizes the field to the specified width. The Width property
doesnt affect the fields caption.
Examples The following example changes the width of several fields in the Invoice
Entry window:

TradeDiscount.Width = 140
Freight.Width = 140
Miscellaneous.Width = 140
Tax.Width = 140
Total.Width = 140
End Sub

The field objects Left property, Top property, Height property and
Move method.

Chapter 10: Grid Object
Your project uses the grid object to perform several tasks related to working
with grids (scrolling windows). The events, methods and properties that
apply to the grid object are listed below. A detailed explanation of each
follows:
AfterLineChange event
AfterLineGotFocus event
AfterLineLostFocus event
BeforeLineChange event
BeforeLineGotFocus event
BeforeLineLostFocus event
BeforeLinePopulate event
Changed property
EventMode property
Hide method
Left property
Move method
Name property
Show method
Top property
Visible property

A F T E R L I N E C H A N G E E V E N T
AfterLineChange event
Description The AfterLineChange event occurs when the contents of a line change in an
editable or adds-allowed grid, and the focus moves out of the line. It occurs
after the Microsoft Dynamics GP line change event.
Syntax grid_AfterLineChange()
Parameters grid A grid object.
Comments Use the AfterLineChange event to perform other actions in the window
after the Microsoft Dynamics GP line change event. Microsoft Dynamics GP
uses the line change event to save data in the line when the user leaves the
line. An example of this is the Invoice Entry window, where each grid line
represents a separate transaction record in the invoice. As the user moves to
a new line, the line change event saves the invoice line item record to a
table.
Examples The following AfterLineChange event procedure checks the Subtotal field
in the Invoice Entry window when the user enters line item information in
the Invoice Entry grid. If the invoice subtotal is greater than $1000, it
assigns the transaction to an existing batch:

'Check the Invoice subtotal
If CCur(InvoiceEntry.Subtotal) > 1000 Then
'Assign an existing batch
InvoiceEntry.BatchID = "BIGSALES"
InvoiceEntry.BatchID.Locked = True
End If
End Sub
A F T E R L I N E G O T F O C U S E V E N T
AfterLineGotFocus event
Description The AfterLineGotFocus event occurs when the focus moves to a new line
in a grid. It occurs after the Microsoft Dynamics GP line got focus event.
Syntax grid_AfterLineGotFocus()
Comments Use the AfterLineGotFocus event to evaluate the contents of fields in the
line gaining focus.
Examples In the following example, the AfterLineGotFocus event checks the value of
the Item Number field in the Invoice Entry grid. If the field is empty, the
procedure opens the Items lookup window:
Private Sub Grid_AfterLineGotFocus()

If ItemNumber.Empty = True Then
'Open the lookup window
InvoiceEntry.LookupButton6 = 1
End If
End Sub

A F T E R L I N E L O S T F O C U S E V E N T
AfterLineLostFocus event
Description The AfterLineLostFocus event occurs when the focus moves out of a line. It
occurs after the Microsoft Dynamics GP line lost focus event.
Syntax grid_AfterLineLostFocus()
Comments Microsoft Dynamics GP rarely uses the line lost focus event. Whether you
choose the VBA AfterLineLostFocus or BeforeLineLostFocus event is of
little consequence.
Examples In this example, the AfterLineLostFocus event procedure shrinks the

grid in the Invoice Entry window when the user moves to the next line. To
do this, it programmatically clicks the grids expand button:
Private Sub Grid_AfterLineLostFocus()

InvoiceEntry.ScrollingWindowExpandButton = 1
End Sub
B E F O R E L I N E C H A N G E E V E N T
BeforeLineChange event
Description The BeforeLineChange event occurs when the contents of a line change in
an editable or adds-allowed grid, and the focus moves out of the line. It
occurs before the Microsoft Dynamics GP line change event.
Syntax grid_BeforeLineChange(KeepFocus As Boolean)
KeepFocus As Boolean If True, this parameter prevents the Microsoft

Dynamics GP line change event and the VBA AfterLineChange event from
occurring, and keeps the focus in the current line.
Comments Use the BeforeLineChange event to check the value of fields in a line, then
cancel subsequent line change events if criteria you specify arent met.
Examples In this example, the BeforeLineChange event checks the value of the
Markdown Amount field in the Invoice Entry grid. If the user attempts to
enter a markdown amount greater than 20%, the KeepFocus parameter stops
the line change event, and moves the focus back to the current line:
Private Sub Grid_BeforeLineChange(KeepFocus As Boolean)

If CCur(MarkdownAmount) > CCur(UnitPrice) * 0.2 Then
'The markdown was greater than 20%
KeepFocus = True
MsgBox "You cannot enter a markdown greater than 20% " + _
"of the unit price."
End If
End Sub

B E F O R E L I N E G O T F O C U S E V E N T
BeforeLineGotFocus event
Description The BeforeLineGotFocus event occurs when the focus moves to a new line
in a grid. It occurs before the Microsoft Dynamics GP line got focus event.
Syntax grid_BeforeLineGotFocus()
Comments Use the BeforeLineGotFocus event to evaluate the contents of fields in the
line gaining focus.
Microsoft Dynamics GP rarely uses the line got focus event, so whether you
choose the VBA AfterLineGotFocus or BeforeLineGotFocus event is of
little consequence.
Examples See the example for the AfterLineGotFocus event.
B E F O R E L I N E L O S T F O C U S E V E N T
BeforeLineLostFocus event
Description The BeforeLineLostFocus event occurs when the focus moves out of a line.
It occurs before the Microsoft Dynamics GP line lost focus event.
Syntax grid_BeforeLineLostFocus()
Comments Microsoft Dynamics GP rarely uses the line lost focus event. Whether you
choose the VBA AfterLineLostFocus or BeforeLineLostFocus event is of
little consequence.
Examples See the example for the AfterLineLostFocus event.

B E F O R E L I N E P O P U L A T E E V E N T
BeforeLinePopulate event
Description The BeforeLinePopulate event occurs each time the accounting system
displays a new line in a grid.
Syntax grid_BeforeLinePopulate(RejectLine As Boolean)
RejectLine As Boolean If True, the accounting system wont display the

current line in the grid.
Comments When Microsoft Dynamics GP initially displays a grid, the

BeforeLinePopulate event occurs repeatedly until the grid is filled. It also
occurs for each line displayed when the user displays new lines in the grid,
(typically, through scrolling up or down in the grid).
Use the BeforeLinePopulate event to selectively filter items from a grid.

When set to True, the RejectLine parameter prevents the current line from
appearing in the grid.
Examples The following event procedure displays only Illinois customers in the
Customers and Prospects lookup window:

If State <> "IL" Then
RejectLine = True
End If
End Sub
C H A N G E D P R O P E R T Y
Changed property
Description The Changed property indicates whether any non-button field values in a
grids line have changed.
Syntax grid.Changed [= boolean]
boolean If True, a non-button field value in a grids line changed.
Comments A grid line changes when the value changes in one of the lines fields. If this
occurs, the Changed property will return True for the current line (the line
with focus) in the grid.
The Changed property is useful for determining whether the contents of a

line changed, and performing an action based on those changes.
Examples The following example displays a message containing the date and time
when a line in a sales transaction record was changed. This information
could also be added to the DUOS or to another database (such as Microsoft
Access) and stored with the transaction record:

If SalesTransactionEntryDetail.Changed Then
MsgBox "This item changed on " & Date & " at " & Time & "."
End If
End Sub
Related items Properties and methods

The window objects Changed property.

EventMode property
Description The EventMode property specifies whether VBA grid events occur for the
original or modified version of the grid.
Syntax grid.EventMode [= mode]
emOriginalOnly Grid events occur only for the original version of the grid.
emModifiedOnly Grid events occur only for the modified version of the
grid.
emNever Grid events dont occur for the grid.
Comments If you use the Modifier to modify a window containing a grid (such as a
lookup window), VBA grid events will occur only if you set both the
windows and the grids EventMode property to emModifiedOnly.
Changing this property allows events to occur only for the modified
version of the window and the grid. To change the EventMode property for
the window object, use the Visual Basic Properties window.
period at the end of the windows caption. Grids have no caption.
Examples Typically, you set the grids EventMode property using the Visual Basic
If CustomersandProspects.Caption = ".Customers and Prospects." _
Then
'Shut off events for the window and the grid.
CustomersandProspects.EventMode = emOriginalOnly
CustomersandProspectsDetail.EventMode = emOriginalOnly
End If
End Sub

The window objects EventMode property.
The report objects EventMode property.
H I D E M E T H O D
Hide method
Description The Hide method makes a grid invisible.
Syntax grid.Hide
Comments Use the Hide method to make any grid in an open window invisible. While
invisible, data in the grid is accessible. Use this method when you want to
reference data displayed in the grid without making the grid itself visible,
or if you want to hide the contents of the grid from the user.
If you use the window objects Hide method to hide a window containing a
grid (such as a lookup window), the Hide method hides both the window
and the grid.
Examples The following example hides the grid on the Sales Transaction Entry
window when the window opens. The rest of the window (the windows
header fields, and the windows summary fields) are still visible:

SalesTransactionEntryDetail.Hide
End Sub

The grid objects Visible property and Show method.

Left property
Description The Left property specifies the horizontal position of the grid (in pixels)
relative to the left edge of the window containing the grid.
Syntax grid.Left [= integer]
integer The distance (in pixels) from the left edge of the grid to the left
edge of the windows border.
Comments The Left property will specify the distance to the left edge of the window
for the grid and any of the fields, prompts and controls associated with the
grid. These items are associated with the grid if theyre no further than one
pixel from the grids border, or if theyre one pixel from the edge of another
associated item.
Most grids in Microsoft Dynamics GP are positioned 8 pixels to the left of

the windows left edge.
Examples The following example positions the left edge of the grid 20 pixels from the
left edge of the window using the Left property:

CustomersandProspectsDetail.Left = 20
End Sub

The grid objects Top property and Move method.
M O V E M E T H O D
Move method
Description The Move method changes the position of a grid relative to the window
containing the grid.
Syntax grid.Move ([left [, top [, width [, height]]]])
left An integer specifying the distance (in pixels) from the left edge of the
grid to the left edge of the windows border.
top An integer specifying the distance (in pixels) from the top edge of the
grid to the bottom edge of the windows title bar.
width An integer specifying the width (in pixels) of the grid.
height An integer specifying the height (in pixels) of the grid.
Comments You can use named arguments for the Move method, or specify arguments
by position. If you use positional arguments, enter each in the order shown,
using commas and null string values ("") to indicate the relative position of
arguments you dont specify.
The Move method will move the grid and any of the fields, prompts and
controls associated with the grid. These items are associated with the grid if
theyre no further than one pixel from the grids border, or if theyre one
pixel from the edge of another associated item.
Examples The following example uses named arguments to change the height of the
grid when the Customers and Prospects lookup window opens:

CustomersandProspectsDetail.Move Height:= 300
End Sub
The following example positions the grid in the Customers and Prospects
lookup window using positional arguments. It sets only the first two
parameters:

CustomersandProspects.Move 10,20,"",""
End Sub

M O V E M E T H O D

The grid objects Top property and Left property.
Name property
grid object.
Syntax grid.Name
Comments The first portion of a grids name is the same as the name of the window
containing the grid. However, grid names include the word Detail at the
end of the name.
Use the Name property to change a grid name when you need to resolve
naming conflicts between grids and other objects in your application. You
can also use the Name property when you want to make an objects name
more readable in VBA code. Be sure to replace all referenced occurrences of
the window with the new name.
Examples To change a grids Name property, use the Visual Basic Properties window.

The fied objects Name property.

S H O W M E T H O D
Show method
Description The Show method makes visible any invisible grid.
Syntax grid.Show
Comments Use the Show method to make visible any grid thats currently invisible.
The Hide method and Visible property make a grid invisible.
Examples The following example shows a grid thats been hidden using either the
Hide method or the Visible property:

If UserInfoGet.UserID <> "LESSONUSER1" Then
SalesTransactionEntryDetail.Show
End If
End Sub

The grid objects Hide method and Visible property.
Top property
Description The Top property specifies the vertical position of the grid relative to the
bottom border of the windows title bar.
Syntax grid.Top [= integer]
integer The distance from the top of the grid to the bottom of the windows
title bar, measured in pixels. The top of the grid includes any of the fields,
prompts and controls associated with the grid.
Comments The Top property will move the grid and any of the fields, prompts and
controls associated with the grid. These items are associated with the grid if
theyre no further than one pixel from the grids border, or if theyre one
pixel from the edge of another associated item.
Examples The following example changes the top position of the grid so it now
appears below a new field, Sort By State, in the Customers and Prospects
lookup window:

CustomersandProspectsDetail.Top = SortByState.Top + _
SortByState.Height + 6
End Sub

The grid objects Left property and Move method.

Visible property
Description The Visible property specifies whether a grid is visible.
Syntax grid.Visible [= boolean]
boolean If True, the grid is visible. If False, the grid is invisible.
Comments While invisible, data in a grid is still accessible. Use this property when you
want to reference data displayed in the grid without making the grid
visible. You can also make a grid invisible using the Hide method.
Examples The following example hides the grid in the Sales Transaction Entry
window based on the current user:

SalesTransactionEntryDetail.Visible = False
End If
End Sub

The grid objects Show method and Hide method.
Chapter 11: Report Object
Your project uses the report object to perform several tasks related to
working with reports. The events, methods and properties that apply to the
report object are listed below. A detailed explanation of each follows:
BeforeAF event
BeforeAH event
BeforeBody event
BeforePF event
BeforePH event
BeforeRF event
BeforeRH event
Cancel method
End event
EventMode property
Legend property
Name property
Start event

B E F O R E A F E V E N T
BeforeAF event
Description The BeforeAF event occurs before each instance of the specified additional
footer prints.
Syntax report_BeforeAF(ByVal Level As Integer, SuppressBand As Boolean)
Parameters report A report object.
By Val Level As Integer The index of the additional footer the event will
occur for. Since a report may have more than one additional footer
(indicated by F1, F2 and so on), use the Level parameter to specify which
additional footer you want the event to occur for.
SuppressBand As Boolean If True, the instance of the specified additional

footer wont print and no VBA events will occur for it. Other portions of the
report wont be affected.
Comments Use the BeforeAF event to reference fields an additional footer. A report
may have none, one or several additional footers. Each prints when the data
in the field it is based on changes. Microsoft Dynamics GP uses additional
footers to display summary data, such as a total of all records in the reports
body.
If the report has only one additional footer, the BeforeAF event occurs only
for that additional footer, and you dont need to set a value for the Level
parameter.
Examples In the following example, the BeforeAF event procedure sets a user-defined
calculated field in the second additional footer:

As Boolean)
If Level = 2 Then
'Set a user-defined calculated field
Status = "Preferred"
End If
End If
End Sub
B E F O R E A H E V E N T
BeforeAH event
Description The BeforeAH event occurs before each instance of the specified additional
header prints.
Syntax report_BeforeAH(ByVal Level As Integer, SuppressBand As Boolean)
By Val Level As Integer The index of the additional header the event will
occur for. Since a report may have more than one additional header
(indicated on the report layout by H1, H2 and so on), use the Level
parameter to specify which additional header you want the event to occur
for.
SuppressBand As Boolean If True, the instance of the specified additional

header wont print and no VBA events will occur for it. Other portions of
the report wont be affected.
Comments Use the BeforeAH event to reference fields in an additional header. A

report may have none, one or several additional headers. Each prints when
the data in the field it is based on changes. If the report has only one
additional header, the BeforeAH event occurs only for that additional
header, and you dont need to set a value for the Level parameter.
Examples In the following example, the BeforeAH event procedure sets the Level
parameter to 2, indicating that the procedure runs for the second additional
header on a report. The procedure then checks the value of the Checkbook
ID field in the second additional header:
Private Sub Report_BeforeAH(By Val Level As Integer, SuppressBand _

As Boolean)
If Level = 2 Then
BankDepositPostingJournal.Cancel
End If
End If
End Sub

B E F O R E B O D Y E V E N T
BeforeBody event
Description The BeforeBody event occurs before each instance of the reports body
prints.
Syntax report_BeforeBody(SuppressBand As Boolean)
SuppressBand As Boolean If True, the current body record wont print, and
no events will occur for it. Other portions of the report wont be affected.
Comments Use the BeforeBody event to reference fields in a reports body. Microsoft
Dynamics GP uses the report body for the bulk of a report, which typically
is made up of table fields. A report prints the body repeatedly until all
records on the report have printed.
Examples The following example uses the BeforeBody event to return the value of the
Commissioned Sales field in the current body record of the RM Salesperson
Report. If a salespersons commissioned sales are less than $200,000, the
SuppressBand parameter stops the current body record from printing. The
result is that the report prints only records for salespeople whove exceeded
$200,000 in commissioned sales:

If CCur(CommissionedSalesToDate) < 200000 Then
SuppressBand = True
End If
End Sub
B E F O R E P F E V E N T
BeforePF event
Description The BeforePF event occurs before the reports page footer prints.
Syntax report_BeforePF(SuppressBand As Boolean)
SuppressBand As Boolean If True, the page footer wont print and no VBA
events will occur for it.
Comments Use the BeforePF event to reference fields in a reports page footer. Items in
the page footer are placed at the bottom of every report page. The page
footer often includes administrative information, such as the name of the
person running the report.
Examples In the following example, the BeforePF event sets a user-defined calculated
string field in the reports footer. It uses the VBA Time and Date functions
to compose a comment on the report:
Private Sub Report_BeforePF(SuppressBand As Boolean)

Comment = UserInfoGet.UserID + " printed this at " + str(Time) + _
" on " + str(Date)
End Sub

B E F O R E P H E V E N T
BeforePH event
Description The BeforePH event occurs before the reports page header prints.
Syntax report_BeforePH(SuppressBand As Boolean)
SuppressBand As Boolean If True, the page header wont print and no

events will occur for it.
Comments Use the BeforePH event to reference fields in a reports page header. Items
in the page header are placed at the top of every report page. Page number,
date and time fields are commonly placed in this section of a report.
Examples The following BeforePH event procedure suppresses the page header
based on the current user ID:
Private Sub Report_BeforePH(SuppressBand As Boolean)

SuppressBand = True
End If
End Sub
B E F O R E R F E V E N T
BeforeRF event
Description The BeforeRF event occurs before the reports report footer prints.
Syntax report_BeforeRF(SuppressBand As Boolean)
SuppressBand As Boolean If True, the report footer wont print and no

VBA events will occur for it.
Comments Use the BeforeRF event to reference fields in the report footer. Summary
information is often included in the report footer. If a page footer is also
included on the last page, the report footer will print before the page footer.
Examples The following BeforeRF event procedure runs for the RM Transaction
Inquiry report. If the current user is LESSONUSER1, the procedure hides
two fields in the report footer:
Private Sub Report_BeforeRF(SuppressBand As Boolean)

OriginalAmountSUMRF.Visible = False
CurrentAmountSUMRF.Visible = False
Else
OriginalAmountSUMRF.Visible = True
CurrentAmountSUMRF.Visible = True
End If
End Sub

B E F O R E R H E V E N T
BeforeRH event
Description The BeforeRH event occurs before the reports report header prints.
Syntax report_BeforeRH(SuppressBand As Boolean)
SuppressBand As Boolean If True, the report header wont print and no

VBA events will occur for it.
Comments Use the BeforeRH event to reference fields in the report header. Items in the
report header appear only on the first page of a report. If a page header is
also included on the first page, the report header will appear after the page
header.
Microsoft Dynamics GP typically uses fields in the report header that you
cant reference from the BeforeRH event; such as system variables that
show the page number, user ID and company name, and legend fields that
show the record ranges for the report. Microsoft Dynamics GP rarely uses
table fields or calculated fields in the report header.
Examples In the following example, the BeforeRH event sets a user-defined

calculated string field in the reports header. It uses the VBA Time and Date
function to compose a comment on the report:
Private Sub Report_BeforeRH(SuppressBand As Boolean)

Comment = UserInfoGet.UserID + " printed this at " + str(Time) + _
" on " + str(Date)
End Sub
C A N C E L M E T H O D
Cancel method
Description The Cancel method cancels a report from a report event.
Syntax report.Cancel
Comments The Cancel method stops the report from printing. If canceled from a report
band event, data from that band will print before the report stops. If the
report prints to the screen, the Cancel method automatically closes the
Screen Output window. The End event occurs after you cancel a report
using the Cancel method.
Examples The following example cancels a report from the reports

BeforeBody event:

If SalespersonID = "ERIN J." Then
RMSalespersonReport.Cancel
End If
End Sub

The report objects End event.

E N D E V E N T
End event
Description The End event occurs when a report finishes printing.
Syntax report_End()
Comments Use the End event to perform any clean-up of activities for the report,
launch other applications, or open and close other windows. The End event
will always run if a reports Start event occurs, including when a report is
canceled using the Cancel method.
Examples In the following example, the End event procedure launches Microsoft
Outlook after the RM Customer Report prints:
Private Sub Report_End()

Dim RetVal As Variant
Response = MsgBox("Do you want to launch MS Outlook?", _
vbYesNo)
RetVal = Shell("C:\Program Files\Microsoft Office\ + _
"Office\Outlook.exe", vbNormalFocus)
End If
End Sub

The report objects Cancel method.
Events
The report objects Start event.
EventMode property
Description The EventMode property specifies whether report events occur for the
original or modified version of the report.
Syntax report.EventMode [= mode]
emOriginalOnly Report events occur only for the original version of the
report.
emModifiedOnly Report events occur only for the modified version of the
report.
emNever Report events dont occur for the report.
Comments If you modify a report using the Report Writer, you must set the
EventMode property to emModified if you want VBA events to occur for
the modified report. To change the EventMode property for the report
object, use the Visual Basic Properties window.
Examples Typically, you set the reports EventMode property using the Visual Basic

RMCustomerReport.EventMode = emOriginalOnly
End If
End Sub

The window objects EventMode property.
The grid objects EventMode property.

L E G E N D P R O P E R T Y
Legend property
Description The Legend property specifies the value of a report legend.
Syntax report.Legend(index) [= string_value]
index An integer that corresponds to the legend fields array index.
string_value The value of the legend field.
Comments Legends are fields whose data is persistent throughout the report, and must
be passed to the report as it starts. You must use the Legend property in the
reports Start event to set or return the value of a legend field in a report.
Legend fields typically include information about the report, such as the
range of records the user chose for the report. The following illustration
shows legend fields in the RM Customer Report used to show the range of
customer records that print for the report.
This is the legends index.

The Legend property
references the legends
index, not the legend field.
You dont add a legend field to your project; instead, you use the Legend
propertys index parameter to refer to a specific legend field on the report.
Examples The following Start event procedure returns the value of the Customer
Class legend field using the fields index:

If RMCustomerReport.Legend(5) = "AARONFIT0001 - AARONFIT0001" Then
End If

The report objects Start event.
Name property
report object.
Syntax report.Name
change a reports Name property using the Visual Basic Properties window.
Be sure to replace all referenced occurrences of the report with the new
name.
Use the Name property to change the report name when you need to
resolve naming conflicts between reports and other objects in your
application. These conflicts typically arise between names in your project
and reserved words in VBA.
You can also use the Name property when you want to make an reports
name more readable in VBA code.
Examples To change a reports Name property, use the Visual Basic Properties
window.

The field objects Name property.

S T A R T E V E N T
Start event
Description The Start event occurs as the report starts to print, but before any data
actually prints.
Syntax report_Start()
Comments Use the Start event to set any report legends using the Legend property.
Legends are fields whose data is persistent throughout the report, and must
be passed to the report as it starts.
Examples The following example sets the value of a legend field from the Start event:

RMCustomerReport.Legend(2) = "Aging Period Amount"
End Sub

The report objects Cancel method.
Events
The report objects End event.
Chapter 12: VBAGlobal Object
Your project uses the VBAGlobal object to perform tasks related to the
Dynamic User Object Store (DUOS). It also provides a method to retrieve
the UserInfo object used to access information about the current user. The
methods that apply to the VBAGlobal object are listed below. A detailed
explanation of each follows:
DUOSObjectCombineID method
DUOSObjectExtractID method
DUOSObjectsGet method
UserInfoGet method

DUO SO B J E C T C O M B I N E ID M E T H O D
DUOSObjectCombineID method
Description The DUOSObjectCombineID method constructs a DUOS data object ID
using two string values.
Syntax DUOSObjectsCombineID(string1, string2)
Parameters string1 The string youre combining with string2.
string2 The string youre combining with string1.
Return value A combined string composed of string1 and string2.
Comments Data objects you define in the DUOS must have a unique object ID within a
collection. If you create a data object with an object ID that already exists in
the collection, the new data object will overwrite the existing object. To
avoid duplicate object IDs, create a unique ID using this method.
In most cases, you can assign the value of a Microsoft Dynamics GP control
field as the objects ID. A control field, such as a customer ID or a document
number, controls the display of a record in a window, and is a unique value
in the accounting system.
Examples The following procedure runs when the user clicks the Save button in the
Item Vendors Maintenance window. It uses the DUOSObjectsCombineID
method to combine the values of two window fields (Vendor ID and Item
Number) to construct a unique object ID:

Dim VendorCollection As DUOSObjects
Dim VendorObject As DUOSObject
Dim ObjectID As String
'Specify a vendors collection

Set VendorCollection = DUOSObjectsGet("Vendors")
'Combine two field values to create a unique object ID
ObjectID = DUOSObjectCombineID(VendorID, ItemNumber)
'Create the object, using the combined ID
Set VendorObject = Vendors.Item(ObjectID)
'Set the objects properties using window fields
VendorObject.Properties("Discount Quantity") = DiscountQuantity
VendorObject.Properties("Discount Percent") = DiscountPercent
End Sub
D U O S O B J E C T C O M B I N E I D M E T H O D

The VBAGlobal objects DUOSObjectExtractID method.

DUO SO B J E C T E X T R A C T ID M E T H O D
DUOSObjectExtractID method
Description The DUOSObjectExtractID method extracts two strings combined using
the DUOSObjectCombineID method.
Syntax DUOSObjectCombineID(objectID, string1, string2)
Parameters objectID A string constructed using the DUOSObjectCombineID

method.
string1 The string combined with string2 to construct the objectID.
string2 The string combined with string1 to construct the objectID.
Return value A boolean indicating whether the objectID was combined using the
DUOSObjectCombineID method. If True, objectID was combined.
Comments Use the DUOSObjectExtractID method to return the original string values
combined using the DUOSObjectCombineID method. Extracting an
object ID returns the original combined string values. This is useful if you
want to update DUOS data objects based on one of the original string
values.
D U O S O B J E C T E X T R A C T I D M E T H O D
Examples The following example uses a button on a VBA user form to loop through a
collection named Vendors. It uses the DUOSObjectExtractID method to
check whether each data objects objectID is combined. Any object with a
combined objectID uses an ID composed of the vendors ID and the vendor
type. If the vendor type (ventype) is PREFERRED, the procedure updates
the properties for the data object:

Dim VendorCollection As DUOSObjects
Dim VendorObject As DUOSObject
Dim ObjectID As String
Dim venID As String
Dim ventype As String
'Return a vendors collection

Set VendorCollection = DUOSObjectsGet("Vendors")
For Each VendorObject In VendorCollection

If DUOSObjectExtractID(VendorObject.ID, venID, ventype) _
= True Then
'This is a combined ID. Update with new discount info.
If ventype = "PREFERRED" Then
'Update the properties for this vendor
VendorObject.Properties("Discount Quantity") = "200"
VendorObject.Properties("Discount Percent") = "6.50"
End If
End If
Next
End Sub

The VBAGlobal objects DUOSObjectCombineID method.

DUO SO B J E C T S G E T M E T H O D
DUOSObjectsGet method
Description The DUOSObjectsGet method returns a DUOS collection for the current
company.
Syntax DUOSObjectsGet(collection_name)
Parameters collection_name A string specifying the collection youre working with. If

the specified collection_name doesnt exist for the current company, this
method creates it.
Return value A collection specified by collection_name.
Comments Use the DUOSObjectsGet method to specify a collection in the DUOS and
assign it to a DUOSObjects variable. For instance, the following example
returns a collection named Customers:

Set CustomerCollection = DUOSObjectsGet("Customers")
You can use the DUOSObjectsGet method to retrieve an existing collection

or create a new collection. In the following illustration, the
DUOSObjectsGet method returns an existing collection named Items.
DUOSObjectsGet("Items")
"Customers" "Vendors" "Items"

In this illustration, the Collection Collection Collection
DUOS contains three
collections.
If the collection_name specified does not exist, this method creates the
collection with that collection_name.
DUOSObjectsGet("Employees")
When the specified

"Customers" "Vendors" "Items" "Employees"
collection doesnt exist, Collection Collection Collection Collection
DUOSObjectsGet
creates an empty
collection.
Data stored in the DUOS is company-specific, so collections defined in

company A dont exist when youre accessing the DUOS in company B.
DUO SO B J E C T S G E T M E T H O D
Examples The following example returns an existing collection named

CustomerCollection using the DUOSObjectsGet method. Once the
collection is created, the procedure can add a data object using the
collections Item property, then assign properties and property values for
the data object:

'Return the collection

Set CustomerCollection to DUOSObjectsGet("CustomerCollection")
'Create a data object in the collection with a unique object ID
Set CustomerObject = CustomerCollection.Item("AARONFIT001")
'Create properties for this object
CustomerObject.Properties.Item("URL Address") = _
"www.fitzelectric.com"
CustomerObject.Properties.Item("Contact E-Mail Address") = _
"[email protected]"

U S E R I N F O G E T M E T H O D
UserInfoGet method
Description The UserInfoGet method returns a UserInfo object containing information
about the current user.
Syntax UserInfoGet(collection_name)
Parameters None
Return value The UserInfo object for the current user.
Examples The following example retrieves the UserInfo object, and then displays the
current companys name in a message box.
Dim UserInfoObj As UserInfo

Dim CompanyName As String
'Get the UserInfo object

Set UserInfoObj = VbaGlobal.UserInfoGet()
'Retrieve and display the company name

CompanyName = UserInfoObj.CompanyName
MsgBox CompanyName

The UserInfo objects CompanyName property, IntercompanyID property,
UserDate property, UserID property, UserName property, and
CreateADOConnection method.
Chapter 13: DUOSObjects Collection
Your project uses the DUOSObjects collection to perform several tasks
related to creating and maintaining a collection of objects in the Dynamic
User Object Store (DUOS). The methods and properties that apply to a
DUOSObjects collection are listed below. A detailed explanation of each
follows:
Exists property
Item property
Name property
Remove method
SortByExisting property

E X I S T S P R O P E R T Y
Exists property
Description The Exists property returns True if specified data object exists in a
collection.
Syntax DUOSObjects.Exists(objectID)
Parameters DUOSObjects A collection of data objects in the DUOS.
objectID The unique identifier for the data object in the collection.
Comments The Exists property is a read-only property. If the specified data object
exists, it will return True. Otherwise, it will return False.
Examples In the following example, the Changed event procedure runs for the Total
field when the user changes an invoice amount in the Invoice Entry
window. The procedure uses the Exists property to ascertain whether a
corresponding invoice object already exists in the collection. If it does exist,
the procedure updates it with the current system date using the VBA Date()
function:
Private Sub Total_Changed()

Dim InvoiceCollection As DUOSObjects
Dim InvoiceObject As DUOSObject
Set InvoiceCollection = DUOSObjectsGet("Invoices")

If InvoiceCollection.Exists(DocumentNumber) Then
'A data object for this invoice exists
'Set a property to indicate the user changed the total
InvoiceObject.Properties("Invoice Adjustment Date") = Date
End If
End Sub
I T E M P R O P E R T Y
Item property
Description The Item property returns a data object from a collection.
Syntax DUOSObjects.Item(objectID)
Comments The Item property is the default member of the DUOSObjects collection. If
you omit the Item property from your VBA code, the collection assumes
youre returning the data object for the specified collection. The following
example includes the Item property:
ItemCollection.Item("ITM001")
This example omits the Item property:
ItemCollection("ITM001")
form. It returns a collection named Item Info, then uses the Item property to
return a data object with an objectID matching the Item Number in the Item
Maintenance window. The Set statement assigns the returned data object to
an object variable named ItemObject. The Remove method then deletes the
object returned by the Item property:
Private Sub DeleteItem_Click()

Set ItemCollection = DUOSObjectsGet("ItemInfo")

'Specify a data object using a window field value
Set ItemObject = ItemCollection.Item(ItemMaintenance.ItemNumber)
ItemCollection.Remove(ItemMaintenance.ItemNumber)
End Sub

Name property
Description The Name property returns the name of a collection.
Syntax DUOSObjects.Name
Comments Use the Name property to identify the name of a collection object returned
by the DUOSObjectsGet method. You can use the Name property to
distinguish between multiple collections in the same procedure.
form. The Name property returns the name of the collection object returned
by the DUOSObjectsGet method:
Private Sub CommandButton_Click()

Dim Collection As DUOSObjects
If CustomerMaintenance.IsLoaded Then
Set Collection = DUOSObjectsGet("Customers")
Else
Set Collection = DUOSObjectsGet("Items")
End If
'Display either "Customers" or "Items"
MsgBox "The current collection is " + Collection.Name
End Sub

The VBAGlobal objects DUOSObjectsGet method.
R E M O V E M E T H O D
Remove method
Description The Remove method deletes a data object from a collection.
Syntax DUOSObjects.Remove(objectID)
form. The procedure loops through a collection named Item Info and checks
the Item Color property for each item. If the value is Red, the collections
Remove method deletes the data object:

Set ItemCollection = DUOSObjectsGet("Item Info")

'Delete the object
ItemCollection.Remove (ItemObject.ID)
End If
Next
End Sub

S O R T B Y E X I S T I N G P R O P E R T Y
SortByExisting property
Description The SortByExisting property specifies the property by which the collection
sorts objects.
Syntax DUOSObjects.SortByExisting [= property_name]
property_name The property used for the sort operation.
Comments Use the SortByExisting property to sort the objects in a collection by the
value of a given property. In the following example, the SortByExisting
property sorts the data objects in the Customers collection by the Date
Added property:
Collection Object Property name Property value

Name ID
Customers C001 Date Added 03/22/96
C005 Date Added 01/04/96
URL Address www.afitz.com
URL Address www.altonmfg.com
In this case, the items are sorted in ascending order starting with the most
recent date. If the property_name exists only for a subset of objects in the
collection, the collection will be restricted to that subset of objects. In the
following example, the SortByExisting method sorts by the URL Address
property:
Collection Object Property name Property value

name ID
Customers C005 Date Added 01/04/96
URL Address www.afitz.com
URL Address www.altonmfg.com
S O R T B Y E X I S T I N G P R O P E R T Y
Examples The following procedure runs when the user clicks a button added to the
Customer Maintenance window using the Modifier. It uses the
SortByExisting method to sort the CustomerCollection by the collections
Date Added property. It then creates a report file using the VBA Open
statement, and prints the objects ID, property names and property values
to the file using the VBA Print# statement. Only data objects that include
the Date Added property will be printed, and will be sorted by date:
Private Sub PrintByDateButton_AfterUserChanged()

Dim CustomerProperty As DUOSProperty
Dim CustomerProperties As DUOSProperties
'Sort the collection by the date the customer was added

CustomerCollection.SortByExisting = "Date Added"
'Create a text file for the report
Open "CustomerReport.txt" For Output As #1
For Each CustomerObject In CustomerCollection
Print #1, CustomerObject.ID
Set CustomerProperties = CustomerObject.Properties
For Each CustomerProperty In CustomerObject.Properties
Print #1, " " + CustomerProperty.Name + " - " + _
CustomerProperty.Value
Next
Next
End Sub

Chapter 14: DUOSObject Object
Your project uses the DUOSObject object to perform several tasks related to
creating and maintaining a data object in the Dynamic User Object Store
(DUOS). The properties that apply to the DUOSObject object are listed
below. A detailed explanation of each follows:
ID property
Properties property

I D P R O P E R T Y
ID property
Description The ID property returns an object ID for a DUOS data object.
Syntax DUOSObject.ID
Parameters DUOSObject A DUOS data object.
Comments The ID property is a read-only property. To set an object ID for a DUOS

data object, use the Item property for the DUOSObjects collection.
form. The procedure loops through the collection named Item Info and
checks the Item Color property for each item. If the value is Red, the
collections Remove method deletes the object indicated by the ID
property:


'Delete the object
ItemCollection.Remove (ItemObject.ID)
End If
Next
End Sub
P R O P E R T I E S P R O P E R T Y
Properties property
Description The Properties property returns a collection of properties for a DUOS data
object.
Syntax DUOSObject.Properties
Parameters DUOSObject A DUOS data object.
Comments You can use the Properties property in combination with the Item property
to specify a named property for the object. In most cases, this is the
preferred way to set or return a propertys value.
form. This example returns a collection of properties for the current data
object:

Dim ItemProperties As DUOSProperties

'Get properties for the object
ItemProperties = ItemObject.Properties
End Sub

Chapter 15: DUOSProperties Collection
Your project uses the DUOSProperties collection to perform several tasks
related to creating and maintaining properties for data objects in the
Dynamic User Object Store (DUOS). The methods and properties that apply
to the DUOSProperties collection are listed below. A detailed explanation of
each follows:
Count property
Exists property
Item property
Remove method

C O U N T P R O P E R T Y
Count property
Description The Count property returns the number of property objects in a properties
collection.
Syntax DUOSProperties.Count
Parameters DUOSProperties A collection of properties for a data object.
Comments The Count property is useful when you want to perform any DUOS
maintenance activities, such as removing unwanted properties, or adding
properties to a data object if it doesnt have the correct number of
properties.
Examples The following example uses the Count property to return the number of
properties for a given data object. If the number of properties is greater than
2, the procedure loops through the collection, and uses the Remove method
to delete properties other than Item Weight and Item Color:
Private Sub DeleteExtraProperties_Click()

Dim ItemProperty As DUOSProperty

Set ItemObject = ItemCollection(ItemNumber)
Set ItemProperties = ItemObject.Properties
If ItemProperties.Count > 2 Then

'There are too many properties for this object
'Remove any other than Item Weight and Item Color
For Each ItemProperty In ItemProperties
If Not ((ItemProperty.Name = "Item Weight") Or _
(ItemProperty.Name = "Item Color")) Then
ItemProperties.Remove (ItemProperty)
End If
Next
End If
End Sub
E X I S T S P R O P E R T Y
Exists property
Description The Exists property returns True if a property object exists in a properties
collection.
Syntax DUOSProperties.Exists(property_name)
property_name The property objects name.
Examples The following procedure runs for a button in a VBA user form. It uses the
Exists property to check whether the Item Color property exists for a given
data object. If the property doesnt exist, the procedure creates it using the
collections Item property:
Private Sub CheckItemColor_Click()

Set ItemCollection = DUOSObjectsGet("ItemCollection")

If ItemProperties.Exists("Item Color") = False Then

'This item has no color property
ItemProperties.Item("Item Color") = InputBox("Enter a " + _
"color for this item.")
'Set the window field
ItemColor = ItemProperties.Item("Item Color")
End If
End Sub

Item property
Description The Item property returns a property object from a properties collection.
Syntax DUOSProperties.Item(index)
index The property objects name (a string) or the position (an integer) of
the property object in the collection.
Comments If you reference the property position in the index, the position starts at 1 for
the first property in the data object. The order you added the property to
the data object determines the property objects position.
If you reference the property name in the index, and the name does not
exist, the Item property creates a property in the collection with that name.
The Item property is the default member of the DUOSProperties collection.

If you omit the Item property from your VBA code, the collection assumes
youre returning the property for the specified properties collection. The
following example includes the Item property:
ItemProperties.Item("Item Color")
This example omits the Item property:
ItemProperties("Item Color")
form. It loops through a properties collection and uses the Item property to
check the property named Item Weight:
Private Sub UpdateItemLocation_Click()

Set ItemCollection = DUOSObjectsGet("ItemCollection")

If ItemProperties.Item("Item Weight") > "100.00" Then
'The item is greater than 100 pounds
ItemProperties.Item("Storage Location") = _
"Bulk Item Area"
End If
Next
Next
End Sub
In this example, the Item property references the position of the property
rather than the name:


'Get properties for the object
ItemObject.Properties(3) = "3.5"
End Sub

R E M O V E M E T H O D
Remove method
Description The Remove method deletes a specified property object from a properties
collection.
Syntax DUOSProperties.Remove(index)
index The property objects name (a string) or the position (an integer) of
the property object in the collection.
form. It removes a property object from a properties collection using the
Remove method:
Private Sub RemoveColorProperty_Click()


If ItemProperties.Exists("Item Color") Then

ItemProperties.Remove("Item Color")
End If
End Sub
Chapter 16: DUOSProperty Object
Your project uses the DUOSProperty object to perform tasks related to a
property for an object in the Dynamic User Object Store (DUOS). The
properties that apply to the DUOSProperty object are listed below. A
detailed explanation of each follows:
Name property
Value property

Name property
Description The Name property specifies the name of a property for a data object.
Syntax DUOSProperty.Name
Parameters DUOSProperty A property object within a properties collection.
form. It uses the Name property with the DUOSProperties Remove
method to delete properties for a data object other than Item Weight and
Item Color:
Private Sub DeleteExtraProperties_Click()


'Remove properties other than Item Weight and Item Color

If Not ((ItemProperty.Name = "Item Weight") Or _
(ItemProperty.Name = "Item Color")) Then
ItemProperties.Remove (ItemProperty)
End If
Next
End Sub
Value property
Description The Value property specifies the value of a property object.
Syntax DUOSProperty.Value [= string_value]
Parameters DUOSProperty A property object within a properties collection.
string_value A string that specifies the value of a property object.
Comments When you set the value of a property object using the Value property, you
cannot exceed 132 characters. The DUOS stores and returns property values
as strings.
The Value property is the default member of the DUOSProperty object. If

you omit the Value property from your VBA code, the object assumes
youre returning the value of the specified property object. The following
example includes the Value property:
ItemProperty.Value = "Red"
This example omits the Value property:
ItemProperty = "Red"

Examples The following example runs when the user clicks a button in a VBA user
form. The procedure loops through a collection named Item Info and uses
the Value property to set the value of the Item Color property for all data
objects:
Private Sub UpdateItemColor_Click()

'Update the item color for all objects in the collection

For Each ItemProperty In ItemObject.Properties
If ItemProperty.Name = "Item Color" Then
ItemProperty.Value = "Red"
End If
Next
Next
End Sub

The field objects Value property.
Chapter 17: UserInfo Object
The UserInfo object contains information about the user currently logged
into Microsoft Dynamics GP. The properties and method that apply to the
UserInfo object are listed below. A detailed explanation of each follows:
CompanyName property
CreateADOConnection method
IntercompanyID property
UserDate property
UserID property
UserName property

C O M P A N Y N A M E P R O P E R T Y
CompanyName property
Description The CompanyName property contains the name of the company that the
user is currently logged into in Microsoft Dynamics GP.
Syntax UserInfo.CompanyName
Parameters UserInfo A UserInfo object.
Examples The following example retrieves and displays the name of the company the
user is currently logged into.
Private Sub CompanyName_Click()

Dim CompanyName As String

'Retrieve and display the company name

CompanyName = UserInfoObj.CompanyName
MsgBox CompanyName
End Sub
C R E A T E A D O C O N N E C T I O N M E T H O D
CreateADOConnection method
Description The CreateADOConnection method creates a new ADO connection to the
database.
Syntax UserInfo.CreateADOConnection()
Examples The following example creates an ADO connection and issues a command
to retrieve all of the customer records from the RM00101 table in the current
companys database. Note how the IntercompanyID property of the
UserInfo object is used to set the default database for the ADO connection.
Private Sub CreateADOConnection_Click()

Dim cn As New ADODB.Connection
Dim rst As New ADODB.Recordset
Dim cmd As New ADODB.Command
On Error Resume Next
'Retrieve an ADO connection for the current user

Set cn = UserInfoGet.CreateADOConnection()
'Set the connection properties

cn.CursorLocation = adUseClient
'Set the current database, using the IntercompanyID property

cn.DefaultDatabase = UserInfoGet.IntercompanyID
'Create a command to select all customers

cmd.ActiveConnection = cn
cmd.CommandType = adCmdText
cmd.CommandText = "Select * from RM00101"
Set rst = cmd.Execute
'Display the number of rows retrieved

MsgBox rst.RecordCount
'Close the connection

cn.Close
End Sub

I N T E R C O M P A N Y I D P R O P E R T Y
IntercompanyID property
Description The IntercompanyID property contains the internal ID of the company that
the user is currently logged into in Microsoft Dynamics GP.
Syntax UserInfo.IntercompanyID
Comments The value of the IntercompanyID property is the same as the name of the
SQL database used for that company.
Examples The following example retrieves and displays the intercompany ID for the
company the user is currently logged into.
Private Sub IntercompanyID_Click()

Dim IntercompanyID As String

'Retrieve and display the intercompany ID

IntercompanyID = UserInfoObj.IntercompanyID
MsgBox IntercompanyID
End Sub
U S E R D A T E P R O P E R T Y
UserDate property
Description The UserDate property contains the user date currently set in Microsoft
Dynamics GP.
Syntax UserInfo.UserDate
Examples The following example retrieves and displays the user date currently set in
Microsoft Dynamics GP.
Private Sub UserDate_Click()

Dim UserDate As Date

'Retrieve and display the user date

UserDate = UserInfoObj.UserDate
MsgBox "Current date is: " + Str(UserDate)
End Sub

U S E R I D P R O P E R T Y
UserID property
Description The UserID property contains the user ID value for the user currently
logged into Microsoft Dynamics GP.
Syntax UserInfo.UserID
Comments The value of the UserID property is the same as the users SQL login.
Examples The following example retrieves and displays the user ID for the user
currently logged into Microsoft Dynamics GP.
Private Sub UserID_Click()

Dim UserID As String

'Retrieve and display the user ID

UserID = UserInfoObj.UserID
MsgBox UserID
End Sub
U S E R N A M E P R O P E R T Y
UserName property
Description The UserName property contains the display name for the user currently
logged into Microsoft Dynamics GP.
Syntax UserInfo.UserName
Examples The following example retrieves and displays the name of the user
currently logged into Microsoft Dynamics GP.
Private Sub UserName_Click()

Dim UserName As String

'Retrieve and display the user name

UserName = UserInfoObj.UserName
MsgBox UserName
End Sub

APPENDIX
Appendix
This manual has the following appendix:
Appendix A, VBA Errors, explains how to handle specfic types of

errors in your Microsoft Dynamics GP VBA projects.
Appendix A: VBA Errors
The information presented here explains the runtime errors that you can
encounter using VBA with Microsoft Dynamics GP. It is divided into the
following sections:
Handling VBA errors

VBA error reference
Handling VBA errors

The following section, VBA errors display a VBA dialog with an error number and message text.
VBA error reference, VBA halts the execution of VBA code at the point the error occurred. You
explains the errors can handle Microsoft Dynamics GP VBA errors in the same manner as other
specific to Microsoft errors that appear in VBA, using VBAs On Error statement to respond to
Dynamics GP VBA and the error condition. The On Error statement has three clauses that allow
their corresponding you to handle errors:
error numbers.
Statement Description
On Error Go To line Enables an error-handling routine that starts at line. The
specified line must be in the same procedure as the On
Error statement.
On Error Resume Next Passes control to the statement that immediately follows
the statement that generated the error.
On Error Go To 0 Disables any enabled error handler in the current
procedure.
Refer to the VBA online In the following example, the Resume Next clause of the On Error
help for a comprehen- statement allows the procedure to skip the statement that generates an
sive explanation of the error. In this case, setting the Shipping Method field will generate an error
On Error statement (VBA error 1007) since NEW isnt an existing shipping method. However,
and other error han- the procedure continues to run, and the final statement sets the Trade
dling techniques. Discount field:

'Bypass any line that encounters an error
On Error Resume Next
'Set a window field that generates an error
'Set a window field that doesn't generate an error
TradeDiscount = "10.00"
End Sub

A P P E N D I X A V B A E R R O R S
VBA error reference

The following table provides a short description of the errors specific to
VBA for Microsoft Dynamics GP. Detailed explanations of the errors follow.
Error code Message text

1001 Unexpected error.
1002 Object not available.
1003 Unsafe operation. This operation could compromise the integrity
of the application.
1004 This property is Read Only.
1005 Unsafe operation. This operation can only be performed in the
BeforeGotFocus or AfterGotFocus events of the target field. The
operation could compromise the integrity of the application.
1006 Unsafe operation. This operation cannot be performed in the
target fields AfterUserChanged, BeforeLostFocus or
AfterLostFocus events. This operation could compromise the
integrity of the application.
1007 Unsafe operation. An attempt was made to set a value that
violates the applications business logic. This operation could
compromise the integrity of the application.
1008 Unsafe operation. An attempt was made to set a value into an
application field that is disabled. This operation could
80040208 This operation cannot be performed while the window is firing
events.
To access online help for these VBA errors, press the Help button in the error dialog
when the error occurs.
A PP E N D I X A V B A E R R O R S
Error 1001 Unexpected error.

Situation:
This error occurs in the following instances:
You set the caption for a field that didnt previously have a caption.
OLE automation failed within Microsoft Dynamics GP. Microsoft

Dynamics GP uses OLE automation to communicate with VBA.
Solution:
If youre using the Caption property to set a fields caption, be sure the
field has an existing caption.
If youre performing other tasks and receive this error, Microsoft Dynamics
GP may be running out of memory. Shut down applications that arent
necessary, then restart the accounting system. If the error persists, contact
Technical Support.
Error 1002 Object not available.

Situation:
Youve referenced a window field object, but the window containing the
field currently isnt open.
Solution:
To reference a window field in VBA code, the window must be open (its
IsLoaded property is True). The window does not need to be visible to
reference the window field.
When you reference a window field from outside the current window, its
good practice to check the window objects IsLoaded property to ascertain
whether the window containing the field is open. The following procedure
checks if the window is open using the IsLoaded property. If it is, the
procedure sets value of a window field:
Private Sub
If CustomerMaintenance.IsLoaded Then
'Reference a window field
CustomerMaintenance.ShippingMethod = "UPS BLUE"
End If
End Sub

Error 1003 Unsafe operation. This operation could compromise the integrity of
the application.
Situation:
You attempted to enable a field disabled by the accounting system, unlock a
field locked by the accounting system, make visible a field made invisible
by the accounting system, or make unrequired a field marked as required
by the accounting system. To preserve data integrity, Microsoft Dynamics
GP application code overrides any attempt you make through VBA to
change properties for disabled, locked, hidden or required fields.
Solution:
If Microsoft Dynamics GP application code disables, locks, hides or requires
a field, it may impact how your VBA code works with the field.
The following table explains some general guidelines for these properties:
Property Description
Enabled If the accounting system disables a field (its Enabled property is
False), you cannot enable it or set its value using VBA.
Locked If the accounting system locks a field, you cannot unlock it (set its
Locked property to False) or set its value using VBA.
Visible If the accounting system hides a field, you cannot make the field
visible (set its Visible property to True) or set its value using VBA.
Required If the accounting system requires a field, you cannot make the field
unrequired (set its Required property to False).
Error 1004 This property is Read Only.

Situation:
You attempted to set the value of a read-only property.
Solution:
You cannot set the value of a read-only property.
The following table shows the read only properties in VBA:
Object/Collection Property Description

Window IsLoaded Specifies whether the window is open.
Required Specifies whether the user entered data in all
fields whose Required property is True.
Field Parent Returns the window or report object that
contains the specified field.
Object Returns a field object without the standard
properties and methods extended to it by
Visual Basic.
DUOSObject ID Returns an object ID for a data object.
DUOSObjects Item Returns a data object from a collection of
data objects.
DUOSProperties Item Returns a property object from a collection
of properties.
Error 1005 Unsafe operation. This operation can only be performed in the
BeforeGotFocus or AfterGotFocus events of the target field. The operation could
Situation:
You attempted to set the value of a composite field using the ValueSeg
method from an event other than the composite fields BeforeGotFocus or
AfterGotFocus events.
Solution:
When setting a composite field using the ValueSeg property, set the
composite from only the BeforeGotFocus or AfterGotFocus events for the
field. When a composite gains focus, Microsoft Dynamics GP application
code validates the value of the composite, segment by segment. Since the
accounting system can perform this validation only after segments values
have been set, you must set segment values using the ValueSeg property in
events that precede the validation (the BeforeGotFocus and AfterGotFocus
events).

Error 1006 Unsafe operation. This operation cannot be performed in the target
fields AfterUserChanged, BeforeLostFocus or AfterLostFocus events. This
operation could compromise the integrity of the application.
Situation:
You attempted to set a fields value using the fields AfterUserChanged,
BeforeUserChanged or AfterLostFocus events. These events follow the
Microsoft Dynamics GP user changed event. Microsoft Dynamics GP uses
the user changed event to verify the value in a field; setting the value of the
field after the Microsoft Dynamics GP user changed event does not allow
the accounting system to verify the field.
Solution:
Set the fields value using the BeforeGotFocus, AfterGotFocus or
BeforeUserChanged events. These events precede the Microsoft Dynamics
GP user changed event, and allow the accounting system to verify the
contents of the field.
Error 1007 Unsafe operation. An attempt was made to set a value that violates
the applications business logic. This operation could compromise the integrity of
the application.
Situation:
You attempted to set a fields value from outside the field (before the field
gains focus), such as by using the windows BeforeOpen or AfterOpen
event, or another fields BeforeUserChanged or AfterUserChanged event.
When you set the value of a field before the field gains focus, VBA
automatically runs the Microsoft Dynamics GP user changed event for the
field youre setting. This is necessary so any accounting system application
code associated with these events can verify the fields value. Although
Microsoft Dynamics GP doesnt perform this verification for all fields, they
will perform verification for fields that affect business logic (such as an
invoice discount percent, or a tax amount) or for add-on-the-fly fields. If the
accounting system determines that the fields value is invalid, it will first
display its error dialog, followed by the VBA error dialog.
Solution:
There are three ways to avoid this type of error:
Whenever possible, set a fields value from inside the field, after it
has gained focus, using the fields AfterGotFocus or BeforeGotFocus
field events. If your event procedure sets an invalid value, the account-
ing system will still display a dialog, but VBA wont generate the error:

End Sub
If you set the value from outside the field, before the field has gained
focus, use the Focus method with the setvalue parameter in your event
procedure. The Focus method moves the focus to the field, then sets it
to the value of the setvalue parameter:

'Move the focus to the field, then set the value
ShippingMethod.Focus("NEW")
End Sub
Only set fields from outside the field if you know the accounting sys-
tem isnt performing field verification. Microsoft Dynamics GP per-
forms verification for fields that affect business logic (such as an invoice
discount percent, or a tax amount) or for add-on-the-fly fields. You can
set the value of add-on-the-fly fields only if the add-on-the-fly value
already exists as a record (such as an existing shipping method).

Error 1008 Unsafe Operation. An attempt was made to set a value into an
application field that is disabled. This operation could compromise the integrity of
the application.
Situation:
You attempted to set the value of a field that was locked or disabled by the
accounting system.
Solution:
If Microsoft Dynamics GP application code disables or locks a field (the
fields Enabled property is False, or its Locked property is True), you
cannot set its value. The accounting system disables fields when they dont
apply in a given situation, and locks fields to preserve the integrity of
accounting data (such as document totals). However, you can set the value
of fields youve disabled or locked through VBA.
Error 80040208 This operation cannot be performed while the window is firing
events.
Situation:
You attempted to use the PullFocus method with a window while VBA
window events or window field events are occuring.
Solution:
The PullFocus method forces a window to lose the focus and should only
be used in windows where no pending VBA window events or field events
are occuring. VBA events rely on the focus being present to run properly.
Glossary Check box field
A field that to allows a user to mark or
Editable grid
A scrolling window that allows the user
unmark a selection. In VBA, the value 1 to edit items in the window.
Additional headers and footers indicates a marked item; a 0 indicates an
Report bands that are printed when a unmarked item. Event
specified field changes. An action for a given object where
Combo box field associated application code (an event
Adds-allowed grid A list field that allows a user to enter a procedure) runs.
A grid that allows the user to enter and text value or choose that value from a list.
save new information using the grid. In VBA, a string value specifies an item in Event procedure
a combo box. VBA code that executes when a given
Ask dialog event occurs.
A modal dialog box that contains one or Composite field
more buttons, allowing the user to make A field made up of multiple segments. Field
a selection, and displays message text. Microsoft Dynamics GP account numbers A field contains a single piece of
are composite fields. information. A field can be displayed in a
Band window or on a report. The type of
A section of a report, such as the body, Concatenate information displayed depends on the
report header, report footer or a page To connect two or more strings to form a fields type.
header. single string.
Focus
Band events Control field The indicator that shows the object being
A VBA event that occurs just before a A unique field in a window thats used to controlled in the current window.
report band prints. control access to a record. In Microsoft
Dynamics GP, control fields are unique Form
Browse-only grid values, such as document numbers or In applications like Microsoft Dynamics
A grid that allows the user to browse customer IDs. GP, a group of windows that function
through items in the window, but not together for a common purpose.
make any changes. Currency field
A field that allows the user to enter a Format
Button drop list field currency amount. The extra characters, spacing and
A button field that drops to allow a attributes that can be applied to a field
user to select one item from a list of Disabled field when data is entered or displayed.
values. VBA uses a numeric value to A field that is unavailable to or cannot be
identify the selected item in the list. chosen by a user. A disabled button or Forms dictionary
field appears dimmed. The dictionary that stores user-modified
Calculated field resources for Microsoft Dynamics GP.
A report field containing an expression Drop-down list field This dictionary is created when the
that combines fields in a reports table, A field that drops to allow users to Modifier is accessed for the first time.
report fields, constants, functions and select one item from a list. VBA uses a
operators. You can set or return the value numeric value to identify the selected Getstring dialog
of user-defined calculated fields. You can item in the list. A modal dialog that contains a data entry
only return the value of Microsoft field and OK and Cancel buttons.
Dynamics GP calculated fields. DUOS
An acronym for Dynamic User Object Grid
Caption Store. The DUOS lets you use VBA to A window used to display information
A field caption is a text label that shows create, store and retrieve user-definable from a table (also known as a scrolling
the user the information thats displayed data objects. window). Grids allow the user to scroll
or that can be entered in the through records in the table. There are
corresponding window field. A window Editable field three types of grids: browse-only,
caption is the title of the window. A field whose contents can be changed editable and adds-allowed.
by the user.

GLOS SA RY
Grid event Modifier Project file

A VBA event that occurs when a grid A tool that allows the user to change the A file containing VBA code, user forms
fills, or a grids line changes, gains focus user interface of Microsoft Dynamics GP and objects. The project is named based
or loses focus. windows. A forms dictionary stores these on the dictionary. For instance, the project
modifications. for Microsoft Dynamics GP is named
Group box DYNAMICS.VBA. For third-party
A box drawn around a group of check Multi-select list box field applications integrating with the
boxes or other fields to visually group the A field from which the user can select one accounting system, this file is name.VBA,
items. or more items. VBA uses a 32-bit numeric where name is the name of the integrating
value to identify the selected item in the applications dictionary.
Integer field list.
A field that allows the user to enter a Prompt
number between -32,768 and 32,767. Object model See Caption.
The relationship objects have to each
Keyable length other within a given application. Property
The number of characters that can be A characteristic of an object in VBA that
typed in a field. Package files you can retrieve or set. Properties include
Special text files that are used to deliver the title of a window, or the value of a
Layout window customizations made with the Modifier, field.
A window in the Modifier and Report VBA, and the Report Writer.
Writer that allows users to design the Push button field
layout of a window, grid (scrolling Page footer A field the user can click to perform an
window) or report. A report band placed at the bottom of action.
every report page. The page footer often
List box field includes administrative information, Radio button field
A field that allow users to select one static such as the name of the person running A field that allows a single selection to be
text value from a list. VBA uses a numeric the report. made from a group of two or more
value to identify the selected item in the options. Radio buttons must be part of a
list. Page header radio group. VBA uses a numeric value
A report band placed at the top of every to identify the selected item in the radio
List field report page. The page header typically
Any list box, drop-down list, multi-select group.
includes fields for the page number, date
list, button drop list, combo box or visual and time. Read only
switch field. A property access mode that indicates the
Palette propertys value can only be returned.
Method A type of window used for navigation.
An action in VBA that you can perform Read/write
for a given object. Methods include Parameter A property access mode that indicates the
opening and closing a window or A value passed to or returned from a propertys value can be returned or set.
moving a field in a window. VBA statement, function or procedure.
Report event
Modal dialog Pixel A VBA event that occurs when you print
A window that contains no operating The smallest graphical element displayed a report. Report events occur when the
system controls and cant be resized. on a monitor. The pixel is the smallest report starts, just before a given band
Modal windows are used when you unit of measurement in windows. within the report prints, and when the
require the user to perform an action report ends.
before continuing. Procedure
A named sequence of statements
Modal dialog event executed as a single unit. An event
A VBA event that occurs when a modal procedure is the most common type of
dialog appears. procedure used in a VBA project.
G L O S S A R Y
Report field Segment

Any field that appears on a report. You One portion of a composite field.
can use VBA to return the value of report Microsoft Dynamics GP uses composite
fields if theyre table fields, accounting fields for account numbers.
system calculated fields, or legends. You
can set the value of report fields only if String field
theyre user-defined calculated fields or A field that allows the user to enter up to
legend fields. 255 ASCII characters. VBA include any
formatting when setting or returning the
Report footer value of a string field.
A report band that prints at the bottom of
the last report page. Reports can include Tab sequence
report footers, page footers and The order in which the focus moves from
additional footers. one field to the next in a window when a
user presses the TAB key.
Report legend
A report field that contains data passed Text field
to the report at runtime, before it prints. A field that allows the user to enter up to
Legend fields typically include 32,000 ASCII characters. VBA references
information about the report, such as the the string value of a text field.
range of records the user chose for the VBA
report.
Visual Basic for Applications. A
Report Writer development environment used to
A tool that allows you to modify reports, interact with and control objects within
or design new reports. A reports host applications.
dictionary stores these changes or Visual switch field
additions. A field that displays a series of text or
Required field picture items. Clicking the field displays
A field in which a value must be entered the next item in the series. VBA uses a
to process information, such as an ID or numeric value to identify the item
customer name. You can use VBA to selected in a visual switch.
mark fields as required. Window
Required fields are displayed in a The work area used to enter and display
different color or type style when a user information in an application.
chooses the Show Required Fields menu
Window event
item.
A VBA event that occurs when a window
Resource Descriptions tool opens, activates, closes or when a modal
A tool that displays information about dialog appears.
the accounting systems fields, windows
Window field
and tables. To access this tool from within
A field within a Microsoft Dynamics GP
the accounting system, point to Resource
window.
Descriptions in the Tools menu, then
choose Tables, Fields or Windows. Window field event
A VBA event that occurs when a field
Scrolling window
gains focus, loses focus, or when its value
See Grid.
changes.

Index AfterLostFocus event (continued)
using 42
BeforeClose event
described 130
AfterModalDialog event using 20
A described 125 BeforeGotFocus event
account numbers using 23 avoiding errors 53
setting account segments 171 AfterOpen event button drop list fields 55
using 58 described 128 described 161
accumulator fields, in VBA 93 using 20 using 37
Activate method AfterUserChanged event BeforeLineChange event
described 122 button drop list fields 55 described 195
using 27 combo box fields 57 using 80
activating windows 27 composite fields 58 BeforeLineGotFocus event
additional footer described 160 described 196
defined 271 drop-down list fields 62 using 79
using the BeforeAF event 90 list box fields 64 BeforeLineLostFocus event
additional header multi-select list box fields 65 described 197
defined 271 push button fields 67 using 81
using the BeforeAH event 89 radio button fields 68 BeforeLinePopulate event
adds-allowed grids related errors 268 described 198
defined 271 using 40 using 81
described 78 visual switch fields 71 BeforeLostFocus event
ADO connection, creating for database alert messages, see modal dialogs button drop list fields 55
255 ask dialogs described 162
AfterActivate event defined 271 using 41
described 123 described 22, 126 BeforeModalDialog event
using 21 responding to 22 described 131
AfterClose event using 22
described 124 B BeforeOpen event
using 21 band, defined 271 described 134
AfterGotFocus event band events using 19
avoiding errors 53 defined 271 BeforePF event
button drop list fields 55 returning data from multiple described 213
described 158 bands 94 using 90
using 37 suppressing report data 89 BeforePH event
AfterLineChange event using 87 described 214
described 192 BeforeActivate event using 89
using 80 described 129 BeforeRF event
AfterLineGotFocus event using 21 described 215
described 193 BeforeAF event using 90
using 79 described 210 BeforeRH event
AfterLineLostFocus event using 90 described 216
described 194 BeforeAH event using 89
using 81 described 211 BeforeUserChanged event
AfterLostFocus event using 89 button drop list fields 55
button drop list fields 55 BeforeBody event combo box fields 57
described 159 described 212 composite fields 58
related errors 268 using 90 described 163

I N D E X
BeforeUserChanged event (continued) Changed event constants (continued)

drop-down list fields 62 button drop list fields 55 emNever, described 138
list box fields 64 described for fields 166 emOriginalOnly, described 138
multi-select list box fields 65 push button fields 67 control field
push button fields 67 using 40 defined 271
radio button fields 68 Changed property using to retrieve a DUOS data
related errors 268 described for grids 199 object 106
using 39 described for windows 136 conventions in documentation 3
visual switch fields 71 check box field converting fields
body, using the BeforeBody event 90 defined 271 for numeric calculations 49
browse-only grids programming 56 guidelines for field values 50
defined 271 circular references, avoiding 14 using VBAs conversion functions
described 77 Clear button, pushing from VBA 67 50
button drop list field Close method Count property, described 244
defined 271 described 137 CreateADOConnection method,
programming 55 using with windows 25 described for UserInfo object 255
button fields, see push button field collections currency field
creating a DUOS collection 100 defined 271
C DUOS object collection 12 programming 60
calculated fields DUOS property collection 12 Customization Maintenance window
defined 271 combo box field 115
referencing in reports 93 defined 271 Customization Site Enabler, described
Cancel button, pushing from VBA 67 programming 57 113
Cancel method company ID, retrieving 256
described 217 company name, retrieving 254 D
using with reports 91 CompanyName property, described for data objects
canceling UserInfo object 254 creating 100
field processing composite field deleting 101, 107
got focus events 37 controlling the focus 44 described 97
lost focus events 41 defined 271 printing 110
user changed events 39 guidelines for setting 171 retrieving 101, 106
grid processing 80 programming 58 saving 104
report processing 91 related errors 267 storage with Microsoft Dynamics
window processing 20 concatenating, defined 271 GP 99
caption connections, ADO connections to updating 101
applied to Microsoft Dynamics GP database 255 database
fields 165 constants creating ADO connection to 255
defined 271 dcButton1, described 125, 131 names of in Microsoft Dynamics
Caption property dcButton2, described 125, 131 GP 256
check box fields 56 dcButton3, described 125, 131 date, retrieving user date 257
described for fields 165 dcCancel, described 125, 131 date field, programming 61
described for windows 135 dcOK, described 125, 131 Delete button, pushing from VBA 67
push button fields 67 dtModalAskDialog, described 125, deleting
radio button fields 68 131 DUOS data objects 107
related errors 265 dtModalGetStringDialog, modified forms, impact on VBA 19
windows 28 described 125, 131 disabled fields
emModifiedOnly, described 138 defined 271
I N D E X
disabled fields (continued) DUOSProperties collection library events (continued)

disabling window fields 43 243-248 for grids 78
distributing a VBA project 113 DUOSProperty object library 249-252 for reports 85
documentation Dynamic User Object Store, see DUOS for window fields 35
other VBA resources 2 for windows 18
symbols and conventions 3 E Exists property, described 232, 245
drop-down list field editable fields, defined 271 expand button, pushing from VBA 67,
defined 271 editable grids 71
programming 62 defined 271 exporting data to other applications 95
DUOS described 78 exporting package files 115
chapter 97-111 Empty property extender properties, described 178
creating a collection 100 described 168 external components, referencing 113
creating data objects 100 using 48
data objects Enabled property F
creating 100 described 169 field object library 157-189
deleting 101, 107 related errors 266, 270 fields
described 97 using 43 see also window fields
printing 110 End event defined 271
retrieving 101, 106 described 218 grid fields 75
saving 104 using 87 report fields 92
tables for storing 99 errors window fields 47
updating 101 appendix 263-270 working with report fields 88
defined 271 error 1001 265 working with report legends 86
deleting a data object 101, 107 error 1002 265 focus, defined 271
described 97 error 1003 266 Focus method
in the object model 10, 12 error 1004 267 avoiding errors 53
overview of the object model 97 error 1005 267 described 170
printing a data object 110 error 1006 268 using 44
programming 97 error 1007 268 FocusSeg method
property and method list 102 error 1008 270 composite fields 58
retrieving data objects 101 error 80040208 270 described 171
saving a data object 104 handling VBA errors 263 using 44
structure 98 VBA error list 264 Format function, use with report fields
updating a data objects 101 when setting fields 52 93
using 103 event procedures formats
using modal dialogs to see also events composite format 58
synchronize 23 defined 271 currency format 60
DUOSObject object library 239-241 EventMode property date format 61
DUOSObjectCombineID method, described for grids 200 defined 271
described 224 described for reports 219 integer format 63
DUOSObjectExtractID method, described for windows 138 report field format 93
described 226 using with grids 82 string format 69
DUOSObjects collection library 231-237 using with reports 85 forms
DUOSObjectsGet method using with windows 29 defined 271
described 228 events using with VBA 26
using 100 defined 271 forms dictionary, defined 271
described 13

I N D E X
G Import Package File window 117 M

getstring dialogs importing package files 116 margin notes 3
defined 271 integer field messages, see modal dialogs
responding to 127 defined 272 method list
got focus events, using 36 programming 63 DUOS 102
grid events IntercompanyID property, described grids 82
defined 272 for UserInfo object 256 reports 91
line change events 79 IsLoaded property, described 142 window fields 43
line got focus events 79 Item property windows 24
line lost focus events 81 described for a DUOSObjects methods
line populate events 81 collection 233 defined 272
grid object library 191-208 described for a DUOSProperties described 12
grids collection 246 Microsoft Office, exporting data to
see also grid events Office applications 95
adding to a project 75
K Missing File dialog 113
keyable length, defined 272
adding window fields from 75 modal dialog events
canceling processing 80 L defined 272
changing a grids name 82 layout windows, defined 272 using 22
chapter 73-82 Left property modal dialogs
defined 271 described for fields 174 changing the contents of 23
filtering grid content 81 described for grids 202 defined 272
in the object model 10, 11 described for windows 143 delete dialog and the DUOS 107
programming 73, 76 using 28 programmatically answering 22
property and method list 82 Legend property responding to 22
removing from a project 75 described 220 save dialog and the DUOS 105
types of 77 using with reports 92 types 126
using grid events 78 light bulb symbol 3 using with the DUOS 23
using VBA with modified grids 79 line change events, using 79 Modifier
group box, defined 272 line got focus events, using 79 defined 272
line lost focus events, using 81 using VBA with grids 79
H line populate events, using 81 using VBA with modified
Height property windows 19
list box field
described for fields 173 using with VBA 13
defined 272
described for windows 140 Move method
programming 64
using 28 described for fields 176
list fields
Hide method described for grids 203
button drop list 55
described for grids 201 described for windows 144
defined 272
described for windows 141 moving windows 28
drop-down list 62
using 27 multi-select list box field
list box 64
hiding defined 272
multi-select list box 65
report fields 93 programming 65
Locked property
window fields 45
described 175
windows 27
related errors 266, 270
N
Name property
I using 43
described for a DUOSObjects
ID property, described 240 locking window fields 43
collection 234
IDs, retrieving user ID 258 lookup button, pushing from VBA 67
lost focus events, using 41
I N D E X
Name property (continued) package files (continued) project (continued)

described for a DUOSProperty described 115 renaming grids 82
object 250 exporting 115 renaming window fields 46
described for fields 177 import/export issues 118 renaming windows 29
described for grids 205 importing 116 Project Explorer
described for reports 221 overwriting customizations 118 described 8
described for windows 145 page footer viewing grids 75
using with fields 46 defined 272 viewing reports 83
using with grids 82 using the BeforePF event 90 viewing window fields 32
using with reports 91 page header viewing windows 16
using with windows 29 defined 272 project file
names using the BeforePH event 89 defined 272
retrieving company name 254 palettes described 8
retrieving user name 259 defined 272 for third-party applications 8
note button, pushing from VBA 67 pushing a stick pin from VBA 71 prompt, see caption
numeric fields, converting for numeric parameters, defined 272 properties
calculations 49 Parent property, described 180 custom, described 178
password protecting a project 114 defined 272
O pixel, defined 272 described 12
object model prerequisites for VBA 2 related errors 267
defined 272 printing standard, described 178
using the object model 10 DUOS data objects 110 Properties property, described 241
Object property, described 178 reports, and VBA events that occur property list
objects 85 DUOS 102
DUOS data object 12 privileges, required to create or edit grids 82
DUOS property object 12 VBA code 7 reports 91
field object, described 11 procedure, defined 272 window fields 43
grid object, described 11 product support for VBA 3 windows 24
in the object model 10 programming PullFocus method
report object, described 11 grids 76 described 148
user information object, described reports 85 related errors 270
11 the Dynamic User Object Store push button field
using with events 13 (DUOS) 100 defined 272
using with methods 12 window fields 34 programming 67
using with properties 12 windows 17
window field object, described 32 project R
window object, described 11, 16 see also project file radio button field
Open method adding grids 75 defined 272
described 146 adding report fields 84 programming 68
using with windows 25 adding reports 83 radio button group 68
opening windows, guidelines 146 adding window fields 32 read only, defined 272
overwriting customizations with adding windows 16 read/write, defined 272
package files 118 locking 114 references
removing grids 75 to external components 113
P removing reports 84 to third-party dictionaries 14
package files removing window fields 33 registration keys, for VBA 113
contents 115 removing windows 17
defined 272

I N D E X
Remove method reports (continued) segments (continued)

described for a DUOSObject programming 83 guidelines for setting 171
collection 235 property and method list 91 using with a composite 58
described for DUOSProperties removing a report 84 setting report fields
collection 248 returning data from an entire using a Start event 86
report body, using the BeforeBody report 94 using band events 88
event 90 returning report fields 88 setting window fields
report events setting report fields 88 guidelines 50
band events 87 using legend fields 86 related errors 268
defined 272 using report events 85 using a BeforeGotFocus event 37
Start/End events 86 using VBA with modified reports using a BeforeUserChanged event
report fields 85 39
accumulator fields 93 required fields using an AfterGotFocus event 37
adding to a project 84 defined 273 Show method
calculated fields 93 using the Required property 46 described for grids 206
defined 273 Required property described for windows 151
format of returned values 93 described for fields 181 showing
guidelines for use 92 described for windows 150 report fields 93
hiding and showing 93 related errors 266 window fields 45
in the object model 10 using with the DUOS 104 windows 27
legend fields 86 using with window fields 46 shrink button, pushing from VBA 71
returning 88 resizing windows 28 SortByExisting property, described 236
setting 88 Resource Descriptions tool Start event
suppressing 89 defined 273 described 222
table fields 92 described 54 using 86
report footer retrieving DUOS data objects 106 stick pin button, pushing from VBA 71
defined 273 returning report fields storing additional data, chapter 97-111
using the BeforeRF event 90 from a Start event 86 string field
report header, using the BeforeRH from band events 88 defined 273
event 89 returning window fields, guidelines 48 programming 69
report legends runtime errors, see errors support available for VBA 3
defined 273 SY_User_Object_Store table, described
setting from a Start event 86 S 99
report object library 209-222 Save button symbols in documentation 3
report sections, see band events pushing from VBA 67
Report Writer using with the DUOS 104 T
defined 273 saving DUOS data objects 104 tab sequence, defined 273
using VBA with modified reports scrolling windows table fields, for reports, using with
85 see also grids VBA 92
reports pushing expand and shrink TabStop property, described 182
see also report events buttons 71 technical support for VBA 3
adding to a project 83 security, setting access to customized text field
canceling 91 resources 117 defined 273
chapter 83-96 segments programming 70
exporting data to other controlling the focus within a third-party dictionaries
applications 95 composite 44 project file 8
in the object model 10, 11 defined 273 using VBA with 14
I N D E X
title, see caption ValueSeg property Width property (continued)

Top property composite fields 58 using 28
described for fields 183 described 187 window activate events, using 21
described for grids 207 related errors 267 window close events, using 20
described for windows 152 using 47 window events
using 28 using with the FocusSeg method activate events 21
171 close events 20
U VBA defined 273
user changed events, using 38 creating the project file 8 modal dialog events 22
user information, in the object model defined 273 open events 19
11 described 2 window field events
UserDate property, described for documentation 2 Changed event 40
UserInfo object 257 enabling 113 defined 273
UserID property, described for packaging a project 114, 115 got focus events 36
UserInfo object 258 prerequisites 2 lost focus events 41
UserInfo object library 253-259 registration keys 4, 113 user changed events 38
UserInfoGet method, described 230 using with fields 34 window fields
UserName property, described for using with grids 76 see also window field events
UserInfo object 259 using with reports 83 accessing fields in child windows
Using VBA, part 6-118 using with the Dynamic User 26
Object Store (DUOS) 97 adding to a project 32
V using with the Modifier 13 button drop list 55
Value property using with windows 17 canceling field processing
button drop list fields 55 Visual Basic Editor 7 using got focus events 37
check box fields 56 VBA Object Library, part 120-259 using lost focus events 41
combo box fields 57 VBA Overview, chapter 7-14 using user changed events 39
composite fields 58 VBAGlobal object library 223-230 chapter 31-71
currency fields 60 Visible property check box 56
date fields 61 described for fields 188 combo box 57
described for a DUOSProperty described for grids 208 composite field 58
object 251 described for windows 153 controlling the focus 44
described for fields 184 related errors 266 currency field 60
drop-down list fields 62 using with report fields 93 date field 61
guidelines for returning window using with window fields 45 defined 273
fields 48 using with windows 27 disabling 43
guidelines for setting fields 50 Visual Basic Editor, described 7 drop-down list field 62
integer fields 63 Visual Basic for Applications, see VBA Empty property 48
list box fields 64 visual switch field errors related to referencing 265
multi-select list box fields 65 defined 273 errors related to setting 268
push button fields 67 programming 71 field type reference 54-71
radio button fields 68 guidelines for moving 174
related errors 268 W guidelines for returning values 48
string fields 69 warning messages, see modal dialogs guidelines for setting values 50
text fields 70 warning symbol 3 in the object model 10
using with report fields 88 Width property integer field 63
using with window fields 47 described for fields 189 list box field 64
visual switch fields 71 described for windows 155 locking 43

I N D E X
window fields (continued) windows (continued)

making fields required 46 in the object model 10, 11
multi-select list box field 65 moving and resizing 28
passing as arguments 180 opening and closing 25
performing numeric calculations opening invisibly 19
49 programming 15, 17
programming 31, 34 property and method list 24
progression of events 51 removing window objects 17
property and method list 43 renaming windows 29
push button field 67 setting the event mode 29, 82
radio button field 68 using VBA with modified
removing from a project 33 windows 19
renaming window fields 46 using window events 18
setting
dealing with VBA errors 52
during window open event 19
using a BeforeGotFocus event
37
using a BeforeUserChanged
event 39
using an AfterGotFocus event
37
showing and hiding 45
string field 69
text field 70
using VBA with new fields 13
using window field events 35
using with grids 75
Value property 47
ValueSeg property 47
verifying field data 51
visual switch field 71
window object library 121-155
window open events, using 19
windows
see also window events
activating 27
adding to a project 16
as part of a form 26
canceling a window close 20
changing a windows caption 28
chapter 15-29
closing other windows 21
defined 273
determining which invoke VBA
events 135
hiding 27

VBA Developer's Guide: Microsoft Dynamics GP 2010

Uploaded by

Copyright:

Available Formats

VBA Developer's Guide: Microsoft Dynamics GP 2010

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VBA Developer's Guide: Microsoft Dynamics GP 2010

Uploaded by

Copyright:

Available Formats

Microsoft Dynamics GP 2010

VBA Developers Guide

All other trademarks are property of their respective owners.

Publication date March 2010

Part 1: Using VBA ................................................................................................................ 6

Chapter 2: Programming Windows ................................................................... 15

Chapter 3: Programming Window Fields ..................................................... 31

VBA DEVELOPERS GUIDE i

Chapter 4: Programming Grids ............................................................................. 73

Chapter 5: Programming Reports ....................................................................... 83

Chapter 6: Storing Additional Data .................................................................. 97

Chapter 7: Distributing a Project ..................................................................... 113

Package files .............................................................................................................................. 115

Part 2: VBA Object Library .............................................................................. 120

Chapter 9: Field Object ............................................................................................. 157

VBA DEVELOPERS GUIDE iii

Height property ............................................................................................................... 173

Chapter 10: Grid Object ............................................................................................ 191

Chapter 11: Report Object ...................................................................................... 209

Chapter 12: VBAGlobal Object........................................................................... 223

Chapter 13: DUOSObjects Collection ......................................................... 231

Chapter 14: DUOSObject Object ...................................................................... 239

Chapter 15: DUOSProperties Collection................................................... 243

Chapter 16: DUOSProperty Object ................................................................ 249

Chapter 17: UserInfo Object ................................................................................ 253

Appendix .................................................................................................................................. 262

Glossary ..................................................................................................................................... 271

VBA DEVELOPERS GUIDE v

Whats in this manual

Part 1, Using VBA, provides information on how you can program

Part 2, VBA Object Library, provides reference information about

Telephone support Technical Support at (888) 477-7877 between 8:00

Internet VBA Technical Support is also available online through

Symbols and conventions

Warnings indicate situations you should be

Margin notes summarize Margin notes call attention to critical

VBA DEVELOPERS GUIDE 3

1. Install Microsoft Dynamics GP.

2. Register the Modifier.

3. Review Chapter 1, VBA Overview.

Chapter 1, VBA Overview, explains the basics of the VBA environ-

Chapter 2, Programming Windows, explains how to use VBA with

Chapter 3, Programming Window Fields, explains how to use VBA

Chapter 4, Programming Grids, explains how to use VBA with the

Chapter 5, Programming Reports, explains how to use VBA with the

Chapter 6, Storing Additional Data, explains how to store user-

Chapter 7, Distributing a Project, explains how to package and

The Visual Basic Editor

The Visual Basic Editor

Modifier and VBA menu

VBA DEVELOPERS GUIDE 7

The following illustration shows how an existing project looks when

The Visual Basic Editor is

The VBA project

If youre working with a third-party application, VBA creates a separate project to

Objects defined for your

VBA DEVELOPERS GUIDE 9

The organization of the model is important, since you must navigate

'Set a field on a window