Automation Error Library not registered
I'm actually very scared to ask this question because I suspect the answer will require hours of work for me.
I have an Access application that comes up with the message "Automation Error Library not registered" when I it gets to the command Set xlApp = CreateObject("Excel.Applic
I have MS Office 2003 loaded on my PC and all of MS Office 2007 except Excel 2007 (because it fouls up on a download from Lotus Notes that I need to do every week). I am running the application that fails on MS Access 2003. I have reference to Microsoft Excel 11.0 Object Library checked.
Does anyone have any suggestions as to what I may need to do to fix the problem?
I have an Access application that comes up with the message "Automation Error Library not registered" when I it gets to the command Set xlApp = CreateObject("Excel.Applic
I have MS Office 2003 loaded on my PC and all of MS Office 2007 except Excel 2007 (because it fouls up on a download from Lotus Notes that I need to do every week). I am running the application that fails on MS Access 2003. I have reference to Microsoft Excel 11.0 Object Library checked.
Does anyone have any suggestions as to what I may need to do to fix the problem?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ignore me!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all your comments. In response:
1 Tried Set xlApp = New Excel.Application problem persists
2 I tried late binding and that worked so I guess it solves my immediate problem, however why won't early binding work now when it did prior to installing 2007?
3. After having Office 2007 on the machine for 2 weeks and exploring a number of options to fix the Lotus Notes download problem I removed Office 2007 and re-installed, excluding Excel. I suspect this may have messed up the registry somehow - or is this just an amateur garbage opinion?
4. Tried Set xlApp = CreateObject("Excel.Applic
Because my immediate problem is fixed I am prepared to close but would welcome any further suggestions if you have any.
Rob
1 Tried Set xlApp = New Excel.Application problem persists
2 I tried late binding and that worked so I guess it solves my immediate problem, however why won't early binding work now when it did prior to installing 2007?
3. After having Office 2007 on the machine for 2 weeks and exploring a number of options to fix the Lotus Notes download problem I removed Office 2007 and re-installed, excluding Excel. I suspect this may have messed up the registry somehow - or is this just an amateur garbage opinion?
4. Tried Set xlApp = CreateObject("Excel.Applic
Because my immediate problem is fixed I am prepared to close but would welcome any further suggestions if you have any.
Rob
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the suggestions.
I will try to re-install Office 2003 AGAIN tomorrow to see if it helps.
I tried running the 'excel.exe /regserver' command. It did not fix the problem but now I am getting another error even earlier in my code - a part of the code that was working fine until I tried the 'excel.exe /regserver' command. Specifically when I run the following code on a Word document that I create: WordApp.Selection.Find.Rep
Again I suspect the problem is a messed up registry. Any more ideals. I now regret ever having installed 2007
I will try to re-install Office 2003 AGAIN tomorrow to see if it helps.
I tried running the 'excel.exe /regserver' command. It did not fix the problem but now I am getting another error even earlier in my code - a part of the code that was working fine until I tried the 'excel.exe /regserver' command. Specifically when I run the following code on a Word document that I create: WordApp.Selection.Find.Rep
Again I suspect the problem is a messed up registry. Any more ideals. I now regret ever having installed 2007
ASKER
Incidentally, I've tried removing and re-installing Office before and found it doesn't always clean out the old registry correctly. Is there a trick to it?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help. I think I have wasted everyone's time enough. I found a fix for the WordApp problem and the late binding suggestion fixed the Excel problem. I will leave it at that.
I really appreciate your help. I will close the question in the morning - my headache is now unbearable.
I really appreciate your help. I will close the question in the morning - my headache is now unbearable.
<I've tried removing and re-installing Office before and found it doesn't always clean out the old registry correctly.>
i think this true for office 97 and 2000.
microsoft has eraser tool for this.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;239938
there was nothing that came out for XP and 2003.
i think this true for office 97 and 2000.
microsoft has eraser tool for this.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;239938
there was nothing that came out for XP and 2003.
ASKER
Thanks for all your help on this one. I have a couple of urgent jobs to do today so I will re-install tomorrow. In the meantime at least it will work with late binding and I've fixed the Word problem so my application will at least work - its just my system that's not right. I will apportion points as fairly as I can because you all contributed.
Rob
Rob
in excel macro editor go to tools | References and look for "Microsoft excel object library" and tick the box.
Hopefully that's all it takes.