Still have no clue as to what you mean by the "mapping function stalls".
Just hangs? Any error messages? The term "mapping" to means - during the
process where you indicate all the information is to be used but before any
data is being imported - ergo, if that's the case - would need info on where
you're at exactly. The term "importing" means that the process of moving
data from your source file to the Outlook folder has started - in which
case, has anything been imported? If yes, first thing to do is compare what
made it in and where that record resides in your Excel file - the record
immediately following it would be the first thing I'd look at. If nothing
got imported - your header row would be the suspect line.
Finally, in terms of Excel, we've run across more then one corrupt Excel
file that was only usable within Excel but couldn't be read properly
otherwise either by Outlook or any of our products (which is how we ran
across them). Once we reconstructed the spreadsheet - problems all
disappeared.
If you save your data to CSV format - can you import the CSV file. IF you
re-opened this CSV file in Excel - added a new named range for all your
data, save it as an Excel file - does the new Excel file exhibit the same
issues?
Karl
__________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0
"Power contact importers for MS Outlook '2000/2003"
http://www.contactgenie.com