Closed GoogleCodeExporter closed 8 years ago
Exact same issue. I'm using Excel 2003, D/Led and installed the toolkit, but
getting this error as well.
Original comment by dco...@gmail.com
on 11 Jan 2011 at 6:36
This may be missing the office toolkit, the office toolkit is required for the
connector to communicate with the salesforce API. Can you confirm that the
office toolkit is installed ?
Original comment by vneh...@gmail.com
on 25 Jan 2011 at 3:01
I'm having the same issue with Excel 2007 though I have installed the Office
Toolkit and double checked that it's installed, yet I get the error: "Compile
error in hidden module: AutoExec". My colleague with 2003 had no problems. Any
ideas how to fix this?
Original comment by miriamcd...@gmail.com
on 25 Jan 2011 at 4:24
I am having the same issue as well on Excel 2003. I do have the office toolkit
installed. When I installed the connector add-in, it came up with an error
about not being able to find the project/library, then asked for a password.
I tried going into add-ins and automation, re-activating connector and sforce
office, that did not change anything.
Original comment by sbark...@asatire.com
on 25 Feb 2011 at 5:13
I am also getting this issue. Any resolution?
Original comment by dexmo...@gmail.com
on 25 Mar 2011 at 5:02
It was working with excel 2007 a while back...but now its stopped working..and
I am getting the same error as above.
Original comment by vardhan....@gmail.com
on 4 Apr 2011 at 3:47
I'm having the same problem with Excel 2003.
Original comment by carolyn....@gmail.com
on 5 Apr 2011 at 8:10
Same issue here. I just re-installed office 2007 and add-in tab is not
appearing and I get the error on autoexec. I cannot fully remove the connection.
I will try to un-install connector, uninstall excel, and reinstall everything.
to note: the office connect did work after re-install without problem.
Original comment by vincent...@gmail.com
on 12 Apr 2011 at 5:57
Attachments:
Follow up: I reinstall office 2007 but no add-in tab appears. Since I am using
the SFDC connector and the connector used to work last week, I assume I have
everything setup right.
to make sure I have the macro settings to enable all macros and the developer
macro settings to trust access to the VBA project object model. I also have not
checked anything in the Add-ins trust center.
Is there an excel update I need to get?
thank you for your help, this tool is so important to me.
Original comment by vincent...@gmail.com
on 15 Apr 2011 at 6:40
Update: I did get a new computer (same model), redone from scratch, installed
office 07 and finally made the connector worked.
At this time i cannot say what setings was making the connector not work.
Original comment by vincent...@gmail.com
on 27 May 2011 at 9:32
I am going crazy here trying to figure out how I can make this connector work.
Same problem as explained above.
Original comment by aozt...@gmail.com
on 30 May 2011 at 5:58
Same problem with Excel 2007 on a brand new computer. I really need this tool.
Can someone please personally email me if they have a resolution:
ksadler1982@gmail.com
thanks!
Original comment by ksadler1...@gmail.com
on 3 Jun 2011 at 3:02
Can someone provide an answer here. I have same problem on new Win 7/Office
2007 machine. New install of Connect for Office which is working fine. Excel
connector can find the connect for office
Original comment by mark.mil...@gmail.com
on 19 Aug 2011 at 10:32
I have only gotten this error when SForce_Office_Toolkit is not installed.
Does uninstal, reboot, and then reinstall help?
Original comment by Christop...@gmail.com
on 3 Oct 2011 at 9:04
Just installed Service Pack 3 for MS Office 2003 and it resolved the issue for
me. In other words, make sure you update your MS Office installation with the
latest service pack.
Original comment by stianbra...@gmail.com
on 23 Mar 2012 at 9:43
Woopie, Service Pack 3 solves the Excel 2003 on 64-bit Win7 issue THANKS!!!
Original comment by datadril...@gmail.com
on 13 Apr 2012 at 9:53
thanks for the note on service pack 3
Original comment by vneh...@gmail.com
on 28 Jan 2013 at 5:12
Original issue reported on code.google.com by
craig.he...@gmail.com
on 4 Jan 2011 at 6:36