MaratYa

I installed in this order:

Visual Studio 2005 pro

Office 2007 pro

VSTO 2005 SE

VSTO 2005

Office 2003 pro

uninstalled office 2007

When I start a new Office project from VS2005, I get:

"Cannot find a required object for Microsoft Office 2003. Run setup and repair Office 2003 to fix the problem."

Strange, but that didn't "fix the problem".

I searched the WWW and found only questions about this error (since 2005), but no answers.

I installed all prerequisites, and followed all recommendations, repaired and/or reinstalled Office2003, VSTO, PIA 2003, etc.

(I also read the message from Mike on 7/27/2005 recommending to reinstall PIA 2003.)

Nothing helphs.

Does anyone knows what causes this

Thank you much in advance!

Marat.



Re: Visual Studio Tools for Office VSTO 2005: "Cannot find a required object for Microsoft Office 2003".

Cindy Meister

Seems an odd you chose in which to install. And I'm surprised VSTO 2005 (not the SE) did install at all without Office 2003 Pro present, as it can only work with Office 2003 at design time.

Which kind of Office project are you trying to create An Add-in or a document-level customization

I'd try uninstalling Office as well as VSTO 2005 (both editions). Then install Office 2003 Pro (use the "custom" type of setup to make sure the PIAs are installing - that would the entries under each application for ".NET programmability support". and then try installing VSTO 2005 again. If 2003 is already present that might break the dam...






Re: Visual Studio Tools for Office VSTO 2005: "Cannot find a required object for Microsoft Office 2003".

MaratYa

I first bought the Office 2007 and installed the VSTO 2005 SE. 每 I should have done my research better.

I need the flexibility to do both - the addins and the document level apps (templates, workbooks).

I realized (too late) that the capabilities I was expecting to obtain (while reading the books on the VSTO) are not for Office 2007 addins. Host controls are just not there.

In addition, my app also has to manage the data access security. (read: ※be responsible for§, ※control all actions§, ※keep track of§, etc). It is like sitting in the manager*s chair, while all I want is to be on the assembly line.

With Addins, I get ※more control§ over the whole process and the opening closing the docs etc. But I want ※less control§ 每 the security of connecting to data ought to be handled by the System security administrator, not by my app. I want to handle only the errors of connection if they happen, and shift the responsibility away from a particular solution. Issues of connection need not be my apps headaches, in other words. At least at this stage, when .NET is still fresh to me.

I also need to be able to just copy ※the whole opus§ on a CD/DVD and mail it to someone; both, with supporting data there and with an option of data sources by XML feed. One can*t do that with add-ins.

At the same time, I have to continue working with my Office 2003 integrated apps (Access&Word&Excel), because our company*s users are staying put on the Office 2003 using (among other things) my apps. We will continue to add to them in Office 2003. This will be so until the whole office decides to move to 2007 每 and that is a different budget item, including training.

So, I uninstalled Office 2003. Tried to open a 2003 XLS files in Excell 2007, MDB files in 2007. Worked fine.

I then installed VSTO 每 I was expecting it to work with Office 2007 with MDB, XLS. So I would produce apps for both 2003 and 2007 with only 2007 office and VSTO, not Office 2003.

Ha-ha. That was naive - didn*t work in VSTO. While the two Offices can coexist side by side (※as advertized§), VSTO solutions cannot work for 2003 format using office 2007 engines or any other way. The purchase of 2007 Office for me it seems, was premature.

To be able to continue development in 2003 I had to uninstall Office 2007.

I then realized, that I can ※have it my way§ by installing the Virtual PC and on it the whole thing about 2007 Office PRO and VSTO 2005 SE. I understand from decumentation (yet to test) it is possible to connect simultaneously to the same physical data source (Access,SQL,Excel) from VSTO app on my pc and from VSTO SE Addin app on the Virtual PC on the same CPU. Provided I get enough memory of course. Will be slow too, I suspect.

I am on the first step of that plan:

1. Install the invironment for Office 2003 Pro with VSTO on my PC.

2. Install Virtual PC

3. On virtual PC install

Visual Studio

Office 2007 Pro

VSTO 2005 SE

3. Connect to data servers on my PC using network connection from Virtual PC to ※physical§ on the same CPU.

Will this will work Will this be a stable environment to develop Otherwise, it*s a choice 2003/2007, but not both, until VSTO 2007.

I am implementing your suggestion 每 of course your advise sounds right 每 it*s the sequence of events, that did it.

Thank you so much for your help, Cindy (and for your excellent code samples too!)

Marat.





Re: Visual Studio Tools for Office VSTO 2005: "Cannot find a required object for Microsoft Office 2003".

MaratYa

At least something changed after all this reinstalling - but it is not working yet.

The message got MUCH longer. Here is the whole message:

Project cannot be started because the application add-in is not working correctly and might have been disabled. To check for disabled items in the Microsoft Office applications, open the Help menu, click About Microsoft Office Word or About Office Excel, and then click Disabled Items. If either ※Word Visual Studio Design Time Adaptor Add-in§ or ※Excel Visual Studio Design Time Adaptor Add-in§ appears, select it and click Enable. If not, reinstall or repair your installation of Visual Tools for Office.

I checked in the helps of all Office apps as message recommends - nothing was disabled there.

I reinstalled/repaired Visual Tools for Office (also suggested by the message). Did not help, same long message popping up when creating a VSTO Excel or Word project. Interestingly, the outlook project created fine.

Next (editing the original message), I searched this forum and found the answers about the registry values of for the designtimeadaptor key to be set to 3.

Unfortunately, the values were correct in my registry for both Word and Excel.

Still, I can't create the VSTO Excel or Word project.

Any suggestions

Thank you,

Marat.





Re: Visual Studio Tools for Office VSTO 2005: "Cannot find a required object for Microsoft Office 2003".

Cindy Meister

Hi Marat

I'm afraid I can't help any further with the main problem/question in your other post. But someone should be along in a day or two who can make further suggestions. The additional information you were able to provide in that message should help them lead you to other steps. To the following, however, I can contribute a remark.

<<I then realized, that I can ※have it my way§ by installing the Virtual PC and on it the whole thing about 2007 Office PRO and VSTO 2005 SE. I understand from decumentation (yet to test) it is possible to connect simultaneously to the same physical data source (Access,SQL,Excel) from VSTO app on my pc and from VSTO SE Addin app on the Virtual PC on the same CPU. Provided I get enough memory of course. Will be slow too, I suspect.>>

I use VMWare, not VPC, so I can't give you any exact measurements, but yes, if the VPC and the host machine are able to communicate, this will work. I have a similar set up on my dev machine (with VMWare) and they can share printers as well as datasources and files. Since the installations are HUGE and the currently installed version of VMWare doesn't grant that much space or memory, the virtual machine tends to be slow. And Windows security on a peer-to-peer basis can make file access a bit slow. But it does function :-)

I hope that soon someone will be able to assist you with getting the configuration problem cleared up.






Re: Visual Studio Tools for Office VSTO 2005: "Cannot find a required object for Microsoft Office 2003".

MaratYa

Cindy,

Just to close the issue, this problem has been resolved.

The answer came from the Microsoft support engineers. (I called the support line)

Although it took some time to be discovered - it's behind us, finally.

Read about it here:

http://forums.microsoft.com/MSDN/ShowPost.aspx postid=1823384&siteid=1

Thank you for your help,

Marat.