It's easier to develop.
But, if data is big:
this is slower - to import it. QTP uses Excel automation inside of this process and , as we know, Excel is complicated object. That's why it's faster to transfer one line into INI and then read one or several Key's Values as needed.
Couple of trick about Import\Export Excel:
1. You have to be sure, that no eny instance of Excel is opened at running time. Otherwise, procedure will give runTime error. (How to be sure?... I use the code, to check out, and kill this Excel object if present by stopping the Process...)
2. If you have predeveloped Macro codes in the Excel file (I've written some in VBA, just because it's more reliable then in VBscript, in order to invoke that MacroCode later from Excel object directly) -
this codes were wiped out after Import\Export executed by QTP.
3. Nothing, but pure data as allowed in Import\Export functions. Meaning: the same situation as with Macro - if you have predefined decorations or some calculations or images in the predeveloped ExcelTemplate - all of them will be gone after Import\Export.
But, in another hand:
If you are dealing with pure data -
using Import\Export from QTP - is faster,
then using ExcelObject as automation...
INI manipulation - is fastest...