Run Time 91 error on my computer, but not coworkers

[Apples52]

Hi,

I am using a template a coworker created that has a macro to clear the sheet, which works fine, and a second macro to run which copies data to another tab, which is not working for me. The macro runs as intended on my coworkers computer, but does not on my computer. I am getting a "Run time error 91: Object variable or with block variable not set" error. I've gone down a google rabbit hole trying to figure this out with no success. We are both on a windows computer using office suite 2019. See screenshot of the debug below. How can I fix this?

 

[Anfinsen]

Hello,
On your coworkers PC, from Visual Basic, click Tools, and then References, you will see a window that looks something like this.

Then go to your PC, and see if you have the same references checked "on". this might not be the problem, but it is the first place I would think to check.

 

[MARK858]

Look at the Find settings on both PC's, do they match? in particular look at Match entire cell contents

 

[Apples52]

Hello,
On your coworkers PC, from Visual Basic, click Tools, and then References, you will see a window that looks something like this.

View attachment 99266
Then go to your PC, and see if you have the same references checked "on". this might not be the problem, but it is the first place I would think to check.

I just compared our references and they are the same- thank you for the suggestion. The only thing I checked from a google search before posting was opening DCOMCnfg.exe and checking that local and remote access was set to allow for "everyone" (it was).

Quite frustrating and puzzling to me. I have about 50 other workbooks I regularly use that run macros fine on my machine and theirs- just don't understand why this one would be any different.

 

[Apples52]

Look at the Find settings on both PC's, do they match? in particular look at Match entire cell contents

Are you referring to the settings in the "Find and Replace" box? The one you open up by ctrl +F? Settings are the same there, but I'm also not searchign for something, so not quite sure how that would impact or relate to me running the macro. Unless I'm misunderstanding something?

 

[Apples52]

Closing the loop on this specific case. Turned out to be me running an older version of excel (2019). Had never been an issue with any other excel files until this one. Changed my settings to use the office 365 account I didnt' realize I hadn't been using and now its running as expected. Just wish I had thought of that about 12 working hours ago. Thanks all for your willingness to help.

 

[MARK858]

I seriously doubt that it was erring out because you were using 2019, more likely that your settings are different in the newer version.
It is often an issue when using Find as Find retains a memory on most of it's settings and so not setting the parameters in the code risks having issues.

In particular I suspect that the line needs to be

 Set FoundCell = FindRange.Find("x*x", LookIn:=xlValues, LookAt:=xlPart)

I have removed the Offset(0, 0) as an offset of 0 rows and 0 columns does nothing