What was there any other error aside from the generic "have to shut down
etc........."?
Have you tried runing Scanpst on your PST file that you're using to see if
there are any issues reported? (sounds like it's having a structural issue
with the PST file because if it was simply a data issue, you're generally
just get a MAPI faliure message). Having said that, would be a good idea to
make sure that there are no obscure data issues inside this particular
batch. Quickest way to do that is try and import this file on another
machine if you can (really doesn't matter what version of Outlook you use
for this particular exercise if it's in the Outlook 2000 family).
Also, does the same issue exist if you save the file in CSV format and
import that versus Excel in the off chance you have a corrupt Excel file?
(and yes we've run across that too - nothing is visibly wrong when you open
the file but the named ranges do not report correctly when pulling the named
range info programmatically). This would be the easiest and quickest thing
to try right off the bat.
If the problem still exists after the above items - create a brand new PST
file and import to that to ensure there are no issues remaining with your
original PST file.
Failing all of the above - do a complete re-install of Office but my guess
is that the problem will show itself in one of the items mentioned.
Karl

Signature
__________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0
"Power contact importers for MS Outlook '2000/2003"
http://www.contactgenie.com
> Win XP/ Office pro 2003
>
[quoted text clipped - 26 lines]
> any suggestions/assistance will be more than appreciated! :-)
> Judy