Most lookup tables should need little additions to the data provided on installation of WellRep.  When adding new values to lookup tables this should be communicated so that the new value can be added to lookup tables in other databases in use (e.g. central office database or other field databases).  This is important to maintain data consistency.

 

For some tables however, this could become quite complex.  A good example is the lookup table for Cost Items.  Depending on company requirements, this table may become very exhaustive with detailed coding for various cost items.  In addition, coding of cost items should be consistent throughout the company.  To prevent having to input all these codes manually whenever a new database is installed (e.g. on a field computer), the lookup table may be exported from a database in which they are already defined.  On the new database, they can then simply be imported and used.

 

Currently the following lookup tables can be exported and imported.  For the other tables the [Export...] and [Import...] buttons will be disabled.

 

1.Company

2.Cost

 

To export the lookup table, click the [Export...] button at the bottom of the Lookup Data Maintenance dialog, select a folder where to save the file and click [Save].  To prevent confusion, it is recommended to keep the suggested file name.

 

 

 

To import the lookup data, open the Lookup Maintenance dialog box and go to the tab of the table to which the data must be imported.  Click the [Import...] button and select the file that should be imported.

 

 

Click the [Open] button to import the file into the current lookup table.

 

When clicking the [Open] button to import the file, a warning message will appear asking confirmation to import. All existing data in the selected lookup table will be permanently deleted before importing (i.e. existing lookup data is overwritten).  This cannot be undone.  If not sure, or just as good practice, it is a good idea to first export the current lookup data to file (e.g. named _luCost_TEMP.wrl) before importing the new data.  If anything goes wrong, changes can be rolled back by simply importing the temporary export.

 

Further reading: Using and maintaining lookup data.