Got a custom .XLA called "Function.xla" (Lousy name... but I didn't choose
it...)

It contains code to compute rolling rates of return.

It's been working fine for all users for years and years.

Now one user is having a problem.

The problem presents as the "ROR" calculation showing up as a fully-qualified
path and an error message that pops when they try to invoke the computation. The
error message is to the effect that there's already a copy of Function.xla open
and Excel is trying to open another copy.

Same thing's happening in an MS Access app on that user's PC - that is creating
Excel spreadsheets. I coded around the error in the MS Access app by just
doing a Resume Next if/when that error popped.


Anybody got an idea what the root cause is?

I'm thinking something to do with multiple copies of the .XLA on this user's
computer coupled with some Excel parm that points to a default folder for
opening such things.... Plus, maybe, some explicit reference in the Excel
spreadsheets to a different folder.
--
PeteCresswell

Does this addin only have UDFs?

If yes, it sounds like there's a mismatch between the location in the formulas
and where the addin is loaded (tools|addins -- or the xlstart folder).

=if(a1=123,'C:\My Documents\excel\function.xla'!ror(something),"")

I'd keep one addin in a single location.

Then you have a couple of choices.

#1. move the addin to the place that the the formula expects.

#2. Fix the formulas
Edit|Links|Change source.

======
This can be a problem when sharing an addin with people and letting them put the
addin in any location--and then sharing a workbook that relies on a function in
that addin.

If you save your addin in one location, the formulas will still try to find them
in that location. The fix I use is to either store the addin in a common
network location and use the UNC path--not a mapped drive where the letter can
change.

Or dedicate a common location and force(?) people to use that location:
C:\MyAddins

And then the formulas will always point to C:\myaddins\function.xla!ror().



"(PeteCresswell)" wrote:

Got a custom .XLA called "Function.xla" (Lousy name... but I didn't choose
it...)

It contains code to compute rolling rates of return.

It's been working fine for all users for years and years.

Now one user is having a problem.

The problem presents as the "ROR" calculation showing up as a fully-qualified
path and an error message that pops when they try to invoke the computation. The
error message is to the effect that there's already a copy of Function.xla open
and Excel is trying to open another copy.

Same thing's happening in an MS Access app on that user's PC - that is creating
Excel spreadsheets. I coded around the error in the MS Access app by just
doing a Resume Next if/when that error popped.

Anybody got an idea what the root cause is?

I'm thinking something to do with multiple copies of the .XLA on this user's
computer coupled with some Excel parm that points to a default folder for
opening such things.... Plus, maybe, some explicit reference in the Excel
spreadsheets to a different folder.
--
PeteCresswell

--

Dave Peterson