We did a project like this routine like this and we found that instead
of performing the translation datadriven, we build a code generator that
would construct the code from the driver tables, then it could be
compiled and run much quicker. Something to look at would be the newly
released feature in SP3 that does compiles at runtime, that way you could
construct the code and then run it automatically.

A gotcha is we couldn't compile programs with more than like 3000 lines.


>I am working on doing routine data imports from remote systems utilizing two data structures that are different from the local data structures, and cannot be changed.
>
>As a result, we have to map the incoming data to match the local fields, possibly performing some other manipulations. Currently, this mapping is hardcoded into the import routines.
>
>What I would like to do is drive the mapping out of a table. The MAPTABLE will contain the source table and fieldnames, the destination table and fieldnames, and the mapping protocol. For example, a last name may come over from field "last_name" all in UPPER case. I want to put it into "name1l", in PROPER case. The map protocol would look like this : PROPER(sourcetable.last_name)
>
>How do I get this to work in code, where the procedure/method/function reads the protocol and then applies it?
>
>Thanks,
>
>John