|
Modifying data at import time
|
Top Previous Next |
|
In some cases data can be even more difficult to process. Pd' Programming has seen some very interesting ways of coding data. The bottom line is this: As long as it is consistent, IMW can handle it! In order to use the methods of data modification discussed in this section, the first section of this chapter must be understood. The user should be comfortable with using multiple import definition files. By placing a special code ahead of the field being imported, several manipulations may be requested. For example, if a street name has the characters N, S, E, W attached in front of it, they can be removed while importing. Another example: if a street name has the address attached to it, the address can be removed and the street preserved. In fact, in the previous example, the block number can be preserved as well. How? By specifying a special code in the first of the import definition files.
If the first of the import definition files has the number 9005 in the field number column, then any N_, S_, E_, W_, characters will be stripped from the beginning of the field after the field is assembled. This means that if in the example from the last section, we added one more import definition to the beginning of the chain, and that import definition specified a 9005 for street_1, then the N in N LINCOLN AVE would be removed. Of course, in that example the best solution would have been not to import it in the first place.
The rest of the fancy conversions can be a bit more complicated. They are listed here for those users with no other alternative. Obviously, it would be a far better choice to modify the data before IMW ever sees it. Also, if a situation exists where there is a real need for a new type of fancy conversion, please send us a request. It often takes but a few days to make such an addition and others may benefit as well. Note: The following table is provided for the information of those users whos import definition is already taking advantage of data conversions. Most new import definitions should not need to use these functions.
To simulate the conversion types listed below while using a .IML file, treat the conversion number as a function, as follows: Put a "@FI_" in front of the number and put the required values in the function as parameters. For example, instead of using 9001 and specifying a 38 as the divider as shown below, use "@FI_9001( TheData, "&" ). This will result in the correct calculation.
More:
|