If we try to insert a part to an existing or empty assembly,
we lose functionality of Microsoft Outlook and none of our
shortcuts work for Microsoft Access or Word. We upgraded from
Office 2003 to 2007 hoping this would fix the problem but it
didn't. Any suggestions?
Thanks
Derek
Thanks
Derek
No problems here.
Vista64 Business
Office 2003
Must be nice. When we try to insert a part to a new or existing assembly, our MS Office programs quit working. Same setup as you and we upgraded a couple of machines to MS Office 2007. Same results. To fix we have to logoff/login (a little quicker than a reboot). We don't know what else to try. We have contacted our VAR and they said SW and MS are aware of the problem. Crazy thing about this is that 3 of our sister companies don't have any of these issues and they have the same setup as us.
Derek
"We have contacted our VAR and they said SW and MS are aware of the problem."
Have you requested an SPR Number?
Yes, a SPR Number was assigned.
Derek
i have the same problem but it is whenever, not during a specific operation. outlook, word, excel, powerpoint will quit working when i have solidworks open. they work fine if i don't have it loaded. i am under the assumption that it has to do with solidworks not dumping files that you have closed and office programs running out of memory. i have tried almost everything and my var said nothing other than that i was the ONLY one with this problem.
i am running vista 64bit, solidworks 2009 sp3, ms office 2007
That interesting...it's only happened to us when in an assembly. It doesn't matter if you drag/drop, insert component or use the design library. I noticed yesterday that just by creating a new assembly, because the insert command is already started, hoses our MS Office. We just bought these new workstations and haven't been able to benefit from them yet...frustrating!
I doubt they know where the solidworks forums are even at.
Bummer...this really is strange. I'm trying to uninstall/reinstall and am having problems with that too. We've been using SW since 2001 and getting pretty discoured. No fixes, work-arounds or ... from SW. Even a message/bulletin saying they are aware of the problem and they are working on it would be nice!
Derek
Anybody tried?
After some testing we've found that if we don't open a MS Access database via a shortcut everything behaves as it should. So for now we start MS Access and use the File>>Open...
Good luck to you...hopefully this will get fixed soon!
Refer to this thread about the issue.
http://forum.solidworks.com/fo...tid=14&threadid=21213
Cheers,