>It has code free part and code support part. You have control over what gets into your table really, how (ie: you can get a single text file and parse into multiple tables), duplicates check etc. and displays the import results. It doesn't directly import into a table but into a cursor, and lets you control rest (the hard part of a text file import is to create a compatible cursor, it does that, rest might be as easy as 'append from' or complex like getting text file for a multijoin view and parsing into multiple tables). You can even do multitable imports with no view in sight (cursor structure you choose).
>Code free part handles, file type, field mappings, text to code conversions (ie: in text file it's "Beverages", in your table is an enumeration got from a lookup table), record selections, mapping save/restore. In our real world usage it even has a recorder that saves all the parameters and does the import as a scheduled task.
>
>Summarized for your question:
>-Yes you can map all or few of them and in any order. You as a developer specify which fields are required at least, which combination of fields define a 'unique' record for dupe check.
>User need to map the required columns at the very least (marked yellow).
>Plus if it's a CSV then you may not need any mapping. Plus it supports 'fixed' value during import (ie: if column X is not in text file but needs to be say "MyText" for all records it could simply be written there instead of a column mapping).
>-Mapping gets saved. It's saved to a local Mappings.dbf file. Also in our real world usage it's saved as an XML as part of the 'recorder' parameters.
>
>PS: The thing you saw in sample is relatively older version.
>Cetin

Thanks a lot. All answers to my complete satisfaction.