Create a record processing utility in VB2008

Write a utility application in VB2008 that continuously inspects records and fields in specified MS-Access tables and if the records are new or have changed, adds/updates words in related records in the same table by looking up values from a reference table.? ## Deliverables ? **Project:** Write a utility application in VB2008 that continuously inspects records and fields in specified MS-Access tables and if the records are new or have changed, adds/updates words in related records in the same table by looking up values from a reference table.? ? There are several MS-Access tables attached that can be used for development and final project acceptance testing.? ? ? Table "Standard Terms" (see attached tables) is a repository of terms that have identical industry usage depending typical usage by different groups of people.? For example, some people often use SLANG words while another group of people might use PROFESSIONAL terminology for lectures, while a third group may require proper ISO Standard terminology for writing formal papers.? This table is manually updated by linguistics staff and records are added to it by the processing routine described below.? ? **Project Deliverable #1** is a simple Windows UI panel with an editable list view of the "Standard Terms" table that allows people to edit the records. ? ? Table "Table Info" (see attached tables) is a program control table that tells the processing routine (below) the names of the tables to process.? The processing routine processes the first table, pauses the number of seconds in the "Pass Pause" field, then processes the next file (etc.).? After having processed the final (or only) file, it then starts over with the first file. ? Three fields must be part of each table that is processed.? They tell the processing routine the state of the record, the terminology "class" of the contents of the record, and link associated records together.? The person running the application must insert the names of these fields in each table into fields "Status Field Name",? "Record Class Field Name", and "Sync Field Key Name" ? for each file to be processed.? There is also the field "Last Run Completed" where the processing routine will post the date/time the last pass on each table was completed. ? **Project Deliverable #2** is a simple Windows UI panel with a "DataSheet" view of the "Table Info" table that allows people to edit records in the "Table Info" table. ? ? Attached tables "Chemical Terms" and "PetroDerivatives" are simple examples of tables to be updated by the processing routine. ? Tables can have any number of TEXT fields so the routine must identify fields when starting to process each table. ? The table field specified in "Status Field Name" will be a logical field that is null by default for new records and will be set to either "True" (1) or "False" (0) after the record is processed by this routine.? This field will always set to "False" by any external applications that modifies data in the record.? ? "False" or Null values in this field means the processing routine should process this record. ? The table field specified in "Record Class Field Name" will contain the class of the words in the record.? Every record added to the table including by this processing routine must contain a terminology class value. ? The table field specified in "Sync Key Field Name" will identify related records in the table. This field will be blank the first time it is processed. ? ? The application user will launch and stop the processing routine.? ? **Project Deliverable #3** is a Windows UI panel with a "Start/Stop" button that launches or interrupts the processing routine described above. ? ? ? **New Records:**? This processing routine looks for any new records in each table (status = null or "No" and no related records exist) then adds two new related records and populates their fields using terms looked up from the "StandardTerms" table.? For example, if the new record being worked is of the class "Slang", then it needs to add a "Professional" record and a "ISO Standard" record.? ? For each field in the two new records, it needs to look up each "Slang" word (unless the slang word field is blank) and insert the corresponding "Professional" or "ISO Standard" word into the new records.? When adding records, the system must generate a unique value to be inserted into the "Sync Key Name" fields of all three records indicating they are associated to each other. ? If the processing routine is able to look up all the slang words in the "Standard Terms" table, and if all the "Professional" and "ISO Standard" terms are there, then it would set the "Status" flag to "Yes" on the two new records, then finally (final step to protect against processing interruptions) set the status flag to "Yes" on the record being processed. ? For each Slang word that is not found in the "Standard Terms" table, the processing routine must insert a new record back into the "Standard Terms" table that contains only the "Slang" word so that a clerical user can later edit the record and add the "Professional" and "ISO Standard" words in preparation for the next processing pass. ? If the processing routine is not able to get responses to all of the Slang words, the "Professional" record "Status" flag will still be set to "Yes" indicating they have all the available data, but will be set to "No" on the record being processed, indicating that it has been processed at least once but still contains at least one word that has not been found. ? ? ? **Changed Records:** The processing routine also processes records with the status of "No" (a field in the record has changed, or the processing was not able to find all the words on the last pass).? Similar to processing new records, it again attempts to look up each field in the "StandardTerms" table.? ? As with new records, it needs to update the words currently in the two associated records.? For this exercise there is no need to know which field has changed, or even if the “Standard Terms?? has changed.? As it processes each record, simply overwrites the fields in the related records and set the related record status flag to "Yes.? Again, only after all of the fields in this record have been found and their matching look-up words written to the two related records should the record's status be set to "Yes". ? *(Side Note:? The business logic here is flawed because it could result in perpetual processing of records and also may result in records being processed out of order, but these issues are not important for this project deliverable and should not be considered.)* ? After all of records in a table being processed as described above, the "Last Pass Completed" field of the "Table Info" table corresponding to this table must be updated with the current date/time, then the processing routine must "sleep" for the number of seconds in the "Table Info" "Pass Pause" field.? After that, it will start to process the next file in the table, or, in the case there is only one record in the table (only one table to be processed), will restart on the same table. ? ? **Project Deliverable #4** is creating the processing routine described above.