Hello, first-time caller here. A lifetime ago I wrote assembler, C, and C++ but was not a VB developer. Being a small business owner now (and with Covid19 giving me downtime) I thought I'd try to automate a few things and found my way to VBA and macros.
I've cobbled together a function that I will use literally hundreds of times - it simply sums numbers below itself while the background color is that same as it's own. It also draws borders around the column of cells as a visual confirmation of how it worked.
I put my VBA function, =sltcSumColor(), into an otherwise empty spreadsheet, put it on a common drive, and then pointed to it in the File|Options|Add-ins section. That all worked, until I had another user test it...
it turns out each usage of the function now has a file-spec in front of it. My function correctly shows up in the Add-in list, and if I delete the long pathname prefix, the function does work, but when I opened it later I found the full pathnames were back, but this time with the name of the testing user...
='C:\Users\Gord\Dropbox\Seabbatical\IT Dept\Office\sltc VBA code.xlam'!sltcSumColor()
I poked around and see information on Personal.xlsb and XLSTART, and compiling - but I feel like I'm going in circles. How do I properly make my function ready for big-time?
I've attached a cut-back version of the spreadsheet (OzGrid sample.xlsm) and I believe the VBA code is included too.
Note: I attempted many variations to put a double-underline on the cell that holds the sum, but never could get it to work and gave up (but pieces of that code are still in there).
If anybody has any guidance for me it would be much appreciated.
Thanks in advance,