Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / General MS InfoPath Questions / October 2007

Tip: Looking for answers? Try searching our database.

InfoPath (2007) cannot add the event handler

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Rolf - 26 Feb 2007 17:19 GMT
I have a problem that I have been working on for days. Using InfoPath and the
programming interface, I get following error when I click an any event:

InfoPath cannot add the event handler .

To work with Visual Basic or C# code, Microsoft Visual Studio Tools for
Applications (VSTA) is required. The Microsft .Net Framework2.0 and Microsoft
Core XML 6.0 must be installed prior to installing VSTA

I have .Net 2005 installed SDK 2.0 installed, InfoPath 2007 and VSTO
installed (also have xml parser 6.0  installed). I have uninstalled and
re-installed all of the above, but still get the same error. I even tried to
update the Office 2007 configuration using the control pannel, change program.

Please can anybody help or guide me in right direction???? Thank you.
S.Y.M. Wong-A-Ton - 27 Feb 2007 23:44 GMT
I've never received this error, so cannot be of much help to you. Others
have, though, so you can try this link:
http://spsfactory.blogspot.com/2007/01/vstavsto-problem-when-installing-office_1
0.html

---
S.Y.M. Wong-A-Ton

> I have a problem that I have been working on for days. Using InfoPath and the
> programming interface, I get following error when I click an any event:
[quoted text clipped - 11 lines]
>
> Please can anybody help or guide me in right direction???? Thank you.
Andrei Gavrila - 04 Oct 2007 16:11 GMT
Hi Rolf,

Today I had the same problem and apparently there can be 2 reasons. One documented by microsoft : Your project path is too long (longer than 127 characters).

The other - Forms that end in numbers (version numbers) can cause bugs because of the way they name the VSTA projects. MyFormv1 will name the VSTA projects in the following order : MyFormv1, MyFormv11, MyFormv12, MyFormv13 (if you decide to create and remove code). If you already have a form MyFormv13 it is obvious that the pair of names (form names and project names) is going to cause a bug.

My recomendation: change the name of the form

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Andrei Gavrila - 04 Oct 2007 16:11 GMT
Hi Rolf,

Today I had the same problem and apparently there can be 2 reasons. One documented by microsoft : Your project path is too long (longer than 127 characters).

The other - Forms that end in numbers (version numbers) can cause bugs because of the way they name the VSTA projects. MyFormv1 will name the VSTA projects in the following order : MyFormv1, MyFormv11, MyFormv12, MyFormv13 (if you decide to create and remove code). If you already have a form MyFormv13 it is obvious that the pair of names (form names and project names) is going to cause a bug.

My recomendation: change the name of the form

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.