excel file error

[Philquad]

ive made a workaround by using office 2007 but curious as to why its so hard to use 2010 or 2013 excel with this file
macros ? yes



throws a compile error on me

have a go, let me know

[lsemmens]

I just tried in in 2010 with no issues. With 2010, can't recall 2007, your security settings in Excel will need to be adjusted to let you run macros. I have certain folders that are flagged as safe so xlsm files open without any issues but elsewhere, I must approve allowing macros to run.

FYI I do develop and use quite complex macros for some of my spreadsheets.

[joezep]

I just tried in Office pro plus 2013 with no issues, OS is Windows 10 . It might help to run repair from programs and features, just click on Microsoft office and click on the change tab.

[Philquad]

i give up
tried every security setting i could find

[lsemmens]

Incopatible with version, platform or architecture. We seem to have ruled out the version. What platform are you running it on? Don't tell us it's XP? 32 or 64bit?

[Philquad]

well, the orig file came from a xp 32 bit machine with office 07 on it
the new 1 is win 7\64 with office 2010 that had trouble, put 07 on it also for excel & that sorted it

but i just went 13, im running 10, yet i can only use it as a xls without macro's to not get the error.

how come yous can open it with no error?

[lsemmens]

Interesting, the only difference is that I am running W10. 64bit. I wonder if you did not include the VBA libraries when you installed Office 10, but I'm not sure that that is even possible. My next point of attention would be to try a repair. IIRC you can run a repair using the install media as you would with Windoze.

[Philquad]

i checked that, no go
it seems, im using office 2010, 2013 both 64bit
ms answers best idea. seems logical, was made in 2000 the file
hence it works with 03 or 07 i tried, both 32 bit
grabbing a variety of office 64 & 32 bit installs now for the future

[lsemmens]

Another thought, load the file, and then use the "Save As" and save it as a different name. Close Orifice down and try and open the "new" file. I've seen office throw a hissy fit with a file in the past (last century I think) and this, for no apparent reason, fixed it.