Planning and Building Custom Tables
Once you have gathered the requirements and planned the Custom Interactions, you are ready to build the custom tables that will hold the Interaction data. There are two strategies for building custom tables in Metrix:
- Creating new data and lookup tables in devmodule.mdb and then importing the tables into interactsql.adp, where you can further customize the forms. The tables are then associated with Interactions through the Interaction Definition in Metrix.adp. These tables are generally imported without any data, except perhaps values in lookup tables for fields requiring a drop-down list.
- Preparing and importing existing tables into devmodule.mdb and then importing them into interactsql.adp, where you can customize forms and eventually setup the Interactions in Metrix.adp. This method is used when an organization has a significant amount of data that is suitable for importing into Metrix.
Many Metrix implementations will require that you both import custom tables with data and create new tables for which there is no data.
||Note: The image lists Metrix.mdb and interactsql.mdb. They are no longer .mdb files. They are .adp files.
Figure: Steps for Creating Custom Tables
Creating custom tables will always involve steps 2 and 3, and if there is custom Interaction data to be imported, then it will also involve step 1.
- Importing tables: When a client has data that needs to be imported as custom Interactions, then these tables must first be imported into Excel, where they are prepared to be integrated as custom tables. From there, the Excel spreadsheets are imported into devmodule.mdb, where the custom tables are formatted. To learn about importing existing tables for custom Interactions, please see Preparing Custom Tables for Importing Interactions.
- Building new tables: If an organization does not have data that needs to be imported as custom Interactions, or if you need to create custom tables for Interactions for which there is no data, then you will build those tables in devmodule.mdb. To learn about building new tables in devmodule.mdb, please see "Importing Custom Table with No Existing Data" in Building New Custom Tables for Interactions.
- Importing tables into interactsql.adp: All tables that will be used for custom Interactions, whether they are imported tables containing data or newly made tables with no data, will need to be moved into interactsql.adp using the Manage Custom Tables feature, which is displayed when interactsql.adp is opened.
Some of the issue to think about when considering whether to import custom Interaction data or to create new custom tables are:
- How reliable is the organization's data? We do not recommend importing data that is not reliable, as it will serve to jeopardize the accuracy of the new database.
- How complex is the structure of the existing data? Sometimes databases are created with a structure that does not lend itself to a direct import. A common example is a very flat table structure where (spreadsheet-style database) where new columns are appended each time new data is added.
- How many records do you need to migrate? If only a few records need to be added, it can be better to create new custom tables and advise the organization to re-enter the Interaction data directly into Metrix. If, on the other hand, there is a significant amount of data, then it may be advisable to work with the data in Excel or Access in order to configure an efficient table structure and then prepare it for migration into Metrix.
If you have existing data to import for custom Interactions, your next step is: Preparing Custom Tables for Importing Interactions. If you do not have any custom Interaction data, then you can proceed to Building New Custom Tables for Interactions.