If the primary interop assembly is not installed in the global assembly
cache, Visual Studio generates an interop assembly for the project that
might not work fully in all cases. For more information, see Troubleshooting
in Office at Run Time.

http://msdn2.microsoft.com/library/6s0wczt9.aspx

--

Regards,

Tom Ogilvy



"overcanyon" wrote in message
oups.com...
Thanks for the reply Jim.

Fact is I've tried that. If any of the parameters is the problem it may
be the second one. I did revert to hard coding a range in here to see
what would happen and the line runs ok... but that's not the point
really... the app still falls over later on. So I think this is a red
herring and there is something more sinister or fundamental going on
here. For what it's worth, the preceeding line is:

rngData = xlApp.ActiveWorkbook.Sheets("Raw Data Sheet").UsedRange
'rngData having been declared as Excel.Range