Microsoft GP 10.0 Integration Manager Set 3

Simple ODBC Source ✘ SQL Source ✘ Text Source ✘ Advanced ODBC Source ✔

In the IM.IMD ✘ In the registry on each workstation ✘ In the IM.dic on each workstation ✘ In the Dynamics.dic on each workstation ✔

Simple ODBC can only pull data from Excel spreadsheets ✘ Advanced ODBC can only be used by the 'sa' user ✘ Simple ODBC must be the only source on an integration ✘ Advanced ODBC requires a SQL statement to be written ✔

Sources Queries Data Sources Query Relationships Destination Mappings

There can be 0 or 1 record in the child for each record in the master ✘ There must be exactly 1 record in the child for each record in the master ✘ There can be 0 or more records in the child for each record in the master ✘ There must be at least 1 record in the child for each record in the master ✔

Local translations cannot be changed Local translations can only be used on the field and integration where they are created Global translations can be used on multiple integrations Global translations can only be used on integrations with the same destination

Give the spreadsheet a name that matches the query name ✘ Define a named range within the spreadsheet ✘ Format the spreadsheet as a eneral format ✘ The first Excel row must have column names ✔

Universal Translation Global Translation Local Translation Fixed Translation

It automatically upgrades, regardless of Integration Manager settings. ✘ It automatically upgrades, unless "Do Not Automatically Upgrade Sources and Destinations" is selected. ✘ It never automatically upgrades; the Database Conversion must be run. ✘ It never automatically upgrades; the adapters must be manually upgraded in Microsoft Access. ✔

Create a Microsoft Dynamics GP Login Macro Create a .BAT file to run an integration Create a macro to log out of Microsoft Dynamics GP Create a .BAT file to start Microsoft Dynamics GP