Course 8964A:

Tools for Visual Basic in Microsoft Dynamics SL 7.0

Length:3 Days
Published:July 09, 2008
Language(s):English
Audience(s):IT Professionals,Developers
Level:300
Technology:Microsoft Dynamics SL 7.0
Type:Course
Delivery Method:Instructor-led (classroom)
About this CourseThe Tools for Visual Basic course is designed to be a thorough, hands-on introduction to the Microsoft Dynamics SL Tools for Visual Basic program and how to use them to create new programs.
Course OutlineModule 1: Introduction, Starting a Tools for Visual Basic ProjectThe purpose of this chapter is to introduce the basic concepts and architecture of Tools for Visual Basic and discusses the importance of planning before an installation. Topics that are covered include what to do in pre-planning in addition to implementation and examine the hardware and software requirements for Microsoft Dynamics SL.Lessons
  • Understand the prerequisites and goals for the course.
  • Understand The Benefits of using Microsoft Dynamics SL Tools for Visual Basic.
  • Understand what programs are running when you use Microsoft Dynamics SL.
  • Understand the roles of the Microsoft Dynamics SL parent application and the data entry, maintenance, and process windows.
  • Have a basic introduction to the Microsoft Dynamics SL Kernel.
  • Have a model for setting up the development environment.
  • How to start a new Tools for Visual Basic project.
  • Understand the use of the Visual Basic Project Template.
Lab : Create and New Tools for Visual Basic Project
  • Using the template provided, create a Visual Basic project that is ready for Tools for Visual Basic.
After completing this chapter, students will be able to:
  • Create an environment for development.
  • Describe the components of Tools for Visual Basic and their general function.
  • Set up new Tools for Visual Basic projects.
  • Understand the components of the template.
Module 2: Creating a Program with One "Normal" LevelThis chapter covers the creation of a program that performs simple maintenance (insert, update and delete) and navigation on rows in a database table, one row at a time.Lessons
  • How to add a "Normal Level" to a Tools for Visual Basic Program.
  • Understand the concept of levels.
  • Learn how a ‘Normal Level" is implemented.
  • Learn the Microsoft Dynamics SL API calls needed to register your program with the Microsoft Dynamics SL Kernel.
  • Explore data navigation provided by the Microsoft Dynamics SL Kernel.
Lab : Create a Program with Normal Level
  • Implement a normal level to navigate and maintain a table in the Microsoft Dynamics SL database one row at a time.
After completing this chapter, students will be able to:
  • Implement a normal level program to maintain one row from the database at a time.
Module 3: Adding a New TableThis chapter covers the database objects that must be created to fully implement a new table in the Microsoft Dynamics SL database. It also covers the setup and implementation if a spreadsheet in a Tools for Visual Basic program that maintains a complete result set form the database.Lessons
  • How to add a new table to the Microsoft Dynamics SL database.
  • Learn the Required Database Objects to add a new table.
  • Understand Naming Requirements for Tables and Indexes.
  • Learn the Structure for Stored Procedures That Are Used by the Microsoft Dynamics SL Kernel.
  • Learn what a detail level is and how it works.
  • Implement a detail level, by using the SAFGrid control.
Lab : Adding a New Table
  • By using the tools that are provided, create and implement a new table in the Microsoft Dynamics SL database.
Lab : Adding a Detail Level
  • Implement the table created earlier in the training, in a spreadsheet as a child of the Customer table.
After completing this chapter, students will be able to:
  • Use the Record Maintenance and Field Maintenance to create a new table.
  • Create a unique index for the table.
  • Create a stored procedure that the Microsoft Dynamics SL Kernel will use to maintain the table.
  • Set up a Detail level in Tools for Visual Basic programs.
  • Understand the steps necessary to correctly program a Parent-Child relationship.
Module 4: Adding a Possible Values Lookup, Adding a Second Table to a Detail Level, Starting a New Project, Adding a Detail LevelThis chapter focuses on the importance of giving the user an easy-to-use interface for look-ups. A complete Possible Values window will be implemented. It also provides information about how to add an additional table to the detail level, created earlier in the training. The addition of the table facilitates the ability to join additional information into the spreadsheet. There is also a review of the concepts presented earlier in the training. A new Tools for Visual Basic project will be created for use in later sections. The main difference is in this implementation the detail level is the first level in the program.Lessons
  • Learn the properties required for a possible values (F3) lookup.
  • How to format the Possible Values window.
  • How to Use the Possible Values Import program.
  • How to add a secondary table to a detail level.
  • Creating an SQL statement that Joins the tables in a query.
  • How to populate the secondary buffer when a value changes.
  • How to start a new Tools for Visual Basic project .
  • Understand the use of the Visual Basic Project Template.
  • Add a detail level to a Tools for Visual Basic project when it is the first level (LEVEL0).
  • Implement an indexed spreadsheet.
Lab : Add a Possible Values Look-up
  • Learn the properties required for a possible values (F3) lookup.
  • How to format the Possible Values window.
  • How to Use the Possible Values Import program.
Lab : Adding a Second Table to a Detail Level
  • Join an additional table into the spreadsheet.
  • Add controls to display data from the joined table.
Lab : Create and New Tools for Visual Basic Project
  • By using the template that is provided, create a Visual Basic project that is ready for Tools for Visual Basic.
Lab : Adding Files to the Project and Code to the Form_Load Event
  • Add the necessary files to the project to set the Microsoft Dynamics SL Kernel framework.
  • Add program code to the form_load event and set properties to describe the program to the Microsoft Dynamics SL Kernel.
Lab : Finishing the Detail Level
  • Add controls to the form.
  • Set control properties to facilitate database navigation and updates.
  • Implement properties to determine the key field in the spreadsheet.
After completing this chapter, students will be able to:
  • Understand the relationship between a Possible Values definition and the stored procedure that is used to retrieve rows.
  • Use the Possible Values Import program.
  • Implement a Possible Values window.
  • Make a join in a stored procedure to include an additional table.
  • Understand the programming requirements to implement the join.
  • Retrieve data from the joined table when new rows are inserted into the spreadsheet.
  • Set up new Tools for Visual Basic projects.
  • Understand the components of the template.
  • Create and implement a table maintenance program that uses an indexed spreadsheet.
Module 5: Adding an Unbound Non-String Control, Adding an Unbound String Control, Manipulating Toolbar Buttons, Working With Memory Arrays, Updating Rows in the DatabaseThis chapter focuses on adding controls that are used to store user selections and additional information that will be used by the processing part of a program. The control is not bound to a field in the database. The focus is on the programming steps to implement the control on the form when it is not in a spreadsheet. This chapter also focuses on the steps that you must follow to implement an unbound control in a spreadsheet that uses the Microsoft Dynamics SL SAFGrid control. Additionally, the exercise points out basic differences in programming for non-string controls and string controls. This chapter also covers a Microsoft Dynamics SL API function call that allows for a straight forward way for a programmer to manipulate program behavior by turning toolbar buttons on and off. It also explores the interaction of the Tools for Visual Basic program and database engine. The Microsoft Dynamics SL Kernel has a comprehensive set of API calls to create result sets, retrieve rows from the result set, update rows in the database, delete rows from the database, and insert rows into the database.Lessons
  • Learn how the Microsoft Dynamics SL Kernel links controls to buffer variables.
  • Learn how to add a Microsoft Dynamics SL custom data control that is not attached to a field from any tables in the database.
  • Learn to use the Microsoft Dynamics SL Code Inspector utility.
  • Learn how to add a Microsoft Dynamics SL custom data control that displays a string value that is not attached to any fields from tables in the database.
  • Learn how to implement an unbound control in a spreadsheet.
  • Learn why a user-defined type (UDT) is required when the unbound control holds a string value.
  • Add a control to the project from the Visual Basic toolbar.
  • Add program code to implement the unbound control.
  • Create an new User-Defined Type (UDT).
  • Learn how memory arrays are accessed in the program.
  • Learn how memory arrays are created.
  • Learn Microsoft Dynamics SL Kernel API calls to locate memory arrays.
  • Learn how to manipulate and update data in memory arrays.
  • Learn how to retrieve and update rows in the database, by using Microsoft Dynamics SL Kernel API calls.
  • Explore the Microsoft Dynamics SL Kernel API calls for performing floating-point math.
  • Learn Microsoft Dynamics SL Kernel API calls for database manipulation.
  • Learn Microsoft Dynamics SL Kernel API calls Start and End a database transaction.
Lab : Adding an Unbound Non-String Control
  • Add a control to the project form the Visual Basic Toolbar.
  • Add program code to implement the control.
Lab : Adding an Unbound String Control
  • Add a control to the project from the Visual Basic toolbar.
  • Add program code to implement the unbound control.
  • Create a new User Defined Type (UDT).
Lab : Manipulating Toolbar Buttons
  • Turn off buttons to save, delete and insert rows.
Lab : Working with Memory Arrays
  • Add a command button from the Visual Basic toolbar.
  • Add processing code to Locate and update the memory array.
  • Add code to update the memory array to show the changed data.
Lab : Updating Rows in the Database
  • Add code to start and end a database transaction.
  • Add code to fetch rows from the database.
  • Add code to update rows in the database.
  • Add code to calculate using Microsoft Dynamics SL API functions for floating-point math.
After completing this chapter, students will be able to:
  • Understand how the Microsoft Dynamics SL Kernel binds controls.
  • Know the difference between bound and unbound controls.
  • Use Code Inspector to check for programming problems.
  • Paste controls in the project from the Visual Basic Toolbar.
  • Add unbound string controls to a project.
  • Set the starting values for the control.
  • Add space to the memory array to store the unbound values.
  • Use Code Inspector to check the control settings.
  • Use the API call to change toolbar button behavior.
  • Control toolbar button behavior for each level in a program.
  • Use Microsoft Dynamics SL API functions related to memory arrays.
  • Access memory arrays.
  • Browse through memory arrays.
  • Change and update data in a memory array.
  • Display changed data in the spreadsheet.
  • Start and end a database transaction.
  • Use floating-point math API functions.
  • Create a result set on the database engine.
  • Fetch rows from the result set to the program buffers.
  • Update rows in the database.
Module 6: Using the Process Status Form, Giving Users Access, Printing Reports, Working with the Microsoft Dynamics SL Object ModelThis chapter explores methods for keeping the user informed of events that are occurring when a process is running and gives feedback on the progress of the process. The Microsoft Dynamics SL Kernel provides an easy to implement API call to facilitate this communication to the user. The same API call is used to communicate information to an event log. It also explores suitable naming of programs, creation of the executable file, adding a program to the Microsoft Dynamics SL Menu, and integrating new windows into Microsoft Dynamics SL Security. This chapter also explores the facility provided by Microsoft Dynamics SL to make the task of printing reports an easy exercise for both the user and programmer. There is a brief introduction to the Microsoft Dynamics SL Object Model. Microsoft Dynamics SL is equipped with a Common Object Model (COM). The Common Object Model provides programmers The ability to manipulate Tools for Visual Basic programs from any program or application that is COM capable.Lessons
  • Learn how display a status window while a process is running.
  • Learn to log events and errors during a process.
  • Learn how to correctly name a Tools for Visual Basic program.
  • Learn how to make the executable program.
  • Learn how to add program and reports to the Microsoft Dynamics SL Menu.
  • Learn How to implement security in a Tools for Visual Basic program.
  • Learn how reports are printed in Microsoft Dynamics SL.
  • Learn How to add a new report Microsoft Dynamics SL’s report control table.
  • Explore the processing logic of the Report Options Interpreter program (ROI.EXE).
  • Learn how to print a report from a Tools for Visual Basic program.
  • Learn how to instantiate and use the Microsoft Dynamics SL Common Object Model (COM).
  • Learn how to add "drill down" capability from a Tools for Visual Basic Tools program to another Tools for Visual Basic program.
  • Explore manipulation of controls in the instantiated program.
Lab : Using the Process Status Form
  • Add code to open the Status Form.
  • Add code to communicate progress and activity to the user.
  • Add code to close the Status Form.
Lab : Naming Programs and Creating Executable Files
  • Add a suitably formatted form caption to programs.
  • Create suitably named executable files from a Tools for Visual Basic program.
  • Add windows and reports to the screen table to enable security administration.
Lab : Adding Windows and Reports to the Microsoft Dynamics SL Dashboard Menu
  • Add modules, by using Modules Maintenance.
  • Add Windows and Reports, by using screen Maintenance.
  • Create a custom menu, by using menu maintenance.
Lab : Adding and Printing Reports
  • Add a new report to the RptControl table.
  • Run a report from the ROI.EXE user interface.
  • Add a command button from the Visual Basic toolbar.
  • Add code to print a report from a Tools for Visual Basic Program
Lab : Instantiate a Microsoft Dynamics SL Program
  • Add a command button to the window.
  • Declare a Microsoft Dynamics SL object variable (SIVApplication).
  • Add code to instantiate the Microsoft Dynamics SL Customer Maintenance program.
Lab : Manipulate the Instantiated Object Variable
  • Add code to retrieve a row from the customer table.
Lab : Give Control to the User
  • Add code to release the connection to the instantiated object, and let the user control the object.
After completing this chapter, students will be able to:
  • Open and close the status form.
  • Communicate progress and events to the user.
  • Log information to the Microsoft Dynamics SL Event Log.
  • Create suitably named executable files form a Tools for Visual Basic program.
  • Add new programs and reports to the Microsoft Dynamics SL security administration facility.
  • Add modules and menu items to the menu.
  • Add new reports to Microsoft Dynamics SL.
  • Understand the ROI.EXE processing flow.
  • Print a report from a Tools for Visual Basic program.
  • Create an SIVApplication variable.
  • Instantiate an instance of a Microsoft Dynamics SL program from a Tools for Visual Basic program.
  • Instantiate an instance of a Microsoft Dynamics SL program from an external application.
  • Manipulate instantiated object variables.
  • Give control of the object over to the user.
Before attending this course, students must have:
  • A working knowledge of Microsoft Windows Server 2003, XP and Vista.
  • A basic knowledge of accounting terms and processes.
  • A good working knowledge of SQL Server.
  • Some experience with SQL Server.
  • A good working knowledge of Microsoft Visual Basic.
Looking for training resources, events and advice from peers? Join the Microsoft Training and Certification Community. Preparing for an exam now? Find your Microsoft Certification Study Group. Talk to us on these social networks:

Find a Microsoft Learning Partner near you

Find Training Near You

Location:

Eg: Seattle, WA or Paris, France