Class does not support automation

Hey everyone,

A coworker is having an issue with a complex macro she was instructed to use for the first time and the creator of the macro is no longer with the company.

The error message is: "Class does not support automation..."

The debugger is highlighting Set Recordset = New ADODB.Recordset
MacroError.JPG

Yeah I just walked over there and checked that.
She is running Windows XP but Microsoft ActiveX Data Objects Recordset 2.8 Library is already checked.

It's the Microsoft Active Data Objects x.x Library I believe, rather than Microsoft ActiveX Data Objects Recordset 2.8 Library

Though the dodgy use of variable names would be my prime suspect

Both Libraries are checked in the references.

I know this is the first time she has run the macro, so it could be as simple as the import/export data could be in the wrong format right?

Is there an easy way to debug this thing? My macro knowledge is very minimal but I am familiar with the step through funcitonality.

In reference to my earlier post, the first thing I'd do is change the variable name Recordset to something else, you shouldn't use resevered words, functions, types etc as variable names - it's asking for trouble

Oh and I am looking in to the DLL update, although I do not think the macro was created in a Win7 environment.

Originally Posted by Kyle123

In reference to my earlier post, the first thing I'd do is change the variable name Recordset to something else, you shouldn't use resevered words, functions, types etc as variable names - it's asking for trouble

Do you think that could be the issue if it has worked in the passt with the dodgy naming conventions?

So I ran it on my computer (with win 7) and it ran fine. o_O

OP, I have encountered the same problem at my workplace when working with Windows XP/Windows 7 and the Active X references.
For me, if there is no bug in the code, I have been able to fix the issue just by putting a comment in each of the modules and then saving it on the Windows XP machine.
I guess if you change the code, even if it is a comment, then save it, it does something haha.
Hope that fixes your issue.

Oh and also, make sure that your recordset isnt empty.

Please Login or Register  to view this content.

Yeah I think it is the DLL issue, and I will see if she has to use it in the future, if so I will look at more DLLs and/or use Jason's approach of changing it slightly.

Thanks