data Merger

Data Merger Forms application • The application will read from the supplied Schema files. • It will be a GUI based forms application. • The application ill look similarly to the below. • • The application will make use of 2 treeviews from Schema 1 and Schema 2 and populate 2 values as seen on the above image. They will be the element name and element type. • The User will be able to select the 2 fields to match on(in this case it is the “ID”) • The application will also be able to output any Unmatched records when the “Create Unmatched output from B” is selected. • The application will also make use of the “Case Level”. As default it will not be selected. When selected it will match on the 2 requested fields as Case Sensative. • The user will be able to select from 1 of the 2 file that will be the main data source as an option. Processing: 1. The application will output to a specific Directory. 2. The output will be a Schema file, much like the ones supplied that will indicate the 2 merging fields. These 2 fields will have a specific indicator: “MergeOn=yes” to signify the merge. 3. The output will also contain all records that were unmatched if the “Create Unmatched output from B” is selected. The programmer must demonstrate the “Function” that creates the non-merged file for output as this function will be used in another portion of the application and it will not be part of this application. 4. The output will contain the main file with all data to include the merged data. The programmer must demonstrate the “Function” that creates the merged file for output as this function will be used in another portion of the application and it will not be part of this application. 5. The output of the main file will be in XML format as in the master schema. Note: • The schema from B must fall under the Root array of A when matching and be part of that Array. Out of scope • “Memory Usage” • “Binary Compare • “Locale” • “strength” • “French Collation” • “Normalization Mode”