Huh? What solution did Bob post?



The solution I posted works with xls and xlsm files, just not xlsx files...

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Sorry not bob it was you. If you create an xlsx and you apply the VB as soon as you exit and go back into it you haven't got the code anymore (because its now a xlsx) and so the calculations don't work - unless Im missing something?

Again apologies for the confusion I really should read what I write

Right, it was macropod's solution. But Paul, I don't see why you told him it would work with .xlsx files. Your solution is a user-written function, which by definition (right?) means it has to be stored in an .xlsm. Now, I'm all for that; these days I sometimes store a new workbook as .xlsm even though I haven't yet written or imagined any code for it, just because experience leads me to believe I will sooner or later. But how would your macro work with an .xlsx?

And shabbaranks, if you really can't use .xlsm, why not store it as an .xls? That'll allow embedded VBA.

If you two would take the time to read my replies, you just might save yourselves some confusion and me some time!
Now, compare what I wrote against your posts...

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Oops. I read it, I just read it too fast and wrong; I thought you wrote "...works with xls and xlsm files, not just xlsx files". My bad.

I also read it wrong....

__________________
Using O365 v2503 - Did you know you can thank someone who helped you? Click on the tiny scale in the right upper hand corner of your helper's post

That is what I wrote...

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Not unless you changed it later. I thought you wrote "...not just .xlsx files"; what appears there now is "...just not .xlsx files". I'm glad I'm not the only one whose eyes found it easy to reverse the two words.