Visual Studio Integration Toolkit For Microsoft Dynamics .
Visual Studio Integration Toolkit for Microsoft Dynamics GPVisual Studio Integration Toolkit forMicrosoft Dynamics GP (build 16)IntroductionVisual Studio Integration Toolkit for Microsoft Dynamics GP is a Dexterity add-on software toolwhich contains an Application Programming Interface (API) that can be called from Visual Studiodevelopment system using Visual Basic or Visual C# languages to integrate with functionalitynormally only available in Microsoft Dynamics GP via the Dexterity development environment,such as menu navigation.Compatibility informationThe tool was previously known as Menus for Visual Studio Tools. File and object names have notbeen changed to maintain compatibility with existing installations and projects. Each build of thetool is only compatible with the version of Microsoft Dynamics GP it was created for.Contents of the Visual Studio Integration Toolkit for Microsoft Dynamics GP ArchiveBelow is a table of the files included with the installer:File or Folder NameVSTMenus.cnkDescriptionTool chunk file (self installing applicationDexterity dictionary)VSTMenus.pdfUser guide documentation (this document)VSTMenus.txtQuick usage guide with example C# and VBscripts and version history.VSTMenus License.docEnd User License Visual Studio Tools Assembly for l Studio Tools XML descriptions oolkit.dll Visual Studio Tools Addin for Registration andsystem features (in Addins folder)VSTMenus Examples.zipVSTMenusCSharp sample Visual C# projectwhich add menus to Cards Sales menuVSTMenusVB sample Visual Basic project whichadd menus to Cards Purchasing menuWinthrop Development Consultants1
Visual Studio Integration Toolkit for Microsoft Dynamics GPInstalling Visual Studio Integration Toolkit for Microsoft Dynamics GP1. Visual Studio Integration Toolkit is installed by downloading the installer and executing it.Follow the onscreen instructions to install the product files into the Microsoft Dynamics GPapplication folder.Uninstalling Visual Studio Integration Toolkit for Microsoft Dynamics GP1. Visual Studio Integration Toolkit is uninstalled from its About window (Help AboutDynamics GP Additional About Visual Studio Integration. Then it can be uninstalledfrom Windows.Installing Visual Studio Integration Toolkit for Microsoft Dynamics GP sample projects1. From the VSTM Examples.zip archive, extract the VSTMenusCSharp folder and/orVSTMenusVB folder to your desired location in your development system. There is nospecific path recommended.2. For each of the projects, perform the steps 3 to 13 below.3. Open the project solution file (VSTMenusCSharp.sln or VSTMenusVB.sln) with Visual Studio.4. In the Solution Explorer, expand References. To see References, you might need to click onthe “Show All Files” button (second button from the left on the Solutions Explorer toolbar).For Visual Basic you will also need to expand the “My Project” node.5. Right click on the reference for Application.MenusForVisualStudioTools and click Remove.6. Right click on the References folder and click Add Reference.7. On the Add Reference dialog, select the Browse tab.8. Select the Application.MenusForVisualStudioTools.dll file installed previously the MicrosoftDynamics GP Application folder (default location: C:\Program Files\Microsoft Dynamics\GP).9. Click OK.10. Click to select the newly added Application.MenusForVisualStudioTools reference.11. In the Properties window, set the Copy Local property to False.12. From the Build menu, build the project.13. Copy the resulting VSTMenusCSharp.dll or VSTMenusVB.dll file from the project’s bin/Debugfolder to the AddIns folder in the Microsoft Dynamics GP Application folder.14. Launch Microsoft Dynamics GP.15. Look at Cards Sales for the “VS C# Test” menu items, or Cards Purchasing for the “VSVB Test” menu items.Winthrop Development Consultants2
Visual Studio Integration Toolkit for Microsoft Dynamics GPUsing Visual Studio Integration Toolkit for Microsoft Dynamics GP in your own projectsNote: The following section is assuming that you have an existing Visual Studio Tools forMicrosoft Dynamics GP project created.To use the Visual Studio Integration Toolkit for Microsoft Dynamics GP, you will need to add areference from your Visual Studio application to the Application.MenusForVisualStudioTools.dllfile you installed in the Microsoft Dynamics GP application folder. Below are the steps:1. In the Solution Explorer, expand References. To see References, you might need to click onthe “Show All Files” button (second button from the left on the Solutions Explorer toolbar). For Visual Basic you will also need to expand the “My Project” node.2. Right click on the References folder and click Add Reference.3. On the Add Reference dialog, select the Browse tab.4. Select the Application.MenusForVisualStudioTools.dll file installed previously the MicrosoftDynamics GP Application folder (default location: C:\Program Files\Microsoft Dynamics\GP).5. Click OK.6. Click to select the newly added Application.MenusForVisualStudioTools reference.7. In the Properties window, set the Copy Local property to False.Winthrop Development Consultants3
Visual Studio Integration Toolkit for Microsoft Dynamics GPRegistering Events for Visual Studio Integration ToolkitNext you need to add into the Initialize() function the commands to register for the twofunction events used by the tool for menus.Register the following function event to call the script to register/create your menu egister.InvokeAfterOriginalThe event handler called from this event then contains the commands to create the menus asneeded by your application.Then, register the following function event to call the script to handle the callback when a menuentry is Handler.InvokeAfterOriginalThe event handler called from this event then checks that the callback is caused by one of themenu items from this application and if so, performs the desired action, such as opening a VisualStudio Tools form.Below are examples of the required event registrations for Visual C# and Visual Basic:public void Initialize(){// Register Event to add menu gister.InvokeAfterOriginal entRegister);// Register Event to handle callbacks from menu ndler.InvokeAfterOriginal ntHandler);}Sub Initialize() Implements IDexterityAddIn.Initialize' Register Event to add menu entriesAddHandler InvokeAfterOriginal,AddressOf VSTMEventRegister' Register Event to handle callbacks from menu entriesAddHandler nvokeAfterOriginal,AddressOf VSTMEventHandlerEnd SubIn this sample the VSTMEventRegister() script would contain the function calls to add the menuitems and record their returned menu tags. The VSTMEventHandler() script would then use thefirst parameter e.inParam1 from EventRegisterFunction.InvokeEventArgs e argument objectreturned by the function call to obtain the menu tag of the menu item selected. This tag canthen be compared to the stored menu tags obtained during registration and if a match is found,the desired actions can be executed.Please see the VSTMenus.txt file or the Visual Basic and Visual C# examples included in thearchive for more information.Winthrop Development Consultants4
Visual Studio Integration Toolkit for Microsoft Dynamics GPRegistering Area Page Events for Visual Studio Integration ToolkitBuild 15 or above introduces support for Area Pages, if you wish to use this functionality youneed to add into the Initialize() function the commands to register for the two new functionevents used by the tool for Area Pages.Register the following function event to call the script to register/create your Area sterAreaPage.InvokeAfterOriginalThe event handler called from this event then contains the commands to create the Area Pagebutton and command list.Then, register the following function event to call the script to handle the callback when the AreaPage is HandlerAreaPage.InvokeAfterOriginalThe event handler called from this event then contains the commands to create the Area Pagecontent.Below are examples of the required event registrations for Visual C# and Visual Basic:public void Initialize(){// Register Event to add Area Page isterAreaPage.InvokeAfterOriginal r(VSTMEventRegisterAreaPage);// Register Event to add Area Page ndlerAreaPage.InvokeAfterOriginal (VSTMEventHandlerAreaPage);}Sub Initialize() Implements IDexterityAddIn.Initialize' Register Event to add Area Page s.EventRegisterAreaPage.InvokeAfterOriginal, AddressOfVSTMEventRegisterAreaPage' Register Event to add Area Page ns.EventHandlerAreaPage.InvokeAfterOriginal, AddressOfVSTMEventHandlerAreaPageEnd SubIn this sample the VSTMEventRegisterAreaPage() script would contain the function calls to addthe Area Page button and record the returned tag. The VSTMEventHandlerAreaPage() scriptwould then use the first parameter e.inParam1 from EventRegisterFunction.InvokeEventArgse argument object to obtain the tag of the Area Page selected. Then the call to add the AreaPage content can be made.Please see the VSTMenus.txt file or the Visual Basic and Visual C# examples included in thearchive for more information.Winthrop Development Consultants5
Visual Studio Integration Toolkit for Microsoft Dynamics GPGlossary of TermsBelow is a list terms used in this documentation and with Visual Studio Integration Toolkit forMicrosoft Dynamics GP:Dictionary ID:Short integer uniquely identifying a Dexterity Dictionary, also known as aProduct ID. The Dictionary ID for a product can be obtained from theDynamics.set launch file.Resource ID:Short integer uniquely identifying an individual resource within aDexterity Dictionary.Form:A container object that holds windows, scripts and commands.Form Name:The name of a form within a Dictionary.Form Resource ID:The Resource ID for a form within a DictionaryCommand:A Dexterity resource used for creating Menus and Toolbars. Commandsare contained on a form. To uniquely identify a command requires aMenu Tag:Short integer assigned to a command when it is added to the applicationmenu structure.Area Page:Navigation page in the application main window containing multiplemenus. Supported from Build 15 or above.LimitationsVisual Studio Integration Toolkit for Microsoft Dynamics GP has the following limitations: There is a maximum of 100 menu items shared among all Visual Studio addins using API. There is a maximum of 10 area pages shared among all Visual Studio addins using API. Menu items defined cannot be added to toolbars The menus added with this tool will not be visible to other Dexterity based applications.Product SupportTechnical support for Visual Studio Integration Toolkit for Microsoft Dynamics GP can beobtained by emailing support@winthropdc.com.While all efforts will be made to respond in a timely manner, due to time zone differences aresponse may take up to two business days.Winthrop Development Consultants6
Visual Studio Integration Toolkit for Microsoft Dynamics GPMenu structure in Microsoft Dynamics GPTo add your menu items to the set of menus in Microsoft Dynamics GP, you need to know howthe menus are structured. The following table shows the menu structure for the coreapplication. These are the menus you see in the Area Pages, in the Microsoft Dynamics GP menu,and the “Main” toolbar. You will use this information when you add the menu items for yourintegration.Top-level menuTools*Tools hasingInventoryPayrollTools ntoryPayrollTools oryPayrollTop-level menuSubmenuWinthrop Development ConsultantsFormCommand SystemCommand SystemCommand SystemCommand SystemCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollCommand SystemCommand SystemCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollCommand SystemCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollCommand SystemCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollFormCommandCL ToolsCL SetupCL System SetupCL Company SetupCL Posting SetupCL Financial SetupCL Sales SetupCL Purchasing SetupCL Inventory SetupCL Payroll SetupCL UtilitiesCL System UtilitiesCL Company UtilitiesCL Financial UtilitiesCL Sales UtilitiesCL Purchasing UtilitiesCL Inventory UtilitiesCL Payroll UtilitiesCL RoutinesCL Company RoutinesCL Financial RoutinesCL Sales RoutinesCL Purchasing RoutinesCL Inventory RoutinesCL Payroll RoutinesCL TransactionsCL Financial TransactionsCL Sales TransactionsCL Purchasing TransactionsCL Inventory TransactionsCL Payroll TransactionsCL InquiryCL System InquiryCL Financial InquiryCL Sales InquiryCL Purchasing InquiryCL Inventory InquiryCL Payroll InquiryCommand7
Visual Studio Integration Toolkit for Microsoft Dynamics entoryPayrollHelp*Command SystemCommand SystemCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollCommand SystemCommand SystemCommand FinancialCommand SalesCommand PurchasingCommand InventoryCommand PayrollCommand SystemCL ReportsCL System ReportsCL Company ReportsCL Financial ReportsCL Sales ReportsCL Purchasing ReportsCL Inventory ReportsCL Payroll ReportsCL CardsCL System CardsCL Financial CardsCL Sales CardsCL Purchasing CardsCL Inventory CardsCL Payroll CardsCL Help*We recommend not adding items directly to this top-level menuFor other Microsoft and third-party productdictionaries, you can find details of the menustructures and commands using WinthropDevelopment Consultants GP Power Tools.From the GP Power Tools area page, select theResource Information window (GP PowerTools Reports Resource Information).Make sure the window has the Resource Typeas Form, Window & Fields, then click on theMenu Lookup to open the Menu Explorer.On the Menu Explorer window use the buttonat the bottom right corner of the window toexpand the window.Now you can see the command dictionary,form and ID for any menu item selected in theleft-hand pane of the Menu Explorer.See the highlighted sections on thescreenshot.Winthrop Development Consultants8
Visual Studio Integration Toolkit for Microsoft Dynamics GPFunctions AvailableBelow is a list of the functions available to be called from theMenusForVisualStudioTools.Functions object.Registration Functions:Name:RegisterDescription:This function is used to create menu entries or parent menus entries for sub menus.Error codes are shown below.Qualified eturns:(Short) The Menu Tag of the registered menu or error code.Parameters:IN Parent TagIN CaptionIN TooltipIN KeyIN ModifierIN CheckedIN DisabledIN HiddenIN Below TagIN SeparatorIN ListRelated:GetTag, GetTagByName, UnregisterError Codes:-1 : Attempting to register more than the supported number of menus.-2 : No Parent Tag provided.-3 : No Caption provided.-4 : Parent Tag was provided, unable to identify Parent Command from Tag.-17: Visual Studio Integration Toolkit is not registered.Notes:Leave IN Below Tag as 0 for bottom of menu or set to -1 for top of menu.Constants for use with IN Key and IN Modifier shown after GetAcceleratorSetAccelerator functions.Winthrop Development ean)Menu Tag for ParentMenu Caption, cannot be emptyMenu Tooltip (optional)Menu Shortcut, ASCII value of keyMenu Shortcut Modifier (optional)Set to True to create menu as checkedSet to True to create menu as disabledSet to True to create menu as hiddenMenu Tag for menu entry to add belowSet to True to add Separator aboveSet to True to add Menu as Command List9
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:RegisterWithSecurityDescription:This function is used to create menu entries with security inherited from anapplication form. Error codes are shown below.Qualified ithSecurityReturns:(Short) The Menu Tag of the registered menu or an error code.Parameters:IN Parent TagIN CaptionIN TooltipIN KeyIN ModifierIN CheckedIN DisabledIN HiddenIN Below TagIN SeparatorIN ListIN SecurityDictIDIN SecurityResIDRelated:GetTag, GetTagByName, GetFormResID, UnregisterError Codes:Validate TagError CodesValidateForm Error Codes-1 : Attempting to register more than the supported number of menus.-2 : No Parent Tag provided.-3 : No Caption provided.-4 : Parent Tag was provided, unable to identify Parent Command from Tag.-5 : Security Form not applied due to table error-17: Visual Studio Integration Toolkit is not registered.Notes:Leave IN Below Tag as 0 for bottom of menu or set to -1 for top of menu.Winthrop Development ean)(Short)(Short)Menu Tag for ParentMenu Caption, cannot be emptyMenu Tooltip (optional)Menu Shortcut, ASCII value of keyMenu Shortcut Modifier (optional)Set to True to create menu as checkedSet to True to create menu as disabledSet to True to create menu as hiddenMenu Tag for menu entry to add belowSet to True to add Separator aboveSet to True to add Menu as Command ListDictionary ID for Security FormResource ID for Security Form10
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:RegisterSimpleDescription:This function provides a simplified registration syntax to add menu entries to the endof any existing menu in core Dynamics GP, Project Accounting, Field Service,Manufacturing and Human Resources.The Command List Name for the parent menu can be any command list commandfrom any of the command forms in the products listed above. The table providedearlier in the documentation includes the command lists for core Dynamics GP in thefinal column. Command lists for the other products can be identified using Dexterityfrom the following forms:Project AccountingField ServiceManufacturingHuman ResourcesCommand PASVC Command * (6 forms)Command MFGCommand HRThe command form and product dictionary do not need to be specified and parentmenu tag does not need to be identified first. The Error codes are shown below.Qualified impleReturns:(Short) The Menu Tag of the registered menu or error code.Parameters:IN Parent MenuIN CaptionRelated:GetTagSimple, UnregisterError Codes:ValidateFormByName Error Codes-1 : Attempting to register more than the supported number of menus.-2 : No Parent Tag provided.-3 : No Caption provided.-4 : Parent Tag was provided, unable to identify Parent Command from Tag.-13: Command Resource not found.-17: Visual Studio Integration Toolkit is not registered.Winthrop Development Consultants(String)(String)Command List Name for ParentMenu Caption, cannot be empty11
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:RegisterAreaPage (build 15 or above)Description:This function is used to create an Area Page Button and associated Command List.Error codes are shown below.Qualified reaPageReturns:(Short) The Area Page Tag of the registered Area Page or error code.Parameters:IN CaptionIN TooltipRelated:RegisterAreaPageContentError Codes:-3 : No Caption provided.-17: Visual Studio Integration Toolkit is not registered.-19 : Attempting to register more than the supported number of Area Pages.Notes:Generic images are used for the buttons as the commands to change the images didnot work for the Area Page buttons.Winthrop Development Consultants(String)(String)Area Page Caption, cannot be emptyArea Page Tooltip (optional)12
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:RegisterAreaPageContent (build 15 or above)Description:This function is used to create menu entries or parent menus entries for sub menus.Error codes are shown below.Qualified reaPageContentReturns:(Short) The Menu Tag of the registered menu or error code.Parameters:IN TagIN CaptionIN Tag1IN Pos1IN Tag2IN Pos2IN Tag3IN Pos3IN Tag4IN Pos4IN Tag5IN Pos5IN Tag6IN Pos6IN Tag7IN Pos7Related:RegisterAreaPageError Codes:-3 : No Caption provided.-17: Visual Studio Integration Toolkit is not registered.Notes:Tag left as 0 will be skipped and not added to the Area Page.Column Numbers can be 1 or 2 for v11.0 and 1 to 3 for V12.0 onwards. Leave theColumn Number as 0 for default column location.Winthrop Development rt)(Short)(Short)(Short)Area Page Button TagArea Page Caption, cannot be emptyMenu Tag for Transaction Menu (optional)Column for Transaction Menu (optional)Menu Tag for Inquiry Menu (optional)Column for Inquiry Menu (optional)Menu Tag for Reports Menu (optional)Column for Reports Menu (optional)Menu Tag for Cards Menu (optional)Column for Cards Menu (optional)Menu Tag for Setup Menu (optional)Column for Setup Menu (optional)Menu Tag for Routines Menu (optional)Column for Routines Menu (optional)Menu Tag for Utilities Menu (optional)Column for Utilities Menu (optional)13
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:UnregisterDescription:This function is used to unregister menu entries. This is only provided to allow menusto be removed due to an exception during the registration process. Ensure all childmenu entries are removed before removing the parent menu entry.This function will not return the unregistered menus to the pool of available menusentries. If you require the ability to dynamically control menus, use the Hide andDisable functions.Qualified rReturns:(Short) Returns zero for no error or an error codeParameters:IN Parent TagIN TagRelated:Register, RegisterWithSecurityError Codes:ValidateTag Error Codes-2 : No Parent Tag provided.-4 : Parent Tag was provided, unable to identify Parent Command from Tag.-16 : Unregistering Menu Tag failed.Winthrop Development Consultants(Short)(Short)Menu Tag for ParentMenu Tag to link Security Form to14
Visual Studio Integration Toolkit for Microsoft Dynamics GPSecurity Functions:Name:ApplySecurityDescription:This function is used to add/change security to an existing menu. Security is inheritedfrom an application form. Error codes are shown below.Qualified rityReturns:(Short) Returns zero for no error or an error codeParameters:IN TagIN DictIDIN ResIDRelated:GetFormResIDError Codes:ValidateTag Error CodesValidateForm Error Codes-5 : Security Form not applied due to table error.Name:RemoveSecurityDescription:This function is used to remove security from a menu. Error codes are shown below.Qualified urityReturns:(Short) Returns zero for no error or an error codeParameters:IN TagRelated:GetFormResIDError Codes:ValidateTag Error Codes-5 : Security Form not applied due to table error.Winthrop Development Consultants(Short)(Short)(Short)(Short)Menu Tag to link Security Form toDictionary ID for Security FormResource ID for Security FormMenu Tag to remove Security Form from15
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:CheckSecurityDescription:This function is used to check the application level security access of a Form given itsID. Error codes are shown below.Qualified rityReturns:(Short) Returns zero for no error or an error codeParameters:IN DictIN FormIN VerboseRelated:CheckSecurityByName, DisplaySecurityErrorError Codes:ValidateForm Error Codes0 : OKAY – Access Granted.1 : REJECT RECORD – Access Denied.2 : REJECT SCRIPT – Form not loaded.Name:CheckSecurityByNameDescription:This function is used to check the application level security access of a Form given itsName. Error codes are shown below.Qualified rityByNameReturns:(Short) Returns zero for no error or an error codeParameters:IN DictIDIN FormNameIN VerboseRelated:CheckSecurity, DisplaySecurityErrorError Codes:ValidateFormByName Error Codes0 : OKAY – Access Granted.1 : REJECT RECORD – Access Denied.2 : REJECT SCRIPT – Form not loaded.Winthrop Development Boolean)Dictionary ID for FormForm Resource ID for FormDisplay Security Error when Access DeniedDictionary ID for FormForm Name for FormDisplay Security Error when Access Denied16
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:DisplaySecurityErrorDescription:This function is used to display the “You don't have security privileges to open thiswindow” security error dialog.Qualified curityErrorReturns:(Short) Returns 1Parameters:NoneRelated:CheckSecurity, CheckSecurityByNameWinthrop Development Consultants17
Visual Studio Integration Toolkit for Microsoft Dynamics GPHelper Functions:Name:GetFormResIDDescription:This function is used to obtain the Resource ID of a form from a string containing theform's technical name. Error codes are shown below.Qualified sIDReturns:(Short) Resource ID for Form or an error codeParameters:IN DictIDIN FormNameRelated:RegisterWithSecurity, ApplySecurityError Codes:ValidateFormByName Error CodesName:GetIDsDescription:This function is used to obtain the Dictionary ID, Form ID and Command ID for a givenMenu Tag. Error codes are shown below.Qualified urns:(Short) Returns zero for no error or an error codeParameters:IN TagOUT DictOUT FormOUT CmdRelated:GetTagError Codes:ValidateTag Error CodesWinthrop Development ort)Dictionary ID for FormForm Name for FormMenu Tag to retrieveDictionary ID of Menu EntryForm Resource ID of Menu EntryCommand Resource ID of Menu Entry18
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:GetTagDescription:This function is used to obtain the Tag ID of a menu entry from the Dictionary ID,Form ID and Command ID. Error codes are shown below.Qualified urns:(Short) Menu Tag of specified Menu Entry or an error codeParameters:IN DictIN FormIN CmdRelated:GetIDs, GetTagByName, GetTagSimpleError Codes:ValidateCmd Error CodesName:GetTagByNameDescription:This function is used to obtain the Tag ID of a menu entry from the Dictionary ID,Form Name and Command Name. Error codes are shown below.Qualified ameReturns:(Short) Menu Tag of specified Menu Entry or an error codeParameters:IN DictIN FormIN CmdRelated:GetTag, GetTagSimple, Register, RegisterWithSecurityError Codes:ValidateCmdByName Error CodesWinthrop Development ring)Dictionary ID of Menu EntryForm Resource ID of Menu EntryCommand Resource ID of Menu EntryDictionary ID of Menu EntryForm Name of Menu EntryCommand Name of Menu Entry19
Visual Studio Integration Toolkit for Microsoft Dynamics GPName:GetTagSimpleDescription:This function provides a simplified syntax to obtain the Tag ID of any existing menu incore Dynamics GP, Project Accounting, Field Service, Manufacturing and HumanResources.The Command List Name for the parent menu can be any command list commandfrom any of the command forms in the products listed above. The table providedearlier in the documentation includes the command lists for core Dynamics GP in thefinal column. Command lists for the other products can be identified using Dexterityfrom the following forms:Project AccountingField ServiceManufacturingHuman ResourcesCommand PASVC Command * (6 forms)Command MFGCommand HRThe command form and product dictionary do not need to be specified and parentmenu tag does not need to be identified first. The Error codes are shown below.Qualified pleReturns:(Short) Menu Tag of specified Menu Entry or an error codeParameters:IN Parent MenuRelated:GetTag, GetTagByName, Register, RegisterWithSecurity, RegisterSimpleError Codes:ValidateCmdByName Error Codes-13: Command Resource not found.Winthrop Development Consultants(String)Command List Name for Parent20
Visual Studio Integration Toolkit for Microsoft Dynamics GPCallback Function:Name:CallbackDescription:This function is used to obtain the Tag ID of the just selected menu entry to becompared with the values returned during registration.Qualified eturns:(Short) Menu Tag of just selected Menu EntryPar
Microsoft Dynamics GP project created. To use the Visual Studio Integration Toolkit for Microsoft Dynamics GP, you will need to add a reference from your Visual Studio application to the Application.MenusForVisualStudioTools.dll file you installed in the Microsoft Dynamics
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
Microsoft Visual Studio 2010 : The Basics This is meant to be a quick tutorial to help understand some of the basics of Microsoft Visual Studio 2010 (from here on just "Visual Studio"). VISUAL STUDIO IS AN IDE Visual Studio is a tool that aids in the development of software systems.
2 Utilisation de Visual Studio 2.1 Ouverture de Visual Studio Tout d'aord, il Àous faut lancer Visual Studio en cliquant sur le bouton Démarrer et tapez « Visual Studio » dans la barre de recherche. Vous devez choisir « Visual Studio 2019 ». À sa sélection, le logiciel démarre. Lors
Sync, Studio 3, Studio 4, Studio 5 (and Studio 5 Lx), Studio 64X, Studio 128X, and Studio 64XTC. . document refers to an Opcode Studio 64XTC, but the next couple of pages are a little detour. Please don’t be confused. Your computer has at least one USB port, which looks like this: . If you have a blue G3, the USB ports are on the back.
3 1 Overview 1.4 What is in the Box Studio 26c and Studio 68c Owner's Manual 1.4 What is in the Box Your Studio-series package contains: Studio 26c or Studio 68c 24-bit, 192 kHz audio interface Quick Start Guide Audio Interface 1M USB-C to C Cable 1M USB-C to A Cable MIDI / S/PDIF breakout cable (Studio 68c only) External power supply (Studio 68c only)
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid
