Read all the way through the following link ... may be helpful ...

http://blogs.msdn.com/eric_carter/ar...06/225989.aspx


And then, embedded in the following is a small section on VALUE2 ...

http://msdn2.microsoft.com/en-us/lib...ffice.11).aspx

And the summary from the above article:

Summary
Microsoft Office Word and Microsoft Office Excel expose rich programming
models, but those object models were originally written to be consumed
by VBA clients. Visual Basic .NET, even with Option Strict On, can
handle most of the requirements of the Office object models. Consuming
those object models with C# requires a bit more care. When writing
applications using Visual Studio Tools for the Microsoft Office System
and C#, keep in mind that you'll often need to make concessions to the
differences between the languages, watching for optional parameters,
parameterized properties, Variants, and late binding. Once you
internalize the types of issues you'll face, writing C# code that
interacts with Office becomes no more difficult than writing Visual
Basic .NET code.


Good luck ...

JimP

*** Sent via Developersdex http://www.developersdex.com ***