ODMA Error opening Excel97

[VOSS1]

I am running GroupWise v5.5 and office97: When I open Excel I get an error stating GroupWise ODMA integration, unable to load resource library. I have deleted the odma32.dll, and turned off document integration in GroupWise but still this error shows up every time I open excel. Any help would be greatly appreciated.

 

[xlhelp]

Rename gwodm132.dll and see what happens I don't particularly care about apathy

 

[VOSS1]

Well that got rid of the ODMA error now when I run excel it tries to debug saying it is looking for the gwodm132.dll.

 

[xlhelp]

You need to look for the macro it is accessing and get rid of it by going to File, Remove Module. If you click on Debug, it will tell you what the name of the macro is. You may need to start up Excel again, then go to Tools, Macro, Visual Basic Editor and look for the macro or the Module that contains the macro.

Then go to File and choose Remove Module. And say No to the prompt. I don't particularly care about apathy

 

[VOSS1]

I will try this tomorrow and let you know, thank you for the help. I was just wondering do you think that the info could be tucked away in an INI file?

 

[dbsub9]

I've run into this before and found that deleting ODMA32 in the registry made the message go away. I can't remember the exact key but if you do a search within regedit it will come up. It is found somewhere like HKLM\Software\Novell\Groupwise\ODMA32. Delete the entire ODMA32 directory and office will no longer bug you. If, however, in word or other apps the message continues to pop up when you select File --> Save As then you will have to rename odma32.dll found in the /system folder under windows or winnt, etc..
Also, if you do a more verbose install and uncheck the integrations from the office apps this problem should not come up.
I've never had any complaints of lost functionality using this method.

 

[dbsub9]

I just wanted to add that although you got rid of this error already by renaming gwodm132.dll you still received errors. Try renaming as a last resort and see what happens.

 

[VOSS1]

I already renamed the odma32.dll and that fixed the first part of the error which was in Word, but this still let the Excel issue. I just read something about removing the gwxl97.xla which is the macro causing all the fuss. If that doesn’t work I will try the verbose install and elect to not have integration. I will post when finished for anyone else who may need this post.