I am working on an import class. What this class will do is:

(1) allow the user to select an import type
(2) allow the user to select a file from that import type
(2) from that import type create some temporary tables and structures unique to that import type
(3) append the import file into the newly created temporary tables
(4) do some file processing unique to that import type


I'm running into design problems trying to make a generic class that can handle any import type and unique file processing for that type. How I had it set up originally is have a table with an import type field, a structure memo field (in which I have a list of table structures and names for that type), and a process memo field (in which I place the custom processing code for that import type.

I'm having all sorts of problems with macro substituting structural arrays for the creating of tables and the same for processing routines. I really didn't want to hard code this information for each new import type we get.

Perhaps my whole approach is wrong? Anyone have any ideas on a better approach to this type of class? Any input/discussion would be much appreciated...hey, I know you all like theoretical discussions ;).