Re: VSTO Excel Lab - DebtConsolidation
- From: "Norm Estabrook [MSFT]" <normesta@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 1 May 2006 16:41:15 -0700
Hello,
Another user posted this exact issue in the VSTO public forum. The response
given to that user was "As you make changes to your toolbars, Excel keeps
track of the changes in a file called Excelnn.xlb. (The name of the file can
vary depending on your version of Excel, but will always end in the .xlb
filename extension. For instance, in Excel 2002 the file is called
Excel10.xlb and in Excel 2003 it is Excel11.xlb.) The contents of the file
are updated whenever you quit your Excel session.
When we host Excel in Visual Studio, we merge the Excel and Visual Studio
menus. If you are missing the Excel Data menus from the Visual Studio menus,
it could be because your Excel11.xlb file is corrupt. You could backup this
file, then delete it. Excel will then recreate it - and this should fix the
corruption.
You can find this file in a subfolder of your profile, typically
%homepath%\Application Data\Microsoft\Excel\"."
You can read the entire thread at
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=212844&SiteID=1. Hope
that helps!
~Norm Estabrook
"dmon" <dmon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14BB3773-B212-4942-98D3-A1B1FE6FD822@xxxxxxxxxxxxxxxx
As I am following the VSTO DebtConsolidation tutorial I can not get past:
Section -
To bind an Excel ListObject to the data source
Step 6. -
On the Data menu, point to Microsoft Office Excel Data, point to List, and
then click Create List. The Create List dialog box appears.
When I select the "Data" menu "Microsoft Office Excel Data" displays with
an
arrow but it will not expand, ergo, nogo...
I had a similar problem in the earlier example in the tutorial but I do
not
know how to solve it.
.
- Prev by Date: Web Systems Analyst-Permanent Position-Mt. Laurel, NJ
- Next by Date: The annoying VSTO 2003 message "The current .NET security policy does not permit....."
- Previous by thread: Web Systems Analyst-Permanent Position-Mt. Laurel, NJ
- Next by thread: The annoying VSTO 2003 message "The current .NET security policy does not permit....."
- Index(es):
Relevant Pages
|
Loading
