![]() It also stores a copy of an ISO file containing SQL Server 2014 setup media mounted as the Z drive. Let’s see how we can eliminate this last remaining manual step in our procedure and finalize the capture.Īs a reminder, the original virtual machine used to generate the image hosts multiple data disks (whose number we control by using the $numberOfDisks variable in our script), striped into a single volume (to which assigned the letter F) constructed by leveraging the Storage Spaces functionality present in Windows Server 2012 R2. Note, however, that anyone taking advantage of such a solution would still need to manually initiate the second part of the SQL Server setup (by invoking the CompleteImage action) once a new, image-based virtual machine is brought online. Effectively, once you capture the virtual disks containing the operating system and the database engine setup files (which can be easily accomplished either directly from the Azure Management Portal or by using Azure PowerShell module cmdlets), you will be able to deploy any number of new systems based on the resulting image. For example, you can declare the variables in your code and then use the variables in the connection string.In our recently published article, we presented a script that provisions a new Azure Infrastructure-as-a-Service (IaaS) virtual machine running Windows Server 2012 R2 and prestages a SQL Server 2014 default instance. The Readme file describes how to declare the variables. dll file, see MBS CustomerSource Retirement.Ī Readme file is included with each version of the. You can also use the RetrieveGlobals_80.dll file for Microsoft Business Solutions - Great Plains 8.0 to retrieve the same information that this script example retrieves. ![]() ObjConn.ConnectionString = "Provider=MSDASQL DSN=GreatPlains Initial Catalog=TWO User Id=sa Password=password"ĬmdString = "Select ACTINDX from GL00105 where (ACTNUMST='" + Account + "')"ĪccountMaintenance.UserDefined1 = objRec!ACTINDX ![]() Set objConn = CreateObject("ADODB.Connection") Set objRec = CreateObject("ADODB.Recordset") In Visual Basic Editor, expand Great Plains Objects, and then double-click AccountMaintenance to open an Account Maintenance code window.Ĭopy the following code, and then paste it into the Account Maintenance code window. ![]() On the Tools menu, click Customize, and then click Visual Basic Editor. On the Tools menu, click Customize, click Add Fields to Visual Basic, and then click the Account Number field, the Description field, and the User-Defined 1 field. On the Tools menu, click Customize, and then click Add Current Window to Visual Basic. Open the Account Maintenance window in Microsoft Dynamics GP. To use the example script, follow these steps: The script returns this value when you enter a new account or use the Account Lookup button. The script will then return the account index value to the User-Defined1 field in the Account Maintenance window. After the connection is made, the script creates a recordset of the data that is stored in the GL00105 account index master table. This script will connect to the Microsoft Dynamics GP sample TWO database and log on as system administrator with a password. The following VBA script example can be used for the Description_AfterGotFocus event in the Microsoft Dynamics GP Account Maintenance window. This article describes how to use a Microsoft Visual Basic for Applications (VBA) script to connect to a Microsoft SQL database that is used by Microsoft Dynamics GP 9.0 and by Microsoft Business Solutions - Great Plains 8.0. This article describes how to use a VBA script to connect to a Microsoft SQL database that is used by Microsoft Dynamics GP.Īpplies to: Microsoft Dynamics GP Original KB number: 892700 Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |