PC Review


Reply
Thread Tools Rate Thread

Confused About Which Excel Reference to Use

 
 
TC
Guest
Posts: n/a
 
      15th Feb 2007
My project has a reference to the Excel 9.0 Object Library. My
understanding is that, by using a reference to 9.0, I make my
application compatible with Excel 2000, 2002, and 2003. If I use a
reference to 11.0, however, then my application is compatible only
with Excel 2003. Is that correct?

I've found that, as long as I use a reference to Excel 9.0, I get a
warning which says "There are updated custom wrappers available for
the following referenced components: Excel ,VBIDE.". The only way I
can make that warning go away is to change the reference from 9.0 to
11.0. In other words, Visual Studio is encouraging me to use 11.0,
even though 9.0 is the better choice for compatibility. Is this a
glitch in Visual Studio, or is there something going on that I don't
understand?


-TC

 
Reply With Quote
 
 
 
 
RobinS
Guest
Posts: n/a
 
      15th Feb 2007
What are you doing with Excel? If you are creating spreadsheets, you want
to use Excel 9.0, because anything you create with that version will be
readable by 10 and 11, but not vice versa. If you are reading
spreadsheets, you want to use 11.0, because it can read most anything in an
earlier version.

If it's just a warning, you can ignore it and your project will still
compile and work.

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------
"TC" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> My project has a reference to the Excel 9.0 Object Library. My
> understanding is that, by using a reference to 9.0, I make my
> application compatible with Excel 2000, 2002, and 2003. If I use a
> reference to 11.0, however, then my application is compatible only
> with Excel 2003. Is that correct?
>
> I've found that, as long as I use a reference to Excel 9.0, I get a
> warning which says "There are updated custom wrappers available for
> the following referenced components: Excel ,VBIDE.". The only way I
> can make that warning go away is to change the reference from 9.0 to
> 11.0. In other words, Visual Studio is encouraging me to use 11.0,
> even though 9.0 is the better choice for compatibility. Is this a
> glitch in Visual Studio, or is there something going on that I don't
> understand?
>
>
> -TC
>



 
Reply With Quote
 
TC
Guest
Posts: n/a
 
      20th Feb 2007
On Feb 15, 3:55 pm, "RobinS" <Rob...@NoSpam.yah.none> wrote:
> What are you doing with Excel? If you are creating spreadsheets, you want
> to use Excel 9.0, because anything you create with that version will be
> readable by 10 and 11, but not vice versa. If you are reading
> spreadsheets, you want to use 11.0, because it can read most anything in an
> earlier version.
>
> If it's just a warning, you can ignore it and your project will still
> compile and work.
>
> Robin S.
> Ts'i mahnu uterna ot twan ot geifur hingts uto.



Robin,

You're right. I hadn't realized that, for people who are reading
spreadsheets, 11.0 is more appropriate. In any case, I'm writing
spreadsheets. I know I can ignore the warning, but I find it annoying
nevertheless. If Visual Studio is going to raise warnings about
perfectly legitimate code, then it should give us a way to dismiss
those warnings.

-TC

 
Reply With Quote
 
RobinS
Guest
Posts: n/a
 
      20th Feb 2007

"TC" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Feb 15, 3:55 pm, "RobinS" <Rob...@NoSpam.yah.none> wrote:
>> What are you doing with Excel? If you are creating spreadsheets, you
>> want
>> to use Excel 9.0, because anything you create with that version will be
>> readable by 10 and 11, but not vice versa. If you are reading
>> spreadsheets, you want to use 11.0, because it can read most anything in
>> an
>> earlier version.
>>
>> If it's just a warning, you can ignore it and your project will still
>> compile and work.
>>
>> Robin S.
>> Ts'i mahnu uterna ot twan ot geifur hingts uto.

>
>
> Robin,
>
> You're right. I hadn't realized that, for people who are reading
> spreadsheets, 11.0 is more appropriate. In any case, I'm writing
> spreadsheets. I know I can ignore the warning, but I find it annoying
> nevertheless. If Visual Studio is going to raise warnings about
> perfectly legitimate code, then it should give us a way to dismiss
> those warnings.
>
> -TC
>


There *is* a way to dismiss some errors or warnings. You can look in the
list displayed on the Compile tab of the project settings. In the middle
are some conditions that you can turn off as warnings.

There's another list under Debug/Exceptions, and hopefully it's in there
somewhere.

Good luck.
Robin S.



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
slightly confused - object reference PBcorn Microsoft Excel Programming 1 27th Sep 2008 09:18 AM
Excel is Confused shep Microsoft Access 2 5th Jul 2008 12:44 AM
Creating reference fields and pulling the reference from Excel =?Utf-8?B?Qm9iIEhheWVz?= Microsoft Word Document Management 0 19th Sep 2007 02:12 PM
confused about null reference compile error Steve Richter Microsoft ASP .NET 4 26th Apr 2005 06:30 PM
How to remove missing reference and add reference for different Excel versions =?Utf-8?B?bHV2Z3JlZW4=?= Microsoft Excel Programming 2 15th Mar 2004 08:46 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 07:14 AM.