I have a library of vba utils I use for daily utility (splitting multiline cells into arrays, range based concatenation, blank removal, etc). I've got these as an add-in module and that is fine for personal use. In a team though, unless everyone has the add in enabled it doesn't work - which is annoying but normal. For a particaular project, to make it portable, I have copied the module into the workbook in question. However, it isn't working as I hoped
When opened on another computer I find the UDF references (some, not all) still point to a local path for the addin - which is not the same for all users, therefore not working. When opened on the other computer you get a formula containing a "path\workbookFileName!"FUNCTION(params) rather than just the function name, and the workbook is maintaining links. Is there a way to force the formuae to reference the embedded module rather than the add in? What is the order of presidence when a UDF name is in both an add-in module and the workbook module?
I've had similar annoyances when people have an addin installed in a different path to me - it's not visible when you write that it embeds the xlam path into the function call in the formula bar. if it was only the function name i believe it would locally resolve for users but I cannot figure how to do this.
I have a suspicion the problems may be udf calls I wrote before I copied the module in, and the newer udf calls are using the local calls. However, there is no real way to check. Sorry I don't have many samples to share since I've already gone through and rebuild half the spreadsheet to remove all external links (after disabling the add in temporarily). I also note that I've had no issues in the vba code calling these functions - probably because I qualified the name always to the local module name and did not reference a dependency.
When opened on another computer I find the UDF references (some, not all) still point to a local path for the addin - which is not the same for all users, therefore not working. When opened on the other computer you get a formula containing a "path\workbookFileName!"FUNCTION(params) rather than just the function name, and the workbook is maintaining links. Is there a way to force the formuae to reference the embedded module rather than the add in? What is the order of presidence when a UDF name is in both an add-in module and the workbook module?
I've had similar annoyances when people have an addin installed in a different path to me - it's not visible when you write that it embeds the xlam path into the function call in the formula bar. if it was only the function name i believe it would locally resolve for users but I cannot figure how to do this.
I have a suspicion the problems may be udf calls I wrote before I copied the module in, and the newer udf calls are using the local calls. However, there is no real way to check. Sorry I don't have many samples to share since I've already gone through and rebuild half the spreadsheet to remove all external links (after disabling the add in temporarily). I also note that I've had no issues in the vba code calling these functions - probably because I qualified the name always to the local module name and did not reference a dependency.
