I code without a .NET, so I can't tell you.
Look at this link:
http://www.dicks-blog.com/archives/2...rt-classic-vb/

Stephen Bullen is the author. In the responses, look at item #8 also
written by Stephen.

This may give you a clearer pictu

http://msdn.microsoft.com/office/arc...ych2_part1.asp

--
Regards,
Tom Ogilvy



"overcanyon" wrote in message
ups.com...
Tom, I have looked at the link you suggested. The instructions for
installing the primary interop assembly (and the article in general)
appears to be aimed at Excel 2003. (I tried but was not given the
option for .NET Programmability Support)

Are primary interop assemblies available for Excel 2000? I've seen much
reference to PIAs but this always seem to refer to later (than 2000)
versions of Excel. Is there a separate remedy for this version?

Thanks.

Tom Ogilvy wrote:

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