microsoft dynamics gp 2013 modifier user’s...

Microsoft Dynamics® GP 2013

Modifier User’s Guide

Copyright Copyright © 2012 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, Dexterity, Microsoft Dynamics, Visual Basic, Visual Studio, 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 Dynamics GP Customer Assistance Department at 800-456-0025 (in the U.S. or Canada) or +1-701-281-6500.

Publication date April 2012

U S E R ’ S G U I D E i

Contents

Introduction .................................................................................................................................................2What’s in this manual...................................................................................................................................2

Symbols and conventions ............................................................................................................................2

Product support ............................................................................................................................................3

Part 1: Basics .............................................................................................................................................6

Chapter 1: Getting Started with the Modifier ........................................................... 7Types of modifications .................................................................................................................................7

Terminology...................................................................................................................................................7

Storing modifications ...................................................................................................................................8

Starting the Modifier ....................................................................................................................................9

Chapter 2: The Modifier Interface ......................................................................................11The Modifier main window and toolbar................................................................................................. 11

Menus ........................................................................................................................................................... 11

Windows ......................................................................................................................................................13

Standard buttons.........................................................................................................................................14

Part 2: Modifying Forms ......................................................................................................... 16

Chapter 3: Selecting Forms to Modify ........................................................................... 17Finding a form name ..................................................................................................................................17

Creating a modified form ..........................................................................................................................18

Chapter 4: Modifying Windows ............................................................................................ 21Opening a window layout.........................................................................................................................21

The Toolbox..................................................................................................................................................22

The layout area ............................................................................................................................................24

The layout grid ............................................................................................................................................25

The Properties window..............................................................................................................................25

Window properties .....................................................................................................................................26

Field properties ...........................................................................................................................................27

Drawn object properties.............................................................................................................................30

Previewing a window ................................................................................................................................30

Setting the tab sequence.............................................................................................................................31

Positioning the window.............................................................................................................................32

Adding fields to the window ....................................................................................................................32

Adding pictures ..........................................................................................................................................33

Linking fields to prompts ..........................................................................................................................33

Resizing windows.......................................................................................................................................33

Auto-complete.............................................................................................................................................35

Linking fields to format fields...................................................................................................................36

ii U S E R ’ S G U I D E

C O N T E N T S

Chapter 5: Modifying Scrolling Windows ................................................................... 39Opening a scrolling window layout.........................................................................................................39

The layout area ............................................................................................................................................39

Scrolling window properties .....................................................................................................................41

Adding fields to a scrolling window .......................................................................................................42

Chapter 6: Modifying Menus................................................................................................... 43Opening a menu definition .......................................................................................................................43

Editing menu items.....................................................................................................................................44

Chapter 7: Adding New Fields ............................................................................................... 45Creating local fields ....................................................................................................................................45

Using the Toolbox .......................................................................................................................................47

Adding prompts..........................................................................................................................................47

Control types ...............................................................................................................................................48

Working with controls................................................................................................................................56

Part 3: Global Modifications.............................................................................................60

Chapter 8: Data Types ................................................................................................................... 61Opening a data type ...................................................................................................................................61

Keyable length.............................................................................................................................................61

Static values .................................................................................................................................................62

Format...........................................................................................................................................................63

Chapter 9: Formats........................................................................................................................... 65Opening a format ........................................................................................................................................65

Formatting options .....................................................................................................................................65

Format string ...............................................................................................................................................66

Chapter 10: Global Fields ........................................................................................................... 69Opening a global field................................................................................................................................69

Opening a field’s data type .......................................................................................................................69

Chapter 11: Pictures and Native Pictures ................................................................... 71Pictures .........................................................................................................................................................71

Adding a picture to the picture library....................................................................................................71

Using a picture from the picture library..................................................................................................72

Creating native pictures .............................................................................................................................72

Synchronizing native pictures...................................................................................................................73

Using native pictures..................................................................................................................................73

Chapter 12: Strings.......................................................................................................................... 75Using strings................................................................................................................................................75

Modifying a string ......................................................................................................................................75

Chapter 13: Messages ................................................................................................................... 77Finding messages........................................................................................................................................77

Replacement markers .................................................................................................................................77

Modifying messages...................................................................................................................................78

U S E R ’ S G U I D E iii

C O N T E N T S

Part 4: Storing and Accessing Modifications ...........................................80

Chapter 14: Storing Modifications.................................................................................... 81Forms dictionary .........................................................................................................................................81

Launch file....................................................................................................................................................81

Modifier configurations .............................................................................................................................82

Chapter 15: Accessing Modifications ............................................................................ 85Accessing the Modifier...............................................................................................................................85

Accessing modified forms .........................................................................................................................85

Accessing third-party modifications........................................................................................................87

Removing modified forms.........................................................................................................................88

Chapter 16: Packaging Modifications ............................................................................ 89Package files.................................................................................................................................................89

Package file import/export issues............................................................................................................91

Glossary .........................................................................................................................................................93

Index ...................................................................................................................................................................97

iv U S E R ’ S G U I D E

INT

RO

DU

CT

ION

2 U S E R ’ S G U I D E

IntroductionWelcome to the Modifier, the tool you can use to customize the appearance ofapplications like Microsoft Dynamics® GP. The Modifier offers a variety of featuresthat allow you to modify the look and feel of Microsoft Dynamics GP withoutaffecting the integrity of the accounting system.

With the Modifier, you can change the appearance of individual windows, makeglobal changes that affect the entire interface, and add new controls to windows.The ability to add new controls is most useful if you are also using Visual Basic® forApplications (VBA), Visual Studio® Tools for Microsoft Dynamics GP, or theContinuum API to extend the functionality of the accounting system.

What’s in this manual

This manual is designed to give you an in-depth understanding of how to use theModifier to customize the appearance of Microsoft Dynamics GP.

• Part 1, Basics, describes the Modifier interface and explains how to start theModifier.

• Part 2, Modifying Forms, provides detailed information about how to makemodifications to forms in Microsoft Dynamics GP.

• Part 3, Global Modifications, describes how to make modifications that willaffect the entire Microsoft Dynamics GP interface.

• Part 4, Storing and Accessing Modifications, describes the Forms dictionary. Italso explains how to control access to modifications you have made with theModifier. Packaging modifications is also described.

You can also refer to the Modifier online help for more information about using theModifier.

Symbols and conventions

To help you use this documentation more effectively, we’ve used the followingsymbols and conventions within the text to make specific types of informationstand out.

Symbol Description

The light bulb symbol indicates helpful tips, shortcuts and suggestions.

Warnings indicate situations you should be aware of when completing tasks with the Modifier.

Margin notes summarize important information.

Margin notes call attention to critical information, and direct you to other areas of the documentation where a topic is explained.

U S E R ’ S G U I D E 3

I N T R O D U C T I O N

Product support

Technical support for the Modifier can be accessed by the following methods:

• Telephone support – Technical Support at (888) 477-7877 between 8:00 a.m. and5:00 p.m. Central Time, Monday through Friday. International users can contactTechnical Support at (701) 281-0555.

• Internet – Modifier Technical Support is also available online throughCustomerSource or PartnerSource, and is accessible from www.microsoft.com/Dynamics/GP.

Convention Description

Part 2, Making Modifications

Bold type indicates a part name.

Chapter 1, “Basics” Quotation marks indicate a chapter name.

Applying formats Italicized type indicates a section name.

RUNTIME.EXE Words in uppercase indicate a file name.

Software Development Kit(SDK)

Acronyms are spelled out the first time they’re used.

TAB or ALT+M Small capital letters indicate a key or a key sequence.

PA

RT

1: B

AS

ICS


Part 1: BasicsThis portion of the documentation contains basic information you should knowbefore you begin using the Modifier. The following topics are discussed:

• Chapter 1, “Getting Started with the Modifier,” describes the types ofmodifications you can make with the Modifier, the terminology used in theproduct, and how modifications are stored. It describes how to start theModifier.

• Chapter 2, “The Modifier Interface,” describes the Modifier’s interface.


Chapter 1: Getting Started with the ModifierBefore you begin working with the Modifier, you should have a basicunderstanding of the types of modifications you can make, terminology used in theModifier, and how modifications are stored. Information is divided into thefollowing sections:

• Types of modifications• Terminology• Storing modifications• Starting the Modifier

Types of modifications

You can use the Modifier to make three basic types of modifications: modifying theappearance of windows, making global changes to the interface, and adding newcontrols.

Modifying windowsWith the Modifier, you can change the appearance of individual windows in theaccounting system. This allows you to customize your system to the way you work.For instance, a common window modification is hiding fields that you won’t beusing. Another common modification is changing the order in which the focusmoves from field to field to reflect the way you enter data into the system.

Making global interface changesThe Modifier also allows you to make changes that will be reflected throughout theentire interface. For example, most of the strings that are displayed in the interfacecan be modified. If you were to modify the string “ZIP Code” and change it to be“Postal Code”, the change would be seen in every place the string “ZIP Code” wasused.

Adding new fieldsYou can also use the Modifier to add new fields to windows in the accountingsystem. This capability is designed primarily for users who also use Visual Basic forApplications (VBA), Visual Studio Tools for Microsoft Dynamics GP, or theContinuum API to further customize Microsoft Dynamics GP.

Terminology

To get the most benefit from the Modifier, you need to understand the structure ofan application like Microsoft Dynamics GP that is written in Microsoft® Dexterity.The interface is composed of windows and forms.

WindowsA window is the work area used to enter and display information in an application.Windows in a Dexterity-based application are the actual windows you see whenyou run the application.

P A R T 1 B A S I C S


FormsA form is a collection of windows, menus and other resources that function togetherfor a common purpose. For example, four windows work together to handlecustomer information. These windows are:

• Customer Maintenance• Customer Maintenance Options• Customer Account Maintenance• Display Credit Limit Warning

Because they work together, these windows are grouped into a form namedRM_Customer_Maintenance.

Forms are typically named based on the type of action the user is performing. Everywindow in a Dexterity-based application is part of a form. When you use theModifier to work with window, you must first find and open the form that containsit.

Storing modifications

All changes and additions you make using the Modifier are stored in the formsdictionary for the application. By storing the new and modified resources in aseparate dictionary, the integrity of the system can be maintained. For example, thefollowing illustration shows the dictionary for Microsoft Dynamics GP and itsassociated forms dictionary.

You’ll learn more about the forms dictionary in Chapter 14, “StoringModifications.”

These windows are part of theRM_Customer_Maintenance

form.

Forms.dicDynamics.dic

New and modified resources are stored in the forms dictionary.


C H A P T E R 1 G E T T I N G S T A R T E D W I T H T H E M O D I F I E R

Starting the Modifier

To begin using the Modifier, log into the accounting system. If you’re usingMicrosoft Dynamics GP in a multiuser environment, verify that no other users arein the system before you use the Modifier. Then perform the following steps:

1. Start the Modifier.From the main Dynamics GP window:In the Microsoft Dynamics GP menu, choose Tools >> Customize >> Modifier.

From individual task windows:In the Tools menu, choose Customize >> Modifier.

If the Modifier item is dimmed, the Modifier hasn’t been registered or you have not beengranted access through system security. Refer to the installation instructions includedwith Microsoft Dynamics GP for information about registering the Modifier. Refer toChapter 15, “Accessing Modifications,” for more information about setting access tothe Modifier.

2. Select the product to modify.If you’re using additional products that integrate with Microsoft Dynamics GP,the following window will appear when you start the Modifier.

Select the product you want to modify, then click OK. If Microsoft Dynamics GPis the only product available, this window won’t appear.

If you have integratingproducts, use this window

to select the product tomodify.


Chapter 2: The Modifier InterfaceThis portion of the documentation describes the basic elements of the Modifierinterface. It is divided into the following sections:

• The Modifier main window and toolbar• Menus• Windows• Standard buttons

The Modifier main window and toolbar

When you start the Modifier, the Modifier’s main window and toolbar appear. Thetoolbar appears across the top of the main window. Each button that appearsrepresents a fundamental resource that you can view or edit. The following tabledescribes each button.

Each of these items is described in detail later in this manual.

Menus

The following items are available in the Modifier menu bar.

File: Generate Resource ReportsThis menu item prints a resource report for the application. The resource report is atext file that lists all resources in the current dictionary, their internal resource IDsand any resources associated with the listed resource. When you choose GenerateResource Reports, a dialog box will appear and allow you to name the report andselect its location.

File: Print SetupThis menu item opens the printer setup dialog box. This dialog box allows you toconfigure the currently selected printer.

File: Process MonitorThis menu option opens the Process Monitor window. This window displaysactivity for tasks that you choose to process in the “background” within yourapplication.

File: Microsoft Dynamics GPChoosing the menu item allows you to exit the Modifier and return to the mainapplication.

File: Table/Field/Window DescriptionsThese menu items open forms in the Resource Descriptions tool. This tool displaysinformation about all the tables, fields and windows used in the current dictionary.

Button DescriptionOpens the Data Types window, where you can view or edit existing data types.

Opens the Fields window, where you can view a list of fields in the application.

Opens the Forms window, where you can view a list of the modified forms in the application. You will also use this window to create new modified forms.



File: ExitThis menu item allows you to exit the application.

Edit: UndoThis menu item will undo the last keyboard entry in an editable field. It will alsoundo field movement and sizing in a layout window, but not the addition orremoval of fields, text or graphics from a layout window.

Edit: Cut/Copy/PasteThese menu items allow you to copy text or graphics to the Clipboard, then paste itin a different location. You cannot cut, copy or paste fields.

Edit: ClearThis menu item allows you to remove text from an editable field, or remove selecteditems from the layout area.

Edit: Select AllThis menu item allows you to select the entire entry in a field, or all items in thelayout area for a window, report or scrolling window.

Macro: (all)The items available from the Macro menu allow you to record and play macros.

Resources: (all)The items in the Resources menu allow you to access the various resources in theapplication. Resources available from this menu include all resources accessed fromthe toolbar, as well as other resources (such as formats and messages).

Windows:This menu displays a list of the windows currently open. Selecting a window fromthis menu makes the window active.

Help: LookupThis menu item opens any lookup window for the current field.

Help: ContentsThis menu item displays the contents topic for the Modifier online help.

Help: Search for Help OnThis menu item displays the search window for the help system, allowing you tosearch the Modifier online help.

Help: Window HelpThis menu item displays help for the current window in the Modifier.

Help: AboutThis menu item displays the About window for the main application.


C H A P T E R 2 T H E M O D I F I E R I N T E R F A C E

Windows

The Modifier uses several types of windows. Review the following descriptions tolearn how each is used.

Resource list windowsResource list windows display a list of resource names for a given resource type. Todisplay a resource list window, click a button in the Modifier toolbar or choose aresource from the Resources menu. When the window appears, select a resourcename and click Open to display its definition window.

The following illustration shows the Formats resource list window.

Definition windowsDefinition windows allow you to customize individual resources in an application.For example, you will use the Format Definition window to customize how data isdisplayed in fields.



Layout windowYou will use the Layout window to customize the appearance of windows in theapplication. The Layout window uses a graphics metaphor you may already befamiliar with: an assortment of tools you can use for drawing and creating objects; abuilt-in grid that allows easy alignment of objects on the window; moveable objectsin a layout like object-oriented drawing programs; and standard cut-copy-and-paste techniques so you can import graphics you create in other applications.

The Toolbox is available whenever the Layout window is open. It contains tools youwill use to add objects to the layout. The Properties window is used to specify thecharacteristics of windows, fields and drawn items when you’re customizing awindow layout.

Standard buttons

The following buttons are used throughout the Modifier:

Button DescriptionSaves changes and closes the current window.

Closes the current window without saving the changes to the window.

Allows you to save information for the current window without closing the window.

Creates a new resource.

Opens the selected resource and displays its definition.

Deletes the selected resource.

Allows you to insert items in a list, such as fields into a table definition.

Allows you to remove items from a list, such as the static text values in a list box.

The lookup button opens another window, allowing you to select a value to return to the current field. Typically, clicking the lookup button displays a list of resources. One of these resources can be selected and have its value returned to the current field.

PA

RT

2: M

OD

IFYIN

G FO

RM

S


Part 2: Modifying FormsThis portion of the documentation contains information about makingmodifications to forms. The following topics are discussed:

• Chapter 3, “Selecting Forms to Modify,” explains how to make modifications toforms and windows.

• Chapter 4, “Modifying Windows,” describes modifications you can make towindows.

• Chapter 5, “Modifying Scrolling Windows,” describes modifications you canmake to scrolling windows.

• Chapter 6, “Modifying Menus,” explains how to modify menus.

• Chapter 7, “Adding New Fields,” explains how to add new controls towindows.


Chapter 3: Selecting Forms to ModifyMost of the modifications you make will be to forms or to the windows contained inthose forms. Before you can make modifications, you must first locate the form tomodify. This portion of the documentation explains how to do this. The informationis divided into the following sections:

• Finding a form name• Creating a modified form

Finding a form name

To modify a form, you need to know its name. You can find a form’s name using theWindow Descriptions window, which is part of the Resource Descriptions tool. Usethe following steps to find a form’s name.

1. Find the name of a window you want to modify.In Microsoft Dynamics GP, open a window that you want to modify. Note thewindow title. You will use this name to find out which form the window is partof. For example, the following illustration shows the window title for theCustomer Maintenance window.

2. Open the Window Descriptions window.If you are in Microsoft Dynamics GP, open the Window Descriptions windowby pointing to Resource Descriptions in the Tools menu, then choosingWindows. If you are already in the Modifier, choose Window Descriptions fromthe File menu.

3. Locate the window.In the Window Descriptions window, set the Product, Series and View By fieldsto locate the window. For example, to locate the Customer Maintenancewindow in Microsoft Dynamics GP, the product is Microsoft Dynamics GP andthe series is Sales. Since you know the window display name (title), set the ViewBy field to sort windows by the Window Display Name. Now you can locate thewindow name in the list.

Note the window title.

Be sure to view thewindows by their display

names (titles).

Once you find the windowname, you can find the form

the window is part of.

P A R T 2 M O D I F Y I N G F O R M S


4. Find the form name.Once you have found the window display name in the list, you can find thename of the form the window is part of. Continuing the example, the CustomerMaintenance window is part of the RM_Customer_Maintenance form.

Creating a modified form

After you know the name of the form that contains the items you want to modify,start the Modifier. Then perform the following steps to create a modified version ofthe form.

1. Create a new modified form.If the Modified Forms window isn’t open, click the Forms button on the toolbarto display the list of Modified forms. Then click New to create a new modifiedform.

A window will appear, allowing you to select a form to modify.

2. Select the form to modify.From the window that appears, select the form that you want to modify, thenclick OK.

The Form Definition window will appear for the form you selected. The nameof the form will also be added to the Modified Forms list. You can then beginmaking modifications.

Click New to create a newmodified form.

Select the form thatyou want to modify,

and then click OK.


C H A P T E R 3 S E L E C T I N G F O R M S T O M O D I F Y

A copy of the form you selected to modify was added to the Forms dictionary,allowing you to make modifications to it. In Part 4, Storing and AccessingModifications, you will learn more about how modified forms are stored andaccessed.

If you simply want to modify a window in Microsoft Dynamics GP, you can save severalsteps. First, display the window you want to modify. Then point to Customize in the Toolsmenu and choose Modify Current Window. The Modifier will start, the form that containsthe window will be added to the list of modified forms, and the layout for the window will bedisplayed.


Chapter 4: Modifying WindowsChanging the appearance of windows is the most common modification made withthe Modifier. This portion of the documentation provides detailed informationabout how to modify windows. It is divided into the following sections:

• Opening a window layout• The Toolbox• The layout area• The layout grid• The Properties window• Window properties• Field properties• Drawn object properties• Previewing a window• Setting the tab sequence• Positioning the window• Adding fields to the window• Adding pictures• Linking fields to prompts• Resizing windows• Auto-complete• Linking fields to format fields

Opening a window layoutRefer to Chapter 3, “Selecting Forms to Modify,” for information about how to create a modified form.

To open the layout for a window, open the Form Definition window for the formthat contains the window. Click the Windows tab to display a list of windows forthe form. Select a window and click Open.

If you are viewing the window you want to modify, you can point to Customize in the Toolsmenu and choose Modify Current Window. The Modifier will start, the form that containsthe window will be added to the list of modified forms, and the layout for the window will bedisplayed.



The Toolbox and Layout window will appear, as shown in the followingillustration.

The Layout window and Toolbox use a graphics metaphor you may already befamiliar with: an assortment of tools you can use for drawing and creating textobjects; a built-in grid that allows easy alignment of objects on the window;moveable objects in a layout like object-oriented drawing programs; and standardcut-copy-and-paste techniques so you can import graphics you create in otherapplications.

Changes you make to windows are saved only when the Layout window is closed. Save yourwork often by closing the Layout window and then reopening it to continue modifying thewindow.

The ToolboxTo add and manipulate objects in the Layout window, use tools from the Toolbox.The following tools are available:

Tool Name Use

Arrow tool Select, resize and move objects in the window layout. Objects highlighted by the arrow tool can be dragged into position in the layout area.

Text tool Add text objects to the layout area. Select the text tool, then click in the appropriate location to type text in the layout.

Picture tool

Place pictures from the picture library in the layout area. Select the picture tool, then click the mouse in the desired location in the layout area; the Pictures window will appear. Select a picture and click OK.

Line tool Add lines to the layout area.

Shape tool Add rectangles, circles and other shapes to the layout area.


C H A P T E R 4 M O D I F Y I N G W I N D O W S

The toolbox also contains tools you can use to add new fields to a window. Addingnew fields is described in Chapter 7, “Adding New Fields.”

Clicking the Arrange tab in the Toolbox displays additional tools used to align,resize or tile fields in the window. These tools are described in the following table.

Tool Name Tool NamePush button tool Drop-down list tool

Combo box tool List box tool

Multi-select list tool Big text tool

String tool Integer tool

Currency tool Date tool

Time tool Visual switch tool

Horizontal list box tool Radio group tool

Radio button tool Check box tool

Progress indicator tool

Category Tool Name UseAlign Align to Top Aligns the selected objects with the top object in the

group.

Align to Left Aligns the selected objects with the leftmost object in the group.

Align to Right Aligns the selected objects with the rightmost object in the group.

Align to Bottom Aligns the selected objects with the bottom object in the group.

Size Size to Shortest Shrinks the selected objects to the height of the shortest object in the group.

Size to Narrowest Shrinks the selected objects to the width of the narrowest object in the group.

Size to Widest Enlarges the selected objects to the width of the widest object in the group.

Size to Tallest Enlarges the selected objects to the height of the tallest object in the group.

Size to Default Resizes the field to its default size, based upon how the visual properties for the field are set.



Arranging objects can’t be undone. Be sure to save your window layout before arrangingobjects. If you aren’t satisfied with the result of an arrangement, you can close the windowwithout saving the changes.

The position and size coordinates for the currently-selected object are displayed at the bottomof the Toolbox. Use these values to accurately position and size objects.

The layout area

The layout area is where you add fields, controls, graphics and text used by thewindow. This area represents the size of the window as it will appear at runtime,exclusive of native operating system controls such as title and scroll bars. To changethe size of the window, drag the resize handles to adjust the width and height of thewindow.

The layout area doesn’t display controls that are specific to the operating system,such as scroll bars, resize boxes, minimize controls and title bars. Instead, operatingsystem elements are created automatically.

It’s important to remember that items appearing in the layout area can looksomewhat different than how they will appear at runtime. At runtime, all objectsadded to the layout area will appear in the window drawn properly.

Use the Show Field Names and Show Invisible Fields items in the Layout menu tospecify how fields will be displayed in the layout window. If you mark the ShowField Names menu item, fields will show their field names, rather than their normaldisplay characteristics. If you choose not to show field names, fields will displaymuch like they do at runtime. The following table shows how several fields appearin the layout and how they appear at runtime:

Tile Tile Horizontally Tiles the selected objects horizontally. The value in the Space field specifies the space between objects.

Tile Vertically Tiles the selected objects vertically. The value in the Space field specifies the space between objects.

Category Tool Name Use

The layout area represents thesize of the window as it will

appear at runtime.

The resize handles allow youto change the dimensions of

the window.

Showing field names Not showing field names At runtime



If you mark the Show Invisible Fields item in the Layout menu, those fields whoseVisible property is set to false will be displayed in the layout. Invisible fields aretypically used to store values used by Microsoft Dynamics GP. They aren’t visiblewhen the accounting system is running.

Each object in the window layout can be selected with the arrow tool, then draggedto a different position in the layout area. You also can move selected graphics, textor fields in front of or behind other objects by choosing Send To Front or Send ToBack from the Layout menu.

The layout grid

The layout window has a grid that’s activated automatically when you open thewindow. When the grid is active, a check mark appears next to the Grid item in theLayout menu. Objects you add to the layout area will be aligned to the gridautomatically, but existing objects in the layout area won’t be aligned to the grid. Toalign existing object to the grid, be sure the grid is active, then select the objects withthe arrow tool and choose Align To Grid from the Layout menu.

It’s a good idea to use the layout grid when adding or rearranging items in thelayout area, so items will be aligned automatically. If you want to display the grid inthe layout area, choose Show Grid from the Layout menu. To display the gridbehind objects in the layout window, choose Grid to Back. To deactivate the grid,choose Grid from the menu to remove the check mark.

You can use the arrow keys to move selected items in the window one pixel at a time,regardless of whether the grid is turned on.

The Properties window

The Properties window is used to set several characteristics of the window and theobjects in the window. To display the properties for the window, select Propertiesfrom the Layout menu. If it isn’t already open, the Properties window will appear.

Select an object in the layout area and click the tab indicating which type ofproperty you want to view. Click the Object or Visual tab, depending on the type ofproperty you want to view. To set a property, select it in the list and then change itsvalue in the settings box.

To set the value of aproperty, select it in the

list. Then set its value inthe settings box.

Click a tab to display thecorresponding list of

properties.Settings box



Setting the property value involves choosing a value from a drop-down list, typinga value, or using a lookup. Some properties listed can’t have their values changed.

Double-clicking a property in the properties list is a shortcut to setting its value. Forinstance, double-clicking a property whose value is set with a drop-down list will set theproperty to the next value in the list.

Window properties

To view window properties, be sure the Properties window is open. Select the arrowtool from the Toolbox and click in the layout window outside of the window’s areato select the window. The window is selected when resize handles appear on itsperimeter. The following table lists the window properties. Asterisks indicate theproperties that can be changed using the Modifier.

Property type Description

Some properties are set using a drop-down list.

Some properties have the value entered directly.

Some properties use a lookup to retrieve values.

Some properties can’t be set.

Object property Description

AutoLinkTable Indicates the table auto-linked to the window. You can add fields from the auto-linked table to the window.

AutoOpen If set to true, the window opens automatically when the form opens. By default, this value is set to true.

CloseBox* If set to true, the close box on the window will be active.

HelpContextID Lists the help context ID value for the window.

Name The name of the window. This name is used to refer to the window in scripts.

Resizeable* If set to false, the window cannot be resized by the user. If set to true-automatic, the window can be resized and the appropriate fields will be resized automatically. If set to true-per field, the window can be resized, but the resize characteristics must be specified for each individual field.

Title* The name that is displayed in the title bar of the window.

WindowID Lists the resource ID of the window.

WindowType Indicates whether the window is a primary window, modal dialog, modeless dialog, wizard, lookup, toolbar, palette, or internal.

Visual property Description

BackColor* If set to true, sets the background area of the window to the window background color specified by the operating system. If set to false, the background of the window will be white.

ControlArea* If set to true, a band called the control area will be displayed across the top of the window.

Position-Left* Indicates the position of the left edge of the window, measured in pixels from the left edge of the screen.

Position-Top* Indicates the position of the top edge of the window, measured in pixels from the bottom edge of the toolbar.



Field properties

The following table lists the field properties. Asterisks indicate the properties thatcan be changed using the Modifier.

Size-Height* Indicates the window height, measured in pixels.

Size-Width* Indicates the window width, measured in pixels.



AutoComplete For string fields, specifies whether the field will use the auto-complete capability. If this property is set to true, the contents of the field will automatically be completed as the user types, based on a list of values associated with the field.

AutoCopy Specifies whether information is automatically transferred between the field and the corresponding field in the table. If set to false, the field will be unaffected by processing that copies information to or from the field.

Cancel If this property is set to true, the process associated with this field will be run when the user presses ESC while the window containing the field is active. This property is typically set to true for a Cancel push button field. This property is available only for push button fields.

DataType Indicates the data type used for the field.

Default If this property is set to true, the process associated with this field will be run when the user pressing the ENTER key or double-clicking a list box or scrolling window with the DefaultDblClick property set to true. The Default property is typically set to true for an OK or Save push button field. This property is available only for push buttons.

DefaultDblClick Setting this property to true allows the user to double-click a list box field to accomplish the action of selecting an item and clicking the push button whose Default property is set to true.

DisableLookup* If set to true, prevents a lookup form associated with the field from opening when a user chooses the Lookup menu item.

DraggableCols Applies only when the list view is displayed in report view mode. True indicates the user can reorder columns by dragging them. False indicates columns can’t be reordered by the user.

Editable* Specifies whether the user can edit the contents of the field.

EditMode* For text fields, this property specifies how text fields can be edited. If set to DisplayOnly, the text field can’t be edited. If set to Editable, the field can be edited. If set to SelectOnly, text can be selected, but not changed.

EndTransaction When set to true, this property indicates that all processing for a transaction will be completed when the button is clicked. This property is available only for push button fields.

Field Indicates the field being used and allows you to view characteristics of the field definition.

FieldID Indicates the resource ID of the field.

FieldType Indicates whether the field is a global field or a local field.

HelpContextID Lists the help context ID value for the field.

Hyperspace When set to true, the push button can be clicked without performing any pending processing for the currently-focused field. Only the process for the push button that was clicked will be run. Typically, this property is set to true for Cancel buttons. It is available only for push button fields.

LinkedFormat Lists the format field linked to the current field.

LinkedLookup Lists the lookup field (typically a push button) linked to the current field.

LinkedPrompt List the prompt linked to the field.

MultiSel True indicates multiple items can be selected in the list view. False indicates only one item can be selected.



Password* If set to true for string fields, the field will display Xs instead of the data entered in the field. This is typically used for password fields.

Required* Specifies whether the field is required for the record or transaction to be saved correctly. Set this value to true when you want to be sure the user enters a value in this field. Also, if this property is set to true, and the Show Required Fields menu item is selected, any prompt linked to the field will be displayed according to the color and style specified in the User Display Preferences window.

The Required property can’t be unmarked for fields already marked as required for the original form. However, the fields you set as required can be unmarked at a later time.

SavedOnRestart* If set to true, causes the field to keep the value that was last entered in it, when the form or window is restarted. If set to false, a restart will clear the field.

ScrollBars* If set to true, a text field will have scroll bars. If set to false, no scroll bars will be displayed.

SetChangeFlag* Specifies whether changes to a field’s value will set the change flag for the form or window. If set to true, the change flag will be set when the contents of the field change. If set to false, the change flag won’t be set.

SortMethod Specifies how items in list view or tree view fields are sorted.

TabStop* Specifies whether to include a window field in the tab sequence. If set to true, the window field will be in the tab sequence.

Tooltip* Specifies the tooltip that will be displayed for the field.

UseUniqueHelp If set to true, a unique HelpContextID will be generated for this instance of the field. If set to false, the same HelpContextID will be generated for all instances of this field in the application.

VisibleItems* For drop-down list and combo box fields, specifies the maximum number of items displayed when the list is displayed in the dropped position.

WordWrap* For text fields, specifies whether text will wrap.


Alignment* Specifies whether the item is left-, center- or right-aligned.

AltLineColor* If set to true, alternate lines of the list view will appear with a different color.

Appearance* For edit fields, specifies what type of border the field will have. For push buttons, button drop lists and push button-style check boxes, setting this property to 3D Highlight causes the button to have a flat appearance until the mouse pointer passes over the button.

BackColor* Specifies the background color of the field.

Border* If set to true, a border is drawn around the field.

Direction* For progress indicator fields, indicates the direction the bar will move in the progress indicator.

DropIndicator* For button drop list fields, specifies whether the drop indicator will be displayed.

DropPosX* For button drop list fields, specifies the distance in pixels the drop indicator will be drawn from the right edge of the control.

DropPosY* For button drop list fields, specifies the distance in pixels the drop indicator will be drawn from the bottom edge of the control.

ExpandButtons* For tree view fields, setting this property to true causes expansion buttons to be shown for nodes that have children.

Font* Specifies the font to use for the field.

FontColor* Specifies the color of the text for the field.

FontBold* If set to true, the field text will be displayed in bold type.




FontItalic* If set to true, the field text will be displayed in italic type.

FontUnderline* If set to true, the field text will be underlined.

FullRowSelect* When set to true, the entire row in the list view field is selected. When set to false, individual row items can be selected. Applies only when the list view is displayed in report view mode.

GridLines* When set to true, grid lines are drawn between items in the list view. Applies only when the list view is displayed in report view mode.

ImageSize* Specifies how list view images are sized. System indicates the images will be scaled to standard system sizes (16 by 16 or 32 by 32 pixels). First Image indicates images will be scaled to the size of the first image defined for the list view field.

Indent* For tree view fields, specifies how many pixels child nodes are indented from the parent. The value 0 allows the control to automatically specify the amount.

IndicateColor* Specifies the color of the progress indicator blocks or bar.

Lines* Specifies how lines are drawn in the tree view field. If set to None, no lines are drawn. If set to TreeLines, lines are drawn for nodes below the root level. If set to RootLines, lines are drawn for all nodes.

Pattern* Specifies the pattern to apply to the background.

PatternColor* Specifies the color of the pattern that is applied to the background.

PatternSelect* Specifies the pattern used when a push button-style check box is selected.

Position-Left* Indicates the position of the left edge of the field, measured in pixels from the left edge of the window.

Position-Top* Indicates the position of the top edge of the field, measured in pixels from the top of the window.

Resize-Horizontal* Specifies the horizontal resize behavior when per field resizing is used. Refer to Resizing windows on page 33 for more information.

Resize-Vertical* Specifies the vertical resize behavior when per field resizing is used. Refer to Resizing windows on page 33 for more information.

Scaling* For picture fields, specifies how the picture pasted into the field will be scaled. Proportional indicates the picture will maintain its original size and proportions. Stretch indicates the picture will be stretched to fill the picture field.

ShowHeadings* When set to true, column headings are shown in the list view. Applies only when the list view is displayed in report view mode.

ShowPartialItems* For native list boxes, setting this property to true causes the list box to be drawn exactly the height indicated in the layout window. If there isn’t enough room to display the last item, it will be only partially drawn. When this property is set to false, the list box will be resized vertically to include just the last complete item.

ShowSelection* For tree view and list view fields, indicates whether the selected node or item is indicated when the field does not have focus.

Size-Height* Indicates the field height, measured in pixels.

Size-Width* Indicates the field width, measured in pixels.

Style* For push button and button drop list fields, specifies whether the button will display text only, graphics only, or both text and graphics. It also specifies the arrangement of the text and graphics.For check box fields, specifies whether the field displays as a standard check box or a push button.For progress indicator fields, specifies whether the progress indicator is composed of blocks or is a solid rectangle.

Visible* If set to true, the field will be visible. If set to false, the field will be hidden.

Fields can’t be made invisible if they have the Required property set to true.




Drawn object propertiesThe following table lists the drawn object properties. Asterisks indicate theproperties that can be changed using the Modifier

Previewing a windowAs you make modifications to a window, it’s useful to see how the window willappear when it’s displayed. To do this, choose Preview from the Layout menu.Remember that this is only a preview of the visual characteristics of the window;the window will not be functional. When you have finished, close the previewwindow to return to the Layout window.

Zoom* For push button fields, setting this property to true causes the pointer to become the zoom pointer (magnifying glass) when it’s moved over the field. Typically, the Visible property is also set to false to make the push button invisible.


Property Description

Alignment* For static text, indicates whether the text is left, center, or right-aligned.

Appearance* Specifies whether the drawn object is displayed with a 2-D or 3-D border.

BackColor* Specifies the background color of the object.

Border* For static text, specifies whether a border is drawn around the object.

Font* Specifies the type style and size to use for static text.

FontBold* If set to true, static text will be displayed in bold type.

FontColor* For static text, specifies the color of the text.

FontItalic* If set to true, static text will be displayed in italic type.

FontUnderline* If set to true, static text will be underlined.

LineColor* Specifies the color of the line used to draw the object.

LineSize* Specifies the width of the line used to draw an object.



Position-Left* Indicates the position of the left edge of the object, measured in pixels from the left edge of the window.

Position-Top* Indicates the position of the top edge of the object, measured in pixels from the top of the window.

Resize-Horizontal* Specifies the horizontal resize behavior when per field resizing is used. Refer to Resizing windows on page 33 for more information.

Resize-Vertical* Specifies the vertical resize behavior when per field resizing is used. Refer to Resizing windows on page 33 for more information.

Shape* Specifies the shape of an item drawn with the shape tool.

Size-Height* Indicates the object height, measured in pixels.

Size-Width* Indicates the object width, measured in pixels.

Zoom* For static text items, setting this property to true causes the text to be displayed as specified by Zoom Fields settings in the User Display Preferences window.



Setting the tab sequence

A tab sequence is the order in which the focus moves through fields in a windowwhen the TAB key is pressed. You may want to change a tab sequence to change theorder in which users enter information, ensuring they enter information youconsider most important first.

Setting a tab sequence is typically one of the last tasks you need to complete whenmodifying a window. After you’ve arranged the fields in the desired order, use thefollowing procedure to set a tab sequence.

1. Choose Set Tab Sequence from the Layout menu.

2. Select the field you want first in the sequence by double-clicking the field. The focus will appear in this field when the window is opened initially. Thefield you double-click will appear shaded, meaning that it’s now the first fieldin the tab sequence.

3. Press the TAB key.

4. Double-click the field you want next in the sequence. The field will appear shaded, indicating it’s the next field in the tab sequence.

5. Press the TAB key again and double-click the field you want third in the tab sequence.Continue to mark fields in the window in the order you want, using the mouseto double-click the field and the TAB key to move the focus to the next object inthe sequence.

6. Test the tab sequence.When the tab sequence for all the fields in the window has been set, press theTAB key several times to move through the tab sequence. When you’ve finishedsetting the tab sequence, choose Set Tab Sequence from the Layout menu.

You can use the TabStop property to exclude fields from the tab sequence.

You can stop the process of setting a tab sequence at any time by closing the Layoutwindow and choosing not to save the changes to the window.

To make radio buttons work properly in your application, the radio group andradio button fields must be arranged properly in the window. In the tab sequence,the radio group must come immediately before the radio buttons. For example, in thePayment Method radio group shown in the following illustration, the PaymentMethod radio group field comes immediately before the Cash, Check and Chargeradio button fields in the tab sequence.

In the tab sequence, theradio group field comesimmediately before the

radio button fields.



Positioning the window

You can also specify the position of the window using the Position properties for the window.

You can specify the opening position of each window. This allows you to arrangewhere a group of windows will appear on the screen, reducing the time users spendorganizing windows on their screen.

You should be aware of the other objects, such as palettes or other windows, thatwill be on the screen at the same time as the window you’re positioning. Use thefollowing procedure to position a window in your application.

1. Choose Position Window from the Layout menu.The Position Window window will appear in the location where the windowwill be positioned. The default position and size coordinates are displayed inthe window.

2. Drag the window to the location you want it to appear when opened.Note that the coordinates change each time you move the window. Use thecoordinates in the window to more accurately position this window. When thewindow is positioned in the proper location, click OK.

Adding fields to the windowInformation about creating new fields is found in Chapter 7, “Adding New Fields.”

You can use the Modifier to add fields from a window’s auto-linked table, enablingyou to display a more extensive range of information. Many Microsoft DynamicsGP windows are automatically linked to a particular table, making transfer ofinformation between the window and table easier.

Some forms have several tables linked to them. However, each window can haveonly one auto-linked table. You can add fields from the window’s auto-linked table(displayed in the Properties window), but not from any other tables that may belinked to the form (displayed in the Form Tables window).

To add a field to the window, use the following steps.

1. Drag the field to the window.Select the appropriate field name from the window’s auto-linked table and dragit to the layout area.

2. Set properties for the field.Setting field properties is described earlier in this chapter.

In most cases, it’s best to make the fields that you add to a window display-only. Ifyou add editable fields to a window’s layout, be sure to test the modified windowthoroughly. Use the lesson company to verify that information contained in the fieldis updated correctly, especially if the same field appears in more than one windowwithin the same form.

Use this drop-down list toview the fields from the

window’s auto-linked table.

To add a field to the window,drag it from this list to the

layout area.



Adding picturesGraphics, such as a company logo, can be added to windows using standard cut-copy-and-paste techniques. If you want to use several custom graphics throughoutyour application, you can store these graphics in the picture library. This libraryallows you to add, name and store specific graphics in the forms dictionary. Addingpictures to the picture library is described in Chapter 11, “Pictures and NativePictures.”

If you paste a picture directly into the layout area, you’ll be prompted to name the picture.The picture will appear in the layout and be added to the picture library automatically.

Linking fields to promptsYou can link a field to the text prompt associated with it by using the Link Promptitem in the Tools menu. By linking a field to its prompt, the prompt can indicate thestatus of the field, such as if the field is disabled or required.

To link a field to a prompt, choose Link Prompt from the Tools menu. Click on thefield and drag the mouse pointer to its prompt (the text describing the field). Aflashing black line will indicate that the link was made. Linking a prompt is shownin the following illustration.

When you’ve finished, choose Link Prompt again to turn prompt linking off.

Resizing windowsWindows in Microsoft Dynamics GP can be resized by the user when they aredisplayed. The ability to resize a window is controlled by the Resizeable propertyfor the window. If set to True, the window can be resized. Two types of resizing ofresizing are supported: automatic and per field.

Automatic resizingWith automatic resizing, fields such as list boxes, text fields, tree views and listviews will resize automatically when the window is resized. To use automaticresizing, set the Resizeable property for the window to True-Automatic. Noadditional work is required.

Automatic resizing was the type supported in earlier versions of Microsoft Dynamics GP.

When a window contains many fields, the rules necessary to properly resize thewindow and maintain the proper appearance become very complex. When awindow layout becomes too complex for the runtime engine to automatically resizethe window, it will no longer try to resize the controls in the window. When thisoccurs, you need to use per field resizing.

Per field resizingTo use per field resizing, set the Resizeable property for the window to True-PerField. You must then specify the Resize Horizontal and Resize Vertical propertiesfor each field in the window. These two properties specify the resize characteristicsof the field.

You can specify resize characteristics for static text and drawn objects, as well.



The following tables describe the possible values for these properties:

Resize Horizontal

Resize Vertical

Value Description

Grow The field will keep its current horizontal position and grow horizontally by the same amount as the window.Example: When the window is resized 100 pixels wider, the field will maintain its horizontal position and be 100 pixels wider.

Stay Centered The field will keep its current horizontal size, but will slide horizontally at half the amount the window grows.Example. When the window is resized 100 pixels wider, the field will maintain its horizontal size and slide 50 pixels to the right.

Stay Left The field will keep its current horizontal size and horizontal position.Example: When the window is resized 100 pixels wider, the field will maintain its horizontal size and position.

Stay Left - Grow The field will keep its current horizontal position, and grow horizontally by half the amount the window grows.Example: When the window is resized 100 pixels wider, the field will maintain its horizontal position and be 50 pixels wider.

Stay Right The field will keep its current horizontal size, and move horizontally to maintain a constant distance from the right edge of the window.Example: When the window is resized 100 pixels wider, the field will slide 100 pixels to the right.

Stay Right - Grow The field will grow horizontally at half the amount the window grows, and move horizontally to maintain a constant distance from the right edge of the window.Example: When the window is resized 100 pixels wider, the field will slide 100 pixels to the right and be 50 pixels wider.

Value Description

Grow The field will keep its current vertical position and grow vertically by the same amount as the window.Example: When the window is resized 100 pixels taller, the field will maintain its vertical position and be 100 pixels taller.

Stay Bottom The field will keep its current vertical size, and move vertically to maintain a constant distance from the bottom edge of the window.Example: When the window is resized 100 pixels taller, the field will slide 100 pixels down.

Stay Bottom - Grow The field will grow vertically at half the amount the window grows, and move vertically to maintain a constant distance from the bottom edge of the window.Example: When the window is resized 100 pixels taller, the field will slide 100 pixels down and be 50 pixels taller.

Stay Centered The field will keep its current vertical size, but will slide vertically at half the amount as the window grows.Example. When the window is resized 100 pixels taller, the field will maintain its vertical size and slide 50 pixels down.

Stay Top The field will keep its current vertical size and vertical position.Example: When the window is resized 100 pixels taller, the field will maintain its vertical size and position.

Stay Top - Grow The field will keep its current vertical position, and grow vertically at half the amount the window grows.Example: When the window is resized 100 pixels taller, the field will maintain its vertical position and be 50 pixels taller.



The following illustration shows a window that is too complex to be resizedautomatically. The horizontal and vertical resize characteristics of each field areshown.

Auto-complete

You can use the AutoComplete property for string fields to automatically fill thecontents of the field as the user types, based on the values previously entered for thefield.

To use the auto-complete capability for a string field, you must set theAutoComplete property to true for every occurrence of the field for which you wantthe functionality. When a user adds a value to the field and moves the focus, thevalue is added to the auto-complete list for the field.

When the user begins to type characters into a field with the AutoCompleteproperty set to true, the auto-complete list for the field will be examined to find anymatches. The matching items will be displayed in a drop-down list. The user cancontinue typing a value to refine the items listed, or use the arrow keys or mouse toselect one of the items in the list. If drop-down list isn’t large enough to fully displaythe auto-complete items, use the resize area in the corner of the list to expand thelist.

To remove an item from the auto-complete list, right-click the item and chooseRemove From List in the menu that appears.

If the same global field appears in multiple windows, and the AutoCompleteproperty is set to true for each instance, the fields will share the auto-complete data.Auto-complete values entered in one field will also be available in the other fieldinstances. The behavior is the same for a local field that appears in multiplewindows within a form. If each instance of the local field has the AutoCompleteproperty set to true, the local field will share the auto-complete data.

Horizontal: GrowVertical: Stay Bottom

Horizontal: Stay LeftVertical: Stay Top

Horizontal: Stay LeftVertical: Grow

Horizontal: GrowVertical: Grow

Horizontal: Stay RightVertical: Stay Top

If any matches are found in theauto-complete list, thematching items will be

displayed in a drop-down list.



If the auto-complete field has a linked-lookup button, an additional item willappear at the bottom of the auto-complete list. Choosing this item will open thelookup window, just as if the lookup button had been clicked.

Values are added to the auto-complete list for a field any time the focus moves tothe field, the content of the field changes, and the focus leaves the field. A userchanging a field’s value, or a lookup window returning a value are common waysthat values are added to the auto-complete list.

Auto-complete items are written to a file that is stored in the “Application Data”folder for the user currently logged into the workstation. By default, this folder ishidden in Windows Explorer. The auto-complete values stored in this table will beused the next time Microsoft Dynamics GP is run. To remove the auto-completeitems for a user, you must delete the table that stores the items.

Linking fields to format fields

This is an advanced formatting feature. You may want to skip this section until you have a better understanding of the Modifier.

The formatting displayed for certain string and currency fields in MicrosoftDynamics GP is based on the value of an integer field called a format field. A formatfield is designated by choosing Link Format Selector from the Tools menu while thelayout window is active. The Modifier will switch to format linking mode, allowingyou to link the string or currency field to the format field. The Modifier will stay inthis mode until you choose Link Format Selector from the Tools menu again.

While the Modifier is in format linking mode, you can link fields to format fields bydragging from a currency or string field to the integer field you want to link it to. Aflashing border around the integer field will indicate that the link was successful.The value of the integer field indicates which format string should be used for thecurrency or string field. The integer field can be an invisible field or a field such as adrop-down list, allowing the user to specify the format.

Formatting currency fieldsThe possible formats for currency fields and the integer value associated with themare shown in the following table.

Choosing this itemperforms the same action

as clicking the lookupbutton for the field.

Integer Format Integer Format

0 Control panel defaults 10 $1,234.567

1 1,234 11 $1,234.5678

2 1,234.5 12 $1,234.56789

3 1,234.56 13 1,234%

4 1,234.567 14 1,234.5%

5 1,234.5678 15 1,234.56%

6 1,234.56789 16 1,234.567%

7 $1,234. 17 1,234.5678%

8 $1,234.5 18 1,234.56789%

9 $1,234.56



The integer value used to indicate the format used can be stored in a table alongwith the currency field being formatted. When the record is retrieved from the table,the currency field will display as it did when the record was saved. The format fieldcan also be used for a report, allowing the currency field to appear in the report as itdid when it was saved in the table.

Microsoft Dynamics GP can define its own formats, in addition to those shown in theprevious table. This capability is used to define currency format information formulticurrency support.

Formatting string fieldsFor string fields, the integer value indicating the format to use corresponds to theposition of the format string in the Format Definition window.

The following example describes a Part Number field that has three different formatstrings. The user selects the format to apply by selecting the corresponding formatin a drop-down list linked to the Part Number field. The three format strings for thePart Number field, entered in the Format Definition window, are shown in thefollowing illustration.

The drop-down list is set to the following value (integer 3), corresponding to thethird format string:

The Part Number field will display the following format:

Using format fieldsUnless you are creating your own fields, the presence of a format field typicallywon’t affect modifications you make to a window. You need to watch for fields thathave their LinkedFormat property set. If you make modifications to these fields, besure the LinkedFormat property remains unchanged.

Another situation to be aware of occurs when Microsoft Dynamics GP uses a formatfield to apply multicurrency formatting to currency fields in transaction entrywindows. All of the currency fields in the window will be linked to a hidden formatfield typically named Currency Index. The value of this hidden field indicates whatmulticurrency formatting will be applied to all of the currency fields linked to it. Ifyou add currency fields to the window, be sure to link those fields to the sameformat selector field that Microsoft Dynamics GP uses.

This format string is used whenthe format selector value is 2.

This format string is used whenthe format selector value is 3.

This format string is used whenthe format selector value is1.



All of the currency fields inthis window are linked to the

Currency Index field, whichspecifies their formatting.


Chapter 5: Modifying Scrolling WindowsMicrosoft Dynamics GP has special windows called scrolling windows that allowthe user to scroll through or enter information into tables. Scrolling windows arecontained in standard windows. This portion of the documentation providesinformation about how to modify scrolling windows. It is divided into thefollowing sections:

• Opening a scrolling window layout• The layout area• Scrolling window properties• Adding fields to a scrolling window

Opening a scrolling window layout

Scrolling windows appear inside of standard windows. A scrolling window isshown in the following illustration.

The prompts for the scrolling window appear above it in the window layout. Tomodify these prompts, simply edit them in the window layout. If you want tomodify the appearance of the scrolling window, you must open a second layoutwindow. To do this, select the scrolling window and choose Open Scrolling Windowfrom the Tools menu. A second layout window will appear, allowing you to edit thecontents of the scrolling window.

You can also open a scrolling window by double-clicking it in the window layout thatcontains it.

The layout area

When you open a scrolling window, a second layout area is displayed. This layoutwindow is similar to the standard layout window, but is used only to edit scrollingwindows.

Scrolling windows are composed of lines. In the scrolling window layout, only oneline of the scrolling window is shown. When the scrolling window is displayed, thisline is drawn repeatedly, until the scrolling window is full.

The prompts above thescrolling window indicate

the information thatappears in the window.

Scrolling windows areedited in a separate

layout window.



Scrolling windows can display information in two modes: normal and expanded. Thescrolling window layout specifies what items are displayed in each mode. The areain the scrolling window layout that corresponds to one line in normal mode is thearea between the top of the window and the first dashed line. This area is called thesmall line item. The area in the scrolling window layout that corresponds to the extraitems displayed in expanded mode is the area between the second dashed line andthe small line item. This area is called the big line item.

To mark the small line item, choose Mark Small Line Item from the Tools menu andclick where you want the dashed line to appear. You may need to move fields out ofway to see where the small line item is placed. To mark the big line item, chooseMark Big Line Item from the Tools menu. Click where you want the line to appear.Note that the big line item must be marked in multiples of the height of the smallline item.

The following illustration shows the layout for the IV_Transfer_Scroll scrollingwindow. In normal mode, the window will display the Item Number, Unit ofMeasure, Quantity and Unit Cost. In expanded mode, it will also display theDescription, From Site and To Site.

The small line item is markedhere. In normal mode, items in

the small line item are displayedin the scrolling window.

The big line item is marked here.In expanded mode, items in both

the big line item and small lineitem are displayed in the

scrolling window.

This is how the scrollingwindow displays information

in normal mode.

The horizontal and verticallines were drawn in the

scrolling window layout usingthe line tool.

This is how the scrollingwindow displays information

in expanded mode.


C H A P T E R 5 M O D I F Y I N G S C R O L L I N G W I N D O W S

Scrolling window properties

Before viewing properties, be sure the Properties window is open. To view thescrolling window’s object properties, the scrolling window layout must be open.Once the layout is open, select the arrow tool from the Toolbox and click in theLayout window outside of the scrolling window’s area to select it. The scrollingwindow is selected when resize handles appear on its perimeter. The followingtable lists the scrolling window object properties.

To view the scrolling window’s visual properties, only the window that contains thescrolling window must be open. Select the arrow tool from the Toolbox and click inthe scrolling window to select it. The following table lists the scrolling windowvisual properties.


DefaultDblClick In a browse-only scrolling window, setting this property to true allows the user to double-click a line in the scrolling window to accomplish the action of selecting a line and clicking the push button whose Default property is set to true.

HelpContextID Lists the help context ID value for the scrolling window.

LinkTable This is the table linked to the scrolling window. Records displayed in the scrolling window come from this table.

LinkTableKey This is the key for the linked table that specifies the default sorting order for records in the scrolling window.

Name This is the name of the scrolling window.

ScrollToBottom Setting this option to true causes the scrolling window to display records at the end of the linked table, rather than at the beginning. In effect, the scrolling window has been scrolled to the bottom of the table.

WindowID Lists the resource ID of the scrolling window.

WindowType Specifies whether the scrolling window is browse-only, editable or adds-allowed.An adds-allowed scrolling window has a blank line at the bottom of the window where the user can add new records and save them in the linked table.A browse-only scrolling window allows the user to select only one line in the scrolling window and make no changes.An editable scrolling window allows the user to edit and change the contents of lines in the scrolling window. These changes can be saved in the linked table.


AltLineColor* If this property is set to true, alternate lines of the scrolling window will appear with a different color.

Appearance* Specifies whether the scrolling window has a 2-D or 3-D border.

BackColor* Specifies the background color of the scrolling window.

FontColor* Specifies the color of the text in alternate lines of the scrolling window.



Position-Left* Indicates the position of the left edge of the scrolling window, measured in pixels from the left edge of the window.

Position-Top* Indicates the position of the top edge of the scrolling window, measured in pixels from the top of the window.

Resize-Horizontal* Specifies the horizontal resize behavior for the scrolling window when per field resizing is used. For more information, refer to Resizing windows on page 33 for more information.



Adding fields to a scrolling window

You can add fields to the scrolling window from the linked table. Adding fields to ascrolling window is similar to adding fields to a standard window. Simply select thefield in the Toolbox and drag it to the layout area. Be sure you place the field ineither the small line item or the big line item. Otherwise, it won’t be displayed in thescrolling window.

Resize-Vertical* Specifies the vertical resize behavior for the scrolling window when per field resizing is used. For more information, refer to Resizing windows on page 33 for more information.

Size-Height* Indicates the scrolling window height, measured in pixels.

Size-Width* Indicates the scrolling window width, measured in pixels.



Chapter 6: Modifying MenusMicrosoft Dynamics GP provides a set of command-based menus that allownavigation for the application. These menus cannot be accessed with the Modifier.You can use the Modifier to make changes to the menus that are part of individualforms. Form-based menus appear as additional menus for individual windows inMicrosoft Dynamics GP. This chapter is divided into the following sections:

• Opening a menu definition• Editing menu items

Opening a menu definition

To open a menu definition, first open the Form Definition window for the form themenu is part of. Click the Menus tab to display a list of menus for the form. Select amenu and click Open.

The Menu Definition window will appear, as shown in the following illustration.



Editing menu items

You can edit the display name and the names of the items in each menu attached tothe form.

Display nameThe display name is the name that appears when the menu is displayed as asubmenu.

You can define an access key for the menu by placing an ampersand (&) in the menudisplay name. The ampersand won’t be displayed in the menu name. Instead, thecharacter immediately following the ampersand will be underlined. To choose themenu, a user can press the ALT key and the underlined character at the same time.

Menu itemsThe items in the menu are listed in the Menu Items list. To change the name of amenu item, select it in the list and then edit it in the Item Name field. The &, #, -, and~ characters have special meaning in menu item names. These characters aredescribed in the following table.

You can define a shortcut for the menu item by selecting a value from the Shortcutfield. The shortcut is CTRL + the specified character. To avoid conflicts, be sure theshortcut key isn’t used more than once.

Character Effect

& Causes the next character to appear underlined and act as the access key.

# Draws an ellipsis (…) after the item.

- If used as the item name, causes a separator line to appear in the menu. Use separator lines to group items in the menu.

~ Draws a forward slash (/).


Chapter 7: Adding New FieldsYou can also use the Modifier to create and add new fields to windows. Thiscapability is designed primarily for users who also use Visual Basic for Applications(VBA), Visual Studio Tools for Microsoft Dynamics GP, or the Continuum API tofurther customize Microsoft Dynamics GP. Any of these code developmentmechanisms can use new fields created with the Modifier.

Information about adding new fields is divided into the following sections:

• Creating local fields• Using the Toolbox• Adding prompts• Control types• Working with controls

Creating local fields

Local fields are specific to a single form, and all windows from the form will haveaccess to the local fields. To add a local field to a window, perform the followingsteps.

1. Open the window layout.Open the window layout for the window on which you want to add a newfield.

2. Create a new local field.In the Toolbox, choose Local Fields in the drop-down list specifying the type offields to display.

Choose Local Fields inthis drop-down list.

Click New to create anew local field.



Click New; the Local Field Definition window will appear.

3. Name the field and set the field characteristics.Name the field and specify its characteristics. You can specify the followingcharacteristics:

Array Size An array field contains multiple occurrences of the same type ofinformation. The individual pieces of information stored by the array field arereferred to as elements. The array size of a field indicates the number of elementsthat will be included in the array field. If the field won’t be an array, set thearray size to 0.

Control Type The control type determines the function of the data type andhow it will display data. The control type is the main characteristic of a datatype. A list of control types can be found in Control types on page 48.

Keyable Length The keyable length is the number of characters a user canenter in a field. Control types such as currency, integer and string have akeyable length.

Static Values Static values are any text and pictures that can be associatedwith a data type. Static values are described in detail in Static values on page 62.

4. Drag the field to the layout area.Select the appropriate local field name from the Toolbox and drag it into thelayout area. The side of the new field is the default size based on the field’scontrol type and current display properties.

5. Set properties for the field.Use the Properties window to set properties for the new field. The properties forfields are described in Field properties on page 27.

Enter the name of thelocal field here.

A new local field hasits own local data

type to specify thefield characteristics.


C H A P T E R 7 A D D I N G N E W F I E L D S

Using the Toolbox

You can also use the tools in the Toolbox to add new local fields to a window. To dothis, select one of the tools and then click in the layout window. A new local fieldwith the specified control type will be created for the current form and placed onthe window. The name of the new control will be based on the tool used to create it.

To further specify characteristics of the new local field, set the drop-down list in theToolbox to display local fields. Locate the new field in the list and then click Open.The Local Field Definition window for the new field will be displayed, allowingyou to edit its characteristics.

Adding prompts

Once you’ve created a new field and added it to a window, you may want to createa prompt for the field. For the best appearance, the prompt should havecharacteristics similar to other prompts in Microsoft Dynamics GP. Use thefollowing procedure to create a prompt.

1. Create the prompt.Select the Text tool in the Toolbox, then click in the layout area. Type the text forthe prompt.

2. Set the prompt properties.Select the prompt with the Arrow tool. Set the following properties in theProperties window’s Visual tab:

These settings allows the prompt color to automatically be updated based onthe color scheme the user selects in the User Display Preferences window.

3. Resize the prompt box.With the Border property set to true, a border will appear for the prompt. Selectthe prompt using the arrow tool. Using the handles, adjust the prompt until it’sthe desired size.

4. Link the field to the prompt (optional).You may want to link the field to the new prompt. This is especially useful ifyou set the field’s Required property to true. Then the prompt will visuallyindicate the field is required. Linking prompts is described in Linking fields toprompts on page 33.

Appearance 3D Highlight

BackColor System - Button Face

Border True

Font System

FontColor System - Button Text

Pattern (none)

PatternColor Black



Control types

A new local field is assigned one of several predefined control types. This sectiondescribes the recommended control types you can use for new fields. We don’trecommend creating new fields with control types not in this list. An example orillustration, keyable length, types of static values used, and a description of thecontrol type’s function are provided for each control type. The following controltypes are described:

• Boolean• Button drop list• Check Box• Combo Box• Currency• Date• Drop-down list• Integer• List box• Long integer• Multi-select list box• Non-native list box• Progress indicator• Push button• Radio button• Radio group• String• Text• Time• Visual switch



Boolean

Example None

Keyable length Not applicable

Static values None

Function Stores a boolean (true or false) value. The default value is false.

Button drop list

Example


Static values Pictures, text, or both pictures and text for the button. Text for items in the list.

Function Allows one item to be selected in the list. The value in the field is an integer thatcorresponds to the position of the last item selected in the list. The items in the listare numbered starting with 1. This control is used as a means of navigation.

Check Box

Example


Static values Text, pictures or native pictures for the prompt

Function Stores and displays a boolean (true or false) value. The value in the field is true ifmarked and false if unmarked.



Combo Box

Example

Keyable length Up to 255

Static values Text for items in the list

Function Allows a text item to be entered by a user or chosen from the list. The value in thefield is a string.

Currency

Example


Static values None

Function Displays a value as a currency amount, with a currency symbol and thousandsseparator if specified in the data type’s format.

The currency value can be in the range [-99,999,999,999,999.99999 to99,999,999,999,999.99999]. The decimal point is implied in the number, but notactually stored. For display purposes, currency values are limited to 14 digits to theleft of the decimal and 5 digits to the right.

Date

Example


Static values None

Function Stores and displays a date. The date is entered in MMDDYYYY form and isdisplayed according to the system settings, in short form. The year values can rangefrom 1800 to 9999.

The runtime engine automatically checks each date value to ascertain whether itsvalues are within the acceptable ranges of a date value. If the date is not valid, amessage is displayed.

An uninitialized date field (one that hasn’t been set to a value) will have the value00000000. This is an acceptable date value.



Drop-down list

Example



Function The value of the field is an integer corresponding to the position of the selected itemas it appears in the Static Text Values window. The items in this list are numberedsequentially so that the first item in the list is 1, the second is 2, and so on. If thestatic text items are sorted for display, the value of the field still is based upon theselected item’s position in the Static Text Values window, not its position asdisplayed in the list at runtime. Up to 32,767 items can be displayed in the list.

Integer

Example


Static values None

Function Displays and stores integers from -32,768 to 32,767.

List box

Example



Function Allows only one item to be selected in the list box.

The value of the field is an integer corresponding to the position of the selected itemas it appears in the Static Text Values window. Items are numbered sequentially sothat the first item in the list is 1, the second is 2, and so on. If the static text items aresorted for display, the value of the field still is based upon the selected item’sposition in the Static Text Values window, not its position as displayed in the list boxat runtime. Up to 32,767 items can be displayed in the list.

The list box control is created using the current operating environment’s native listbox control. It is preferable to use the list box control, rather than the non-native listbox control.



Long integer

Example


Static values None

Function Displays and stores integers from -2,147,483,648 to 2,147,483,647.

Multi-select list box

Example



Function Allows multiple items to be selected in the list box. Up to 32 items can be displayedin the list. The CTRL key is used to select non-consecutive items.

Non-native list box

Example



Function Allows only one item to be selected in the list box.

The value of the field is an integer corresponding to the position of the selected itemas it appears in the Static Text Values window. Items are numbered sequentially sothat the first item in the list is 1, the second is 2, and so on. If the static text items aresorted for display, the value of the field still is based upon the selected item’sposition in the Static Text Values window, not its position as displayed in the list atruntime. Up to 32,767 items can be displayed in the list.

A non-native list box control is created completely by the runtime engine.



Progress indicator

Example


Static values None

Function Allows progress to be shown visually. The indicator position is based on the valueof the progress indicator field. The valid values range from 0 to 100. When set to 0 orless, no indicator is displayed. When set to 100 or greater, the entire indicator isdisplayed. For values in between, the amount displayed is proportional to thevalue.

Several properties control the display characteristics of the progress indicator, suchas style and indicator color. If the indicator is composed of blocks, the block size isset automatically based upon the height of the progress indicator.

Push button

Example


Static values Text, pictures or native pictures

Function Provides a means of starting processing. The action associated with the field is runwhen the button is clicked.

Radio button

Example


Static values Text for each radio button prompt

Function Radio button values are stored using a radio group. The value of the radio group isan integer that corresponds to the radio button currently selected. A specific radiobutton’s value is determined by its position in the tab sequence; the first radiobutton’s value is 0, the second is 1, and so on. The radio group must comeimmediately before the radio buttons in the tab sequence.



Radio group

Example


Static values None

Function Groups and stores a single value for the radio buttons inside the radio group.

The value stored is an integer corresponding to the position of the selected radiobutton in the tab sequence; if the first radio button is selected, the value 0 is stored;if the second one is selected, the value 1 is stored, and so on. The radio group mustimmediately precede the radio buttons in the tab sequence.

String

Example


Static values None

Function Allows entry and display of strings of up to 255 characters.

Text

Example

Keyable length Up to 32,000

Static values None

Function Displays text and allows a user to enter text into the application. The text will wraponly if the WordWrap property for the field using the data type is set to true. Scrollbars can be turned off by setting the ScrollBars property for the field using the datatype to false.

Up to 32,000 characters can be stored in the field.

Radio group



Time

Example


Static values None

Function Time is entered in 24-hour format, such as 181732, and is displayed in 12-hourformat, such as 6:17:32 PM. The runtime engine automatically checks each timevalue to ascertain whether it’s within the proper range of a time value.

An uninitialized time field (one that hasn’t been set to a value) will have the value000000. This is an acceptable time value.

Visual switch

Example


Static values Text, picture or native picture

Function Displays a series of items. The next item in the field is displayed when the field isclicked. The value of the field is an integer corresponding to the position of thecurrently-displayed item in the series, starting with 1 and incremented by 1.



Working with controls

This section contains specific information about how to work with the mostcommon controls you can create in the Modifier, such as push buttons, button droplists and check boxes.

Push buttonsPush buttons provide a method of starting processing in an application. A pushbutton can display a text item, a graphic item, or both text and graphics. Eitherpictures or native pictures can be used.

Use the Style property for the push button field to specify which types of items aredisplayed on the button. The Style property also controls the arrangement of theitems. The following table shows the arrangements possible for text and graphics ona push button.

A push button can have up to three images: an Up image, a Down image and anOver image. The Up image is displayed when the button isn’t being clicked. TheDown image is displayed when the button is being clicked. The Over image isdisplayed when the pointer is positioned over the button.

If you supply only the Up image for a push button, the Down image will be drawnautomatically when the push button is clicked.

Style Example

Text Only

Graphic Only

Text on Top

Text on Bottom

Text on Right

Text on Left



Check boxesYou can use picture static values with check boxes. In addition, you can use theStyle property to specify whether the check box will appear as a standard check boxor as a push button. The following illustrations show how check boxes look with thevarious styles.

If you change the Style property for a check box that uses static picture values, use the Sizeto Default tool in the toolbox to resize the check box field to the appropriate size.

If you use pictures (picture resources) as the static values for a push button-stylecheck box, you can specify two, four or six images. These images are used for thevarious check box states.

• If you specify two images, these images will be used for the up and down states,respectively.

• If you specify four images, these will be used for the up, up clicked, down, anddown clicked states, respectively.

• If you specify six images, the Appearance property for the check box must beset to 3D Highlight. The images will be used for the up, up clicked, down, downclicked, up highlight and down highlight states, respectively.

Button drop listsButton drop lists are typically used to provide a method of navigation in anapplication. When you define a button drop list data type, you can specify what willappear on the button and the static text items that will appear in the list.

The button portion of a button drop list can display a text item, a graphic item, orboth text and graphics. You must use pictures for graphics that appear on the buttondrop list. In versions of Microsoft Dynamics GP prior to 6.0, native pictures wereused.

A button drop list can have up to three images: an Up image, a Down image and anOver image. The Up image is displayed when the button isn’t being clicked. TheDown image is displayed when the button is being clicked. The Over image isdisplayed when the pointer is positioned over the button drop list.

Use the Style property for the button drop list field to specify which types of itemsare displayed on the button. The Style property also controls the arrangement of theitems.

If you select 3D Highlight for the Appearance property, the text caption in the buttonportion of the button drop list will become bold when the field has the focus. Be sure toprovide extra space for the caption to accommodate the bold text.

Normal style Push button style

Marked

Not marked



Typically, button drop lists have a drop indicator (a small triangle) in the lower-right corner of the field. It’s not necessary to include the drop indicator in the imagefor the button drop list. Instead, set the DropIndicator property to True. Use theDropPosX and DropPosY properties to specify the distance the drop indicator willappear from the lower-right corner of the button drop list.

This is the drop indicator.

PA

RT

3: G

LOB

AL M

OD

IFICA

TIO

NS


Part 3: Global ModificationsThe Modifier also allows you to make changes that will affect the entire applicationinterface. This part provides detailed information about the various globalresources you can modify in Microsoft Dynamics GP. The following items arediscussed:

• Chapter 8, “Data Types,” describes data types and how they controlcharacteristics of fields.

• Chapter 9, “Formats,” describes how formats are used to control how data isdisplayed.

• Chapter 10, “Global Fields,” explains how to examine global fields in theaccounting system.

• Chapter 11, “Pictures and Native Pictures,” describes how to use the Modifier tocreate and modify picture resources.

• Chapter 12, “Strings,” explains how to modify string resources in MicrosoftDynamics GP.

• Chapter 13, “Messages,” explains how to modify message resources inMicrosoft Dynamics GP.


Chapter 8: Data TypesData type resources specify the characteristics of all fields used in an application. Ifyou want to change the characteristics of a field, you need to change itscorresponding data type. Keep in mind that a single data type can be used bymultiple fields. When you change the data type, you change the characteristics of allthe fields that use it. Information is divided into the following sections:

• Opening a data type• Keyable length• Static values• Format

Opening a data type

To open a list of data types, click the Data Types button on the toolbar or chooseData Types from the Resources menu. In the Data Types window, select a data typeand click Open. The Data Type Definition window will appear, as shown in thefollowing illustration.

The data type’s name appears at the top of the window. The Control Type fieldspecifies the function of the data type, indicating how it will display and store data.The other fields in the window specify the additional characteristics of the datatype. The following sections describe the data type characteristics you can changewith the Modifier.

Keyable length

The keyable length is the number of characters a user can enter in a field that usesthis data type. Control types such as currency, integer and string have a keyablelength. You can use the Modifier to change the keyable length. For example, youmay want to increase the keyable length for the STR10_Phone data type to allow theuser to enter more digits. The following table lists control types for which you canset the keyable length.

The control type is themain characteristic of the

data type.

Control type Maximum keyable length

Combo box Storage Size - 1

Currency 19

Integer 5

Long integer 10

String Storage Size - 1

Text 32,000

P A R T 3 G L O B A L M O D I F I C A T I O N S


Static values

Certain control types allow you to specify static values for the data type. Staticvalues are any text or pictures associated with a data type that are displayed by afield using that data type. For example, the text on a push button and the items in alist box are static values. To view the static values for a data type, click the StaticValues lookup button.

Static text valuesThe following table lists the control types that use static text values.

The Button Items window is used to specify the static text for button drop lists andpush buttons.

To edit a static text value, select the appropriate Up, Down or Over caption. Enterthe new text and then click OK in the Button Items window to save the changes.

Push buttons can be clicked using access keys (pressing ALT in combination with aletter). When the push button is displayed, an underscore beneath one of the lettersin the static text for the push button indicates the button has an access key. To definean access key, place an ampersand (&) in the static text value for the button beforethe letter that will act as the access key.

Click this lookup button toview the static items for

the data type.

Control type Static text used to:

Button Drop List Indicate the text on the button and the selections in the list.

Check box Indicate the check box prompt name.

Drop-down list Indicate the selections in the drop-down list.

List box Indicate the selections in the list box.

Push button Indicate the text displayed on the button.

Radio button Indicate the name displayed next to the button.

Visual switch Display two or more text values that will be displayed in sequence as the user clicks the visual switch.


C H A P T E R 8 D A T A T Y P E S

The Static Text Values window is used to specify the static text for check boxes,drop-down lists, list boxes, radio buttons and visual switches.

To edit a static text value, select it in the Static Text Values list. Make the appropriatechanges in the New Value field, then click Replace. You can mark or unmark theSort List option, depending on whether you want the static items sorted.

Static picture valuesSome control types use graphics as static values. Two kinds of resources are used asstatic picture values:

Modifying pictures and native pictures is described in Chapter 11, “Pictures and Native Pictures.”

• Native picture resources are specific, or native, to a particular operating system.

• Picture resources are pictures you’ve added to the picture library. They arestored in a generic format that can be used on any supported operating system.

The following table lists the control types that can use static picture values:

Format

A format contains extra characters, spacing and attributes that can be applied to adata type when data is entered or displayed. Formats are described in the nextchapter.

Control type Static picture usage

Push button Pictures and native pictures can be used for images on the button.

Check box Pictures and native pictures for the control.

Button drop list Pictures and native pictures can be used to indicate the images for the button part of a button drop list.

List view Pictures can be used for items appearing in the list.

Tree view Pictures can be used with nodes appearing in the tree.

Visual switch Can display two or more pictures or native pictures to set up a sequence of images that will change as the user clicks the visual switch.


Chapter 9: FormatsFormats are the extra characters, spacing and attributes that can be applied to a datatype to format data when it is entered or displayed. For example, a string data typefor a phone number can have a format applied to it so a field using the data typewill display a phone number as (555) 123-4567 instead of 5551234567.

Formats are stored as separate resources, but are applied to data types to helpdefine how information is displayed. A single format resource can be used byseveral data types. Perhaps the easiest way to understand what formats are is toview them as data “masks” that simply change the look of the information in a fieldwithout changing the actual information itself. Information about formats isdivided into the following sections:

• Opening a format• Formatting options• Format string

Opening a formatTo open a list of formats, choose Formats from the Resources menu. The Formatswindow will appear. To create a new format, click New. To open an existing format,select one in the list and click Open. The Format Definition window will appear, asshown in the following illustration.

Each format has a name. Typically, the name indicates the data type the format isapplied to. For instance, the name STR_Employer_ID_Number indicates a formatthat will be applied to a data type used for an employee ID number.

Formatting optionsYou can use several formatting options to change how specific types of data willappear. You can use them to specify the following characteristics:

• Align information to the left, right or center of a field.• Determine what characters will appear in unused parts of a field.• Specify how you want currency fields to appear.• Specify how numeric fields display information.

The format name isentered here.

Options for the format arechosen here.

Format strings areentered here.



The following tables describe the various formatting options:

Format string

The Format Definition window allows you to specify a format string for string andcomposite data types.

String formatsFormat strings are used with string data types to add static elements to a field, suchas parentheses or static text. The Modifier uses the capital X as a place holder torepresent alphanumeric characters that will appear in the field. All other characterswill be displayed as you type them.

Numeric formats

Decimal Digits Number of decimal places (0 to 5).

Negative Symbol The operating system setting, a minus sign, the letters CR, or parentheses.

Alignment Number is left-, center- or right-aligned.

Fill Unused spaces are filled with asterisks, zeros or spaces.

Unsigned If marked, the negative symbol won’t be displayed.

Show Thousands Separator

If marked, the field will show thousands separators in the number.

Show Percent Sign If marked, the field will show the percent sign.

Currency formats

Decimal Digits Number of decimal places (0 to 5).

Negative Symbol The operating system setting, a minus sign, the letters CR, or parentheses.

Alignment Number is left-, center- or right-aligned.

Fill Unused spaces are filled with asterisks, zeros or spaces.

Unsigned If marked, the negative symbol won’t be displayed.

Show Thousands Separator

If marked, the field will show thousands separators in the number.

Relative Decimal Position

If marked, the number of decimal digits selected is added to the number in the operating system setting. The total can be up to 5 decimal digits.

Show Currency Symbol If marked, the currency symbol specified in the operating system settings is displayed.

String and composite formats

Alignment String is left-, center- or right-aligned.

Fill Unused characters are filled with asterisks, zeros or spaces.

Trailing Blanks If marked, any spaces that follow the contents of the field will be saved in the table. If the option isn’t marked, any spaces following the item in the field won’t be saved. Leave unmarked to ensure that the same entry made with or without trailing blanks will be stored with the same value.

Leading Blanks If marked, spaces can be entered as the first characters in the field. These spaces will be saved in a table.

Numeric Only If marked, only numbers can be entered in the field.

Alphanumeric Only If marked, only letters and numbers can be entered in the field.

Uppercase Only If marked, all alphabetic characters will be displayed in uppercase.


C H A P T E R 9 F O R M A T S

Example 1For instance, suppose you’re using a specific data type to store information enteredin phone number fields. This Phone_Number data type uses a format and a formatstring to determine how phone numbers will appear at runtime:

The Xs are placeholders indicating where the digits will be displayed, while theparentheses and dash are displayed just as you typed them. When the field isdisplayed and the phone number is entered, the format string will automaticallydisplay the special characters in the field.

Also note that a lowercase x is used in the “ext.” abbreviation in the second formatstring. Only uppercase Xs are treated as place holders, so the lowercase x isdisplayed in the field, instead of being replaced when data is entered.

Static characters in a format string aren’t actually stored with the data in the table. Thisallows you to change the format string without affecting how data is stored.

Composite formatsA format string is used with a composite data type to indicate the size and order ofthe components of the composite, and to add static elements, such as parentheses orstatic text. The numeric characters 1 through 9 are used to represent the charactersof each component of the composite. All other characters will be displayed just asyou type them.

Not all composites use a format string. Some composite fields, such as the MicrosoftDynamics GP Account Number, have their format defined through program code.

Example 2The following example shows the use of a format for a standard composite. Acomposite must have a format and a format string. This composite contains threeparts, as indicated by the format string.

Note that the 1s, 2s and 3s are used as placeholders.

Format string Data entered Data displayed

(XXX) XXX-XXXX 7015550100 (701) 555-0100

ext. XXXX 6590 ext. 6590

Format string Data entered Data displayed

1111-22-3333 1000ND5050 1000-ND-5050


Chapter 10: Global FieldsFields represent the individual pieces of information in an application. They canappear in windows and be stored in tables. Each field uses a data type to specify itscharacteristics. Two types of fields are used in applications: global fields and localfields.

• Global fields can be used in window and can also be stored in tables.

• Local fields can be used only in windows. They are described in Chapter 7,“Adding New Fields.”

Information about global fields is divided into the following sections:

• Opening a global field• Opening a field’s data type

Opening a global field

To open a list of global fields, click the Fields button on the toolbar or choose Fieldsfrom the Resources menu. In the Fields window, select a global field and click Open.The Field Definition window will appear, as shown in the following illustration.

You can also open the Global Field Definition window from the Layout window.Select Global Fields as the type of field to display in the Toolbox. Select a field namein the list and click Open.

Opening a field’s data type

When the Field Definition window is open, you can easily drill down to the datatype definition used for that field. To open the Data Type Definition window, clickOpen.

Click Open to open thedata type definition for

the global field.


Chapter 11: Pictures and Native PicturesTwo types of pictures are used in Dexterity-based applications: pictures and nativepictures. Pictures are stored in a generic format and can be displayed on anyplatform. They are typically used to display large graphics and logos in anapplication. Native pictures are pictures that are used only on a particular platform.They are used to display pictures on push buttons and visual switches.

Information about pictures and native pictures is divided into the followingsections:

• Pictures• Adding a picture to the picture library• Using a picture from the picture library• Creating native pictures• Synchronizing native pictures• Using native pictures

Pictures

Pictures are stored in a generic format and can be displayed on any platform.Currently, the Modifier can convert Windows metafiles to a form that can be storedin the picture library. Pictures up to 32K in size can be stored. Pictures are stored onlyonce, but can be placed in several windows of an application using the picture toolfrom the Toolbox in the Layout windows.

A company or product logo can be pasted into the picture library and used inMicrosoft Dynamics GP windows. The following picture is the logo that is used forbusiness alerts.

Adding a picture to the picture library

Choose Pictures from the Resources menu; the Pictures window will appear.

1. Create a new picture or edit an existing one.Click new to create a new picture or select a picture and click Open to edit it.The Picture Definition window will appear, as shown in the followingillustration.

Enter the name of thepicture here.

To add a picture, click inthis area to select it andthen choose Paste from

the Edit menu.



2. Name the picture.In the Picture Definition window, name the picture.

3. Add the picture.Be sure the picture you want to add is in the Clipboard. Click in the area belowthe Picture Name field to select it, and the choose Paste from the Edit menu topaste the picture into that area.

4. Click OK to add the picture to the library.

Using a picture from the picture library

Open the layout of the window where you want to paste a picture.

1. Select the picture tool.

2. Click in the layout area where you want the picture to appear.After you click in the layout area, the Pictures window will appear, allowingyou to select a picture to paste into the layout.

3. Select the picture to paste.From the Pictures window, select the name of the picture to paste into thewindow and click OK.

4. Position and resize the picture if necessary.

You can paste a picture directly into the window layout, bypassing the step of adding thepicture to the picture library. Simply copy the picture to the Clipboard and choose Paste fromthe Edit menu to paste it into a window layout. You’ll be asked to name the picture. Thepicture will appear in the layout and will be added to the picture library automatically.

Creating native picturesChoose Native Pictures from the Resources menu. The Native Pictures window willappear.

1. Create a new native picture or edit an existing one.Click New to create a new native picture or select a native picture and clickOpen to edit it. The Native Picture Definition window will appear, as shown inthe following illustration.

This is the name of thenative picture on the

current platform.This is the native picture

the current picture issynchronized with.

This is the native picturefor the current platform.

Click Copy to copy theexisting native picture.

Click Paste to paste a newnative picture.


C H A P T E R 1 1 P I C T U R E S A N D N A T I V E P I C T U R E S

2. Name the native picture.In the Native Picture Name field, enter the name of the native picture for thisplatform.

3. Add the native picture.Be sure the picture you want to add is in the Clipboard. Click Paste to paste thepicture into the Native Picture Definition window.

4. Click OK to save the native picture.

Synchronizing native pictures

If you will be using native pictures on more than one platform, you must createcorresponding native pictures on both platforms. These pictures must besynchronized (given the same internal ID) so the correct picture will be displayedon each platform.

1. Create the native picture on the first platform.When you create the first native picture, be sure the Synchronize With option inthe Native Picture Definition window is unmarked.

2. Access the Modifier on the next platform.

3. Create the corresponding native picture for the new platform.Before you save the native picture, mark the Synchronize With option. A list ofpictures from the first platform will be displayed.

4. Select the name of the appropriate picture from the first platform and click OK. The pictures will automatically be given the same internal ID.

Using native pictures

Follow these guidelines when using native pictures in the Modifier.

Push buttonsWhen you use them for push buttons, two native pictures are required. The “buttonup” picture is displayed when the button is not being clicked. The “button down”picture is displayed when the button is being clicked. Often, the button up andbutton down pictures are drawn to produce a three-dimensional effect (offsettingthe button down picture one pixel down and to the right) when the button ispushed. To have the best appearance, the native pictures used should be the samephysical size.

The following illustration shows the native pictures used for a lookup button. Thebutton up and button down pictures were synchronized so the correct picture isdisplayed for each platform. Native pictures can be created so they appear assimilar as possible, or different for each platform.

Button Up Button Down



Visual switchesVisual switches can be used to display a series of native pictures. For each imagedisplayed, only one native picture is required. To have the best appearance, allnative pictures used for the visual switch should be the same physical size.


Chapter 12: StringsA string is a sequence of up to 79 characters that doesn’t contain carriage returns.Strings are used throughout the accounting system for window names, fieldprompts and static text values. Information about strings is divided into thefollowing sections:

• Using strings• Modifying a string

Using strings

The strings resource allows you to update all occurrences of a string in one stepinstead of changing the same string in each place it occurs.

For example, to change all occurrences of the words “Customer Name” to “ClientName,” you could select the Customer Name string and change it to Client Nameinstead of changing each individual prompt, text value or window name.

Note that changing a string with the Modifier will change it only in the interface. The stringwon’t be changed in any reports. To change strings in reports, you must use the ReportWriter.

Modifying a string

Choose Strings from the Resources menu. The Strings window will open, allowingyou to select the string to edit.

The Microsoft Dynamics GP dictionary contains several thousand strings. The Stringswindow may take a few moments to open.

1. Select the appropriate dictionary core.String resources are divided into several cores, which are special divisions inthe dictionary. Microsoft Dynamics GP has a core for each major modulecategory. When locating a string, begin by choosing the core that the string ismost likely contained in. For example, the string “Customer” is likely part ofthe Sales core, so begin looking there. If you don’t find a string in a particularcore, look in the other available cores.

2. Select the string to edit.After you have located the string, select it in the list and click Open. The StringDefinition window will appear, as shown in the following illustration.

3. Edit the string.Edit the string in the String Definition window and click OK to save themodified string.

Edit the string and thenclick OK to save the

changes.


Chapter 13: MessagesMessages are a type of resource that associates a text string with an ID. In MicrosoftDynamics GP, messages are used to store the text that provides information orprompts a user to make a selection. Messages are also used to store other stringsused in the accounting system, such as the names of reports. Information aboutmessages is divided into the following sections:

• Finding messages• Replacement markers• Modifying messages

Finding messages

To find messages in Microsoft Dynamics GP, you will need to generate a resourcereport. This report lists all of the resources in the current dictionary, includingmessage resources. To generate a resource report, choose Generate ResourceReports from the File menu. Specify a file name and location and then save thereport.

Microsoft Dynamics GP contains several thousand resources. Generating the resourcereport may take a few minutes.

After the resource report has been generated, you can use a text editor to search forspecific messages. Once you have found the message, you can see its message ID.

Replacement markers

Some messages contain replacement markers. A replacement marker is a percentsymbol (%) followed by a number. Replacement markers indicate positions in themessage text where additional information will be substituted when the message isdisplayed. If you edit a message, be sure to leave the replacement markers in place.Otherwise, the message won’t be displayed properly.

Use a text editor to searchfor a message. When you

have located it, you cansee its message ID.



Modifying messages

Choose Messages from the Resources menu. The Messages window will open,allowing you to edit messages.

1. Enter the message ID.Enter the ID of the message you want to edit. The message will be displayed.

2. Edit the message text.Make the changes to the message string and click Save.

Enter a Message ID andthen edit the message.

PA

RT

4: S

TO

RIN

G A

ND

AC

CE

SS

ING

MO

DIFIC

AT

ION

S


Part 4: Storing and Accessing ModificationsThis portion of the documentation contains information about how modificationsyou make are stored and accessed. The following items are discussed:

• Chapter 14, “Storing Modifications,” explains how modifications are stored anddescribes two common Modifier configurations.

• Chapter 15, “Accessing Modifications,” describes how to control access to theModifier and to forms that you have modified.

• Chapter 16, “Packaging Modifications,” explains how you can package anddistribute modifications to other users.


Chapter 14: Storing ModificationsAll modifications you make with the Modifier are stored in the Forms dictionary.Information about storing modifications is divided into the following sections:

• Forms dictionary• Launch file• Modifier configurations

Forms dictionary

All changes and additions you make using the Modifier are stored in the formsdictionary for the application. By storing the new and modified resources in aseparate dictionary, the integrity of the main dictionary can be maintained. Forexample, the following illustration shows the dictionary for Microsoft Dynamics GPand its associated forms dictionary.

When you access the Modifier for the first time, all of the core resources for theapplication dictionary are copied to the forms dictionary. Core resources includestrings, data types and global fields that are used by several parts of the system.Once core resources have been copied to the Forms dictionary, the runtime enginewill look there first when it retrieves resources from the dictionary. Any additions ormodifications you make to core resources will be stored in the forms dictionary. Themodifications will be accessed automatically when you use Microsoft Dynamics GP.

When you select a form to modify, that form is copied into the forms dictionary.Any modifications or additions you make to that form will be stored only in theforms dictionary. To access the modifications you make to forms, you must setsecurity in the accounting system to access the modified form. This is described inChapter 15, “Accessing Modifications.”

Launch file

When you start Microsoft Dynamics GP, you use the launch file that tells the runtimeengine which dictionaries will be used by the application. The launch file stores thelocation of the application dictionary as well as the names and locations of anyforms or reports dictionaries.

By default, the forms dictionary is named Forms.dic and is located in the Datafolder for the Microsoft Dynamics GP installation. You can use the Edit Launch Filewindow to change the name or location of the forms dictionary.

To update the launch file, you must have appropriate user privileges. Typically, this meansbeing part of the Administrators group or the Power Users group. If User Account Control(UAC) is active, it means launching Microsoft Dynamics GP with Administrativeprivileges.

Forms.dicDynamics.dic

New and modified resources are stored in the forms dictionary.

P A R T 4 S T O R I N G A N D A C C E S S I N G M O D I F I C A T I O N S


To display this window, choose Microsoft Dynamics GP >> Tools >> Setup >>System >> Edit Launch File.

To change the name or location of a forms dictionary, select a product such asMicrosoft Dynamics GP. Then edit the name or location of the forms dictionary inthe field at the bottom of the Edit Launch File window.

Be sure that you have correctly specified the name and location of the forms dictionary.Otherwise, the accounting system may not start properly.

Modifier configurations

Two common configurations are used with the Modifier. One configuration has theforms dictionary stored locally on each workstation. In the other configuration, theforms dictionary is stored in a network location accessible by all workstations.

Storing the forms dictionary locallyIn this configuration, each workstation has its own forms dictionary. Typically theforms dictionary is stored in the Data folder for the Microsoft Dynamics GPinstallation. This configuration is also used for single-user installations. Thisconfiguration has the following advantages:

• Each workstation can have its own unique set of modifications.

• Users can access the Modifier at any time.

It has the following disadvantage:

• Modifications can’t easily be shared by multiple users. This issue can bepartially resolved by making modifications on one workstation and thendistributing the modifications to other workstations.

Select a product for whichyou want to modify

dictionary locations.

You can change the nameor location of the forms

dictionary here.


C H A P T E R 1 4 S T O R I N G M O D I F I C A T I O N S

Storing the forms dictionary on a networkIn this configuration, one forms dictionary is stored in a network location that canbe accessed by each workstation. This configuration has the following advantages:

• The same modifications are available to all users.

• Any modifications users make are available to other users.

It has the following disadvantages:

• Only one user can access the Modifier at one time.

• All workstations are dependent on a single forms dictionary. If this dictionary isnot available or becomes damaged, all users are affected.

• Users can’t have different sets of modifications.

The configuration you choose depends upon how many modifications you want tomake, whether individual users will be making modifications, and how you want toshare modifications among users.


Chapter 15: Accessing ModificationsYou can control which users have access to the Modifier and which modificationsspecific users will see. Information about controlling access is divided into thefollowing sections:

• Accessing the Modifier• Accessing modified forms• Accessing third-party modifications• Removing modified forms

Accessing the Modifier

The predefined security task ADMIN_SYSTEM_009 for Microsoft Dynamics GP isused to control which users will be able to access the Modifier. Assign this securitytask to an existing role to grant access to the Modifier for users assigned to that role.You might also consider creating a new security role for the Modifier. Any userassigned to this new role will be able to access the Modifier.

Accessing modified formsIf you want to view a modified report from within the application, you must use theAlternate/Modified Forms and Reports window in Microsoft Dynamics GP to grantaccess. To open this window, choose Microsoft Dynamics GP menu >> Tools >>Setup >> System >> Alternate/Modified Forms and Reports.

Consider creating a newsecurity role that has

access to the Modifiertask.



Complete the following procedure to specify that a modified form should be used.

1. Specify the ID.Select the ID for the set of forms and reports you are modifying. The users thatyou want to view the modified version of the form must be assigned to use theset of modified/alternate forms and reports you selected. The User SecuritySetup window is used to specify the set of modified/alternate forms andreports for each user.

2. Select the product containing the modified form.This is the product in which the form was originally defined.

3. Choose to display windows.Choose Windows as the type of resource to display. The tree view will be filledwith the modified forms available.

4. Set the series.By default, the Series drop-down list is set to All. You can choose to displayresources from a specific series.

5. Locate the modified form.Expand the nodes in the tree view to locate the form that you modified. Theforms are organized by series.

6. Choose to use the modified form.The original and modified versions of the form will be listed. Mark themodified version.

If you later wanted to use the original version of the form, you would mark the originalform instead.

7. Save the changes.Click Save to save the changes.

To view modified forms, you must have either the Modifier or the Customization SiteEnabler registered.

Mark the item to usethe modified version

of the form.


C H A P T E R 1 5 A C C E S S I N G M O D I F I C A T I O N S

Be sure to activate security once you've made your selections by marking theSecurity option in the Company Setup window in Microsoft Dynamics GP. Whenyou open the form to which you made modifications, the modified form will beopened in its place. You can verify that the modified form is being used by closelyexamining the title bar of the window. If the text in the title bar starts with a period,the modified window is being displayed.

Changes you made to core resources like strings and data types will be seen by all users. Noadditional configuration is required.

Accessing third-party modifications

You can use the Modifier to make changes to forms that are part of third-partyproducts created with Dexterity. Dexterity is the tool used to create MicrosoftDynamics GP. If you have third-party products that integrate with MicrosoftDynamics GP, you will be asked which product you want to modify when you startthe Modifier.

Modified formsAny modifications you make to a third-party product will be stored in a separateforms dictionary for that product. To access these modified forms, you must selectthe third-party product in the Alternate/Modified Forms and Reports window. Youcan then choose to use the modified version of the form.

The period in the windowtitle indicates a modified

version of the form isbeing displayed.

If you have products thatintegrate with Microsoft

Dynamics GP, use thiswindow to select the

product to modify.

This is a modified version ofthe Service Call Entry/Update

form in the Field Servicethird-party application.



Alternate formsSome third-party developers create alternate windows. These are Microsoft DynamicsGP forms that the third-party developer has enhanced and transferred to their owndictionary. By choosing the third-party dictionary when you start the Modifier, youcan make modifications to these alternate windows.

When using the Alternate/Modified Forms and Reports window to set access tothese reports, choose the modified version of the alternate report to display themodifications you made. For example, the following illustration shows how youwould display a modified version of the alternate Country Codes form provided bythe SmartList dictionary.

Removing modified forms

If you remove a modified form from Forms dictionary, be sure that you change thesecurity settings to use the original form rather than the modified form. Otherwise,Microsoft Dynamics GP will not be able to properly access the form.

This is the modifiedalternate version of the

Country Codes form.


Chapter 16: Packaging ModificationsWhen you have finished making modifications, you may want to distribute thosemodifications to other users. This portion of the documentation describes how youcan use package files to distribute modifications. Information is divided into thefollowing sections:

• Package files• Package file import/export issues

Package files

Package files are special text files that are used to deliver customizations made withthe Modifier, VBA, and the Report Writer. A developer can create a package file thatcontains their customizations, move the package file to the destination workstation,then import the customizations into the installation.

Package file contentsA 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 withthe 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 theVBA development environment.

References References to external components used by VBA. A package filecannot contain the actual components referenced by the VBA customization. Thosecomponents must be delivered separately.

Exporting a package filePackage files are created using the Customization Maintenance window. Completethe 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 choosingCustomization Maintenance.



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

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 thepackage file. Be sure the file has the .package extension. The results of theexport operation will be displayed in the status area at the bottom of thewindow.

Note that some global changes you make with the Modifier and Report Writer can’t beincluded in a package file. For instance, changes to picture resources or global data typeswon’t be included in package files.

Importing a package fileTo 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 choosingCustomization Maintenance.

2. Open the Import Package File window.Click Import in the Customization Maintenance window to display the ImportPackage File window.

3. Select the package to import.Click Browse to open a file dialog that allows you to select the package file youwant to import. The contents of the package will be displayed in the ImportPackage File window.

Select all of thecomponents that are part

of the customization.


C H A P T E R 1 6 P A C K A G I N G M O D I F I C A T I O N S

An “X” in the Overwrite column indicates that a customized version of acomponent already exists for the system, and will be overwritten by thecontents of the package file. Refer to Package file import/export issues on page 91for details about overwriting existing customizations.

If any of the package file items contain VBA code, the user importing them must haveappropriate user privileges to update the .vba files in the Microsoft Dynamics GPinstallation. Typically, this means being part of the Administrators group or the PowerUsers group. If User Account Control (UAC) is active, it means launching MicrosoftDynamics GP with Administrative privileges.

Click OK to start the import process. If any errors occur during the importprocess, the Errors window will be displayed. The results of the importoperation will also be displayed in the status bar of the CustomizationMaintenance window. To view the list of the last errors that occurred, click theErrors 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 accessto 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 andexporting package files, concerning how customized resources are stored byMicrosoft Dynamics GP.

Microsoft Dynamics GP contains forms, which are groups of windows, menus andother resources that work together for a common purpose. A form can have severalwindows, but you can make customizations to individual windows with theModifier and VBA. When you export a form to a package file, you are exporting allof the windows in that form, not just the windows you modified or applied VBAcode to.

This fact is important to keep in mind when you import a package file that containscustomized forms. If a customized version of the form already exists in the systemand you import another set of customizations for that same form, the originalcustomizations will be overwritten. This occurs even if the customizations are madefor different windows in the form.

A similar issue occurs for reports. If you’ve made customizations to a report, thenimport a package that contains customizations for that same report, the existingcustomizations will be overwritten.

A warning message is automatically displayed allowing you to cancel an import operationthat will overwrite existing customizations.


Glossary3D highlight

An Appearance property setting for pushbuttons that causes them to have a flatappearance until the mouse pointer ismoved over the button. Then the buttonappears with a 3-D border.

Accelerator keyA key or set of keys on the keyboard that canbe used as a “shortcut” to select a menu ormenu option rather than using the mouse.

Access keyAn underlined character in a menu name,menu item name or push button that allowsusers to select the item by typing theunderlined character or by holding down theALT key and typing the character.

AlphanumericA combination of numbers and letters.

Array fieldA field containing multiple occurrences ofthe same type of information. The individualpieces of information stored by an array fieldare called elements.

Array indexThe number designating a specific elementwithin an array field.

Auto-linked tableThe table specified in the AutoLinkTablewindow property. You can use the Modifierto add fields from the auto-linked table tothe window.

Big line itemThe area containing the fields that will bedisplayed for a scrolling window inexpanded mode. See also Small line item.

Button drop listA control type used to define data types thatallow a user to select one item from a list ofvalues. A series of static text values willappear, or “drop” when a user clicks a fieldthat uses this control type.

Cancel propertyA property that can be applied to a pushbutton window field. If this property is set totrue, pressing the ESC key produces the sameresult as clicking the push button.

Cascading menusSubmenus that appear to the right of a menuitem.

Change flagA boolean value associated with each formor window in an application. If the contentsof the form or window change, the changeflag is set to true, indicating the contentshave changed.

Check boxA control type used to define data types thatallow users to mark or unmark an option.

Check boxes have boolean storage types.

Combo boxA control type used to define data types thatallow users to enter a text value or choosethat value from a list.

The items in the list are determined by thestatic text values in the data type definition.

ComponentOne field of a composite field.

CompositeA group of fields and their associated datatypes that form a single data type.Composite data types are defined by thecomposite control type and the fields thatmake up the composite.

Control typeThe main characteristic of a data type,controlling the type of information that canbe stored in fields that use that data type,and some aspects of how the informationwill be displayed. Commonly-used controltypes are push button, integer, check box,date and currency.

Core resourcesResources such as strings, data types orglobal fields that are used by several parts ofan application. When the forms dictionary iscreated, the core resources in the applicationdictionary are copied to it.

Customization site enablerA Microsoft Dynamics GP module that canbe registered to allow access to modifiedforms without having to register theModifier.

Data typeA resource that defines the characteristics fora field, such as its keyable length, controltype (push button, check box, string and soon) and format. A single data type can beapplied to several fields, but a field can haveonly one data type applied to it.

Default propertyA property that can be applied to a pushbutton window field. If this property is set totrue, pressing the ENTER key or double-clicking a list box or scrolling window withthe DefaultDblClick property set to truecauses the push button to be clicked.

DefaultDblClick propertyA property for list box fields, non-native listbox fields, and scrolling windows. Double-clicking the list box or a line in a scrollingwindow with this property set to true causesthe push button whose Default property setto true to be clicked. See also Default property.

Definition windowA window that allows you to create or edit aresource and specify its functionalcharacteristics.

DictionaryA group of resources that, when interpretedby the runtime engine, present a completefunctioning application.

Drop-down listA control type used to define data types thatallow users to select one item from a list.

A series of static text values will appear, or“drop,” when a user clicks a field with thiscontrol type. The integer valuecorresponding to the position of the itemchosen, not the item’s static text value, isstored when the user’s selection is saved.

ElementOne of the fields in an array field.

FieldA field contains a single piece of informationused by an application. A field can bedisplayed on a window or stored in a table.The kind of information the field displays orstores depends on the data type associatedwith it. See also Global field and Local field.

FocusThe indicator that shows the object beingcontrolled in the current window.

FormA collection of windows, menus and otherresources that function together for acommon purpose.

FormatThe extra characters, spacing and attributesthat can be applied to a data type when datais entered or displayed.

Format fieldAn integer field that specifies the format touse for a string or currency field.

Format stringA data “mask” used for string andcomposite formats. The format string allowsextra characters to appear in a field withoutaffecting the way data in the field is stored.

Forms dictionaryThe dictionary that stores user-modifiedresources. This dictionary is created whenthe Modifier is accessed for the first time.Only copies of a dictionary’s resources arestored in the forms dictionary.

Global fieldA field that can be displayed in windowsand also stored in tables. The characteristicsof global fields can be viewed with the FieldDefinition window. See also Local field.

G L O S S A R Y


Group boxA box drawn around a group of check boxesor other fields, using the rectangle tool, tovisually group the items.

Keyable lengthThe number of characters that can be typedin a field.

Keyboard equivalentA key combination that will activate a menuitem as an alternative to selecting it with themouse.

Launch fileA file that is used to start an application withthe runtime engine. This file stores thelocation of the dictionaries that will be used,including the application dictionary and theforms dictionary.

Layout windowA window in the Modifier that allows you todesign the layout of a window or scrollingwindow.

List boxA control type used to define data types thatallow users to select one static text valuefrom a list.

The list will appear with scroll bars if theinformation in the list is greater than the sizeof the list box field when it’s added to theLayout window. An integer position - not thestatic text - for the corresponding selection ina list box is stored when the selection issaved.

List fieldAny field that uses a list box, drop-down list,multi-select list, button drop list, combo boxor visual switch data type.

Local fieldA field that’s available only within the formin which it’s created. Local fields are used aswindow fields. The Modifier can create localfields. See also Global field.

MenuOne of the items displayed on the menu baracross the top of the screen.

Menu itemOne of the selections associated with aparticular menu.

MessagesA type of resource that associates a textstring with an ID. Messages are used to storethe text that provides information orprompts a user to make a selection.Messages are also used to store other strings,such as the names of reports or the items thatappear in the toolbar buttons.

Modal dialogA window that contains no operating systemcontrols and can’t be resized. Modal dialogsare used when you require the user toperform an action before continuing.

Modified formThe copy you make of the original form.Modified forms are added to the Formsdictionary. You can select the modified formand customize the windows belonging to it.See also Original form.

Multi-select list boxA control type used to define fields fromwhich one or more static text values can beselected. The list will appear with scroll barsif the number of items in the list are greaterthan the size of the field when it was addedto the Layout window.

Native picturesPicture objects that are specific, or native, toa particular operating system. Metafiles andbitmap images are used as native pictures onWindows. Native pictures must be used forgraphics that appear on push buttons andvisual switches.

Original formAn unmodified form that is stored in itsoriginal dictionary. You must make a copy ofan original form before you can makemodifications to it. See also Modified form.

Package filesSpecial text files that are used to delivercustomizations made with the Modifier,VBA, and the Report Writer.

PasswordA field property that allows you to hideentries in a field, such as when a password isbeing entered. If this property is set to true,an X will be displayed in place of eachcharacter a user enters, so that no one elsecan read the entry from the screen.

Picture libraryA feature in the Modifier that allows you tostore graphics in a generic format that can beused on any supported platforms.

PixelThe smallest graphical element displayed ona monitor. The pixel is the smallest unit ofmeasurement in layout windows. You canmove objects one pixel at a time within alayout window by using the arrow keys onthe keyboard.

Point sizeThe vertical size of a font. There are 72 pointsto an inch.

Progress indicatorA control type used for fields that shows theprogress of processes in the application.

PromptText in a window that shows the user theinformation that is displayed or can beentered in the corresponding field or fields.

PropertyAn attribute that can be assigned to fields,windows or graphical objects displayed in awindow layout. For example, a window withthe Resizeable property set to false cannot beresized by the user.

Push buttonA control type used to define data types forbuttons users can click to accomplish tasks.

Static text or pictures can be used to indicatethe button’s function.

Radio buttonA control type used to define data types thatallow a single selection to be made from agroup of two or more selections.

Radio buttons must be used with a radiogroup.

Radio groupA control type that’s used to group relatedradio buttons and store the value of theselected button.

A radio group’s value is stored as an integercorresponding to the selected radio button’sposition in the tab sequence, beginning with0. For instance, if the second radio button inthe tab sequence is selected, the radiogroup’s value is 1.

Relative decimal positionAn option for currency formats that sets thenumber of decimal digits that will bedisplayed to the indicated value plus thenumber of decimal places specified by theoperating system. If your operating systemdisplays two decimal positions and youspecify three decimal digits for the format inthe Format Definition window, the field willdisplay a total of five decimal places.

Radio group


G L O S S A R Y

Replacement markerA placeholder (% followed by a number)that indicates where items may besubstituted in messages.

Resource descriptions toolA tool that displays information about thecurrent dictionary’s fields, windows andtables.

Resource list windowA window in the Modifier that allows you toview all the resources of a particular type,such as fields.

Runtime engineAn application that’s used to interpret adictionary. When a user starts an application,the runtime engine uses the resources in thedictionary to present a functioningapplication.

Scrolling windowA special type of window that allows theuser to “scroll” through items.

SeriesA predefined category to which form andtable resources are assigned. Series allowcategorization of resources.

Small line itemThe area containing the fields that will bedisplayed when a scrolling window is instandard mode. When a scrolling window isin expanded mode, additional fields belowthe small line item mark, but above the bigline item mark will be displayed. See also Bigline item.

Static picture valueA picture that’s displayed as part of a datatype, such as the picture on a button droplist.

Static text valueText that’s displayed as part of a data type,such as the name of a push button or theitems in a list box.

Storage sizeThe size, in bytes, used store the informationin a field. The storage size is specified in thefield’s data type. It can’t be changed by theModifier.

Storage typeOne of the standard forms used to store thedata in a field. The storage types are:boolean, integer, long, currency, currency(variable), string, text, date, and time. Thecontrol type determines which storage typeis used to store the data in the field.

String resourcesSequences of up to 79 characters usedthroughout a dictionary for window names,field prompts and static text values.

SynchronizeThe process of specifying the native pictureon each platform that should be used as thestatic value for a single data type. When twopictures are synchronized, the Modifier willassign them the same internal ID. Thereafter,when a synchronized picture is displayed,the native picture that’s appropriate to thecurrent platform will be displayed.

Tab sequenceThe order in which the focus moves fromone field to the next field when the userpresses the TAB key.

ToolboxA window that opens in conjunction withthe Window Layout and Scrolling WindowLayout windows. It contains tools used toplace and arrange items in the layout area.

Visual Basic for Applications (VBA)A development system created by Microsoftthat can be embedded into applications.VBA is embedded into the Modifier, where itprovides additional customizationcapabilities.

Visual Studio Tools for MicrosoftDynamics GP

A development toolset based on theMicrosoft .NET framework that can be usedto create integrations for MicrosoftDynamics GP. Microsoft Visual Studio is thedevelopment tool used to create theseintegrations.

WindowThe work area used to enter and displayinformation in a application.

Window fieldA global or local field that has been added toa window layout.

WordWrapA property for text fields that causes text toautomatically continue to the next line whenit extends beyond the right edge of the field.

Zoom pointerA special cursor that appears when thepointer is over a push button field that hasthe Zoom property set to true. In MicrosoftDynamics GP, clicking the mouse when thispointer is over the field enables users to“zoom” to the window where records for thefield can be added.


IndexNumerics3-D highlight, defined 93

AAbout, menu item 12accelerator key, defined 93access keys

defined 93described 44, 62

Accessing Modifications, chapter 85-88Add button, how used in Modifier 14Adding New Fields, chapter 45-58ADMIN_SYSTEM_009 task 85align to bottom tool, using in window

layout 23Align To Grid menu item 25align to left tool, using in window layout

23align to right tool, using in window layout

23align to top tool, using in window layout

23aligning

fields in windows 23objects to the grid 25

Alignmentdrawn object property 30field property 28

alphanumeric, defined 93alternate windows

described 88modifying 88

Alternate/Modified Forms and Reports window 86

AltLineColorfield property 28scrolling window property 41

Appearancedrawn object property 30field property 28scrolling window property 41

arrange tools, described 23arranging items, in window layout 23array fields

defined 93described 46

array indexes, defined 93arrow tool, using in window layout 22AutoComplete, field property 27auto-complete

adding items 36described 35removing items 35, 36saving items 36sharing auto-complete values 35

AutoCopy, field property 27auto-linked table

defined 93

auto-linked table (continued)described 32

AutoLinkTable, window property 26AutoOpen, window property 26

BBackColor

drawn object property 30field property 28scrolling window property 41window property 26

Basics, part 6-14big line item


big text tool 23boolean, control type 49Border

drawn object property 30field property 28

button drop listscaption and images 57control type 49defined 93drop indicator 58using 57

Button Items window 62

CCancel, field property 27, 93Cancel button, how used in Modifier 14cascading menus, defined 93change flag, defined 93charts

composite format options 66currency format options 66drawn object properties 30field properties 27-28formats for currency fields 36numeric format options 66standard buttons in the Modifier 14static picture values 63static text values 62string format options 66window properties 26

check boxcontrol type 49defined 93static picture values 57Style property 57tool 23types 57

Clear, menu item 12CloseBox, window property 26combo box

control type 50defined 93tool 23

components, defined 93composite formats

example 67

composite formats (continued)format options 66

compositesdefined 93formatting 67

configurations, for Modifier 82Contents, menu item 12control types

defined 93described 46list of 48static values for 62, 63

ControlArea, window property 26conventions, in documentation 2Copy, menu item 12core resources


currencycontrol type 50formats

format options 66using format fields 36

tool 23Customization Maintenance window 89Customization Site Enabler


customizations, see modificationsCut, menu item 12

DData Type Definition window 61data types

chapter 61-63characteristics 61defined 93described 61format 63keyable length 61opening 61opening from global fields 69static values 62

DataType, field property 27date, control type 50date tool, using in window layout 23Default, field property 27, 93DefaultDblClick

defined 93field property 27scrolling window property 41

definition windowsdefined 93described 13

Delete button, how used in Modifier 14deleting modifications 88dictionaries, defined 93Direction, field property 28DisableLookup, field property 27display name, for menu items 44distributing modifications 89

I N D E X


documentation, symbols and conventions 2

DraggableCols, field property 27drawn objects, properties, list 30drop indicator, for button drop lists 58drop-down list


DropIndicator, field property 28DropPosX, field property 28DropPosY, field property 28

EEdit Launch File window 82Edit menu, described 12Editable, field property 27EditMode, field property 27elements of arrays, defined 93EndTransaction, field property 27Exit, menu item 12ExpandButtons, field property 28expanded mode, for scrolling windows 40exporting package files 89

FField, field property 27Field Definition window 69Field Descriptions, menu item 11field properties, list 27-28FieldID, field property 27fields

adding prompts 47adding to a window, procedure 32adding to scrolling windows 42auto-complete fields 35chapter 69creating local fields 45creating new fields 45defined 93linking format fields 36linking prompts 33object properties 27opening 69opening data type 69properties, list 27resizing 33tab sequence 31types of 69visual properties 28

FieldType, field property 27focus, defined 93Font


FontBolddrawn object property 30field property 28

FontColordrawn object property 30field property 28

FontColor (continued)scrolling window property 41

FontItalicdrawn object property 30field property 29

FontUnderlinedrawn object property 30field property 29

Form Definition window 21, 43Format Definition window 65format fields

defined 93described 36example 37use 37

format linking mode, described 36format strings

composite formats 67defined 93described 66example 67string formats 66using to add static elements 66

formatsaligning field information 65chapter 65-67composite formats 66, 67currency, format options 66defined 93described 65format strings 66naming 65numeric, format options 66opening 65options 65string formats 66

formscreating modified forms 18defined 93described 8example 8finding form name 17selecting form to modify 17

forms dictionarychanging location 82changing name 82core resources 81default location 82default name 82defined 93described 81launch file 81modified forms 81storing locally 82storing on network 83

FullRowSelect, field property 29

GGenerate Resource Reports

described 77menu item 11

Getting Started with the Modifier, chapter 7-9

global fieldsadding to a window, illustration 32chapter 69defined 93described 69opening 69opening data type 69

Global Modifications, part 60-78grid

described 25for window layout 25grid spacing, setting 25

Grid to Back menu item 25GridLines, field property 29group box, defined 94

HHelp menu, described 12HelpContextID

field property 27scrolling window property 41window property 26

horizontal list box tool 23Hyperspace, field property 27

Iimages, for push buttons 56ImageSize, field property 29Import Package File window 90importing package files 90Indent, field property 29IndicatorColor, field property 29Insert button, how used in Modifier 14integer

control type 51tool 23

invisible fields, showing in layout 24

Kkeyable length

defined 94described 46, 61

keyboard equivalent, defined 94

Llaunch file, described 81layout area

described 24for scrolling windows 39for windows 24

Layout window 22layout windows

defined 94described 14opening 21

light bulb symbol 2line tool, using in window layout 22LineColor, drawn object property 30Lines, field property 29LineSize, drawn object property 30


I N D E X

LinkedFormat, field property 27LinkedLookup, field property 27LinkedPrompt, field property 27linking

fields to format fields 36prompts to fields 33

LinkTable, scrolling window property 41LinkTableKey, scrolling window property

41list box


list fields, defined 94Local Field Definition window 46local fields

adding to layout area 46array size 46characteristics 46control type 46creating 45creating with the Toolbox 47defined 94described 45, 69keyable length 46list of 45static values 46

long integer, control type 52Lookup, menu item 12lookup buttons

described 14native pictures used 73

MMacro menu, described 12margin notes 2Menu Definition window 43menu items

access keys 44defined 94display name 44editing 44naming 44special characters 44

menusaccess keys 44defined 94editing menu items 44menu definition 43menu items 44modifying 43opening 43

menus in ModifierEdit menu 12File menu 11Help menu 12Macro menu 12Resources menu 12Windows menu 12

messageschapter 77-78

messages (continued)defined 94described 77finding 77message ID 77modifying, procedure 78overview 77replacement markers 77use 77

metafiles, as pictures 71Microsoft Dynamics GP Modifier, see

Modifiermodal dialog, defined 94modifications

distributing 89packaging 89removing 88storing 8, 81types of 7

modified formsaccessing 85defined 94removing 88viewing 85

Modified Forms window 18Modifier

accessing 85configurations 82described 2exiting 11getting started 7interface 11local forms dictionary 82menus 11network forms dictionary 83packaging a project 89registering 9returning to the main application 11selecting a product 9starting 9storing modifications 8terminology 7toolbar 11types of modifications 7

modifyingsee also individual resourcesthird-party resources 87windows 21

Modifying Forms, part 16-58Modifying Menus, chapter 43-44Modifying Scrolling Windows, chapter

39-42Modifying Windows, chapter 21-38MultiSel, field property 27multi-select list box


NName

scrolling window property 41window property 26

namesfinding for forms 17formats 65

Native Picture Definition window 72native pictures

chapter 71-74creating, procedure 72-73defined 94described 63, 71examples 73for push buttons 73for visual switches 74synchronizing, procedure 73using 73

New button, how used in Modifier 14non-native list box, control type 52normal mode, for scrolling windows 40numeric formats, format options 66

Oobject properties, for fields 27OK button, how used in Modifier 14Open button, how used in Modifier 14overwriting customizations with package

files 91

Ppackage files

contents 89defined 94described 89exporting 89import/export issues 91importing 90overwriting customizations 91

Packaging Modifications, chapter 89-91Password, field property 28, 94Paste, menu item 12Pattern

drawn object property 30field property 29scrolling window property 41

PatternColordrawn object property 30field property 29scrolling window property 41

PatternSelect, field property 29Picture Definition window 71picture library

adding pictures to 71defined 94using pictures from 72

picture tool, using in window layout 22pictures (resource)

adding to picture library 71adding to windows 33, 72chapter 71-74

I N D E X


pictures (resource) (continued)described 63, 71example 71for check boxes 57for push buttons 56

pixel, defined 94point size, defined 94positioning, windows 32Position-Left


Position-Topdrawn object property 30field property 29scrolling window property 41window property 26

previewing, windows 30Print Setup, menu item 11procedures

Adding a picture to the picture library 71-72

Adding fields to a window 32Adding prompts 47Creating a modified form 18Creating local fields 45-46Creating native pictures 72-73Finding a form name 17-18Modifying a message 78Modifying a string 75Positioning the window 32Setting tab sequence 31Synchronizing native pictures 73Using a picture from the picture

library 72Process Monitor, menu item 11product support, for the Modifier 3products, selecting product to modify 9progress indicator


promptsadding to windows 47defined 94for scrolling windows 39linking to fields 33

propertiesdefined 94for drawn objects 30for fields 27for scrolling windows 41for windows 26setting 26

Properties window, using 25push buttons

access keys 62caption and images 56control type 53defined 94

push buttons (continued)native pictures for 73pictures for 56static picture values 56tool 23using 56

Rradio buttons

control type 53defined 94tab sequence 31tool 23using 31

radio groupscontrol type 54defined 94tab sequence 31tool 23using 31

registering the Modifier 9relative decimal position, defined 94Remove button, how used in Modifier 14removing modifications 88replacement markers


Report Writercontrolling access 85security task 85

Required, field property 28Resizeable, window property 26Resize-Horizontal

drawn object property 30field property 29scrolling window property 41

Resize-Verticaldrawn object property 30field property 29scrolling window property 42

resizing windowsautomatic resizing 33described 33horizontal resize properties 34per field resizing 33vertical resize properties 34

Resource Descriptions toolaccessing 11defined 95

resource list windowsdefined 95described 13

resource reports, to list messages 77Resources menu, described 12runtime engine, defined 95

SSavedOnRestart, field property 28Scaling, field property 29ScrollBars, field property 28

scrolling windowsadding fields 42big line item 40defined 95described 39expanded mode 40layout 39modifying 39normal mode 40opening 39prompts 39properties 41small line item 40types of 41

ScrollToBottom, scrolling window property 41

Search for Help On, menu item 12security

accessing modified forms 85accessing the Modifier 85accessing third-party modifications

87setting access to customized

resources 91Security Role Setup window 85Select a form to modify window 18Select All, menu item 12Selecting Forms to Modify, chapter 17-19series, defined 95SetChangeFlag, field property 28settings box

illustration 26using 26

Shape, drawn object property 30shape tool, using in window layout 22Show Field Names menu item 24Show Grid menu item 25Show Invisible Fields menu item 24ShowHeadings, field property 29ShowPartialItems, field property 29ShowSelection, field property 29size to default tool, using in window

layout 23size to narrowest tool, using in window

layout 23size to shortest tool, using in window

layout 23size to tallest tool, using in window layout

23size to widest tool, using in window

layout 23Size-Height


Size-Widthdrawn object property 30field property 29scrolling window property 42window property 27


I N D E X

small line itemdefined 95described 40

SortMethod, field property 28starting the Modifier 9static picture values

defined 95described 63native pictures 63pictures 63

static text valuesdefined 95described 62

Static Text Values window 63static values

described 46, 62static picture values 63static text values 62

storage size, defined 95storage types, defined 95Storing and Accessing Modifications, part

80-91Storing Modifications, chapter 81-83string, control type 54String Definition window 75string formats

described 66example 66format options 66using format fields 37

stringschapter 75defined 95described 75example 75formatting 66modifying, procedure 75tool 23using 75

Style, field property 29support, available for the Modifier 3symbols in documentation 2synchronizing

defined 95native pictures 73

Ttab sequence

defined 95described 31removing fields from 31setting 31

Table Descriptions, menu item 11TabStop, field property 28task, security task for Report Writer 85technical support, for the Modifier 3terminology, for Modifier 7text

aligning 65control type 54

text tool, using in window layout 22

The Modifier Interface, chapter 11-14third-party modifications, accessing 87tile horizontally tool, using in window

layout 24tile vertically tool, using in window layout

24time, control type 55time tool, using in window layout 23Title, window property 26toolbar, described 11Toolbox

arrange tools 23creating local fields 47defined 95described 22local field list 45tools 22-24

Tooltip, field property 28types of modifications 7

UUndo, menu item 12UseUniqueHelp, field property 28

VVBA, defined 95Visible, field property 29VisibleItems, field property 28visual properties

for drawn objects 30for fields 28

Visual Studio Tools for Microsoft Dynamics GP, defined 95

visual switchcontrol type 55native pictures for 74tool 23

Wwarning symbol 2window controls

lookup buttons 14standard buttons in the Modifier 14

Window Descriptions, menu item 11window fields, defined 95Window Help, menu item 12window layout, opening 21window properties, list of 26WindowID


windowsadding, fields 32creating new fields 45defined 95described 7invisible fields 24opening layout 21pictures in 33positioning 32previewing 30properties, list of 26

windows (continued)resizing 33setting, tab sequence 31

windows in Microsoft Dynamics GPAlternate/Modified Forms and

Reports 86Edit Launch File 82Security Role Setup 85

windows in ModifierButton Items 62Data Type Definition 61Field Definition 69Form Definition 21, 43Format Definition 65Layout window 22Local Field Definition 46Menu Definition 43Modified Forms 18Native Picture Definition 72Picture Definition 71Properties 25Select a form to modify 18Static Text Values 63String Definition 75

Windows menu, described 12WindowType


word wrap, defined 95WordWrap, field property 28

ZZoom


zoom pointer, defined 95

microsoft dynamics gp 2013 modifier user’s...

Documents