asked on .xlam add-in is not being referenced in Workbook Code
Having difficulty referencing code from an add-in.
Created a Personal.xlsb workbook and then a VBA_CODE_Tools.xlam add-in to store commonly used functions (LastDataRow, etc.). These are installed.
The routines were copied from a .xlsm workbook over to VBA_CODE_Tools.xlam and then deleted from the .xlsm workbook. When running a newly created Sub, and referencing lRow = LastDataRow, the code just moves to the next line with a "LastDataRow is Empty" when hovering over it.
If I move the Function back to the .xlsm workbook, it runs correctly.
Even installed a Workbook_Open routine to reference the add-in. What else am I missing?
Cook09
Created a Personal.xlsb workbook and then a VBA_CODE_Tools.xlam add-in to store commonly used functions (LastDataRow, etc.). These are installed.
The routines were copied from a .xlsm workbook over to VBA_CODE_Tools.xlam and then deleted from the .xlsm workbook. When running a newly created Sub, and referencing lRow = LastDataRow, the code just moves to the next line with a "LastDataRow is Empty" when hovering over it.
If I move the Function back to the .xlsm workbook, it runs correctly.
Even installed a Workbook_Open routine to reference the add-in. What else am I missing?
Cook09
Microsoft ExcelVB Script
Last Comment
Roy Cox
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
so we can see how your functions are constructed, please post the code you are using for LastDataRow, thanks
ASKER
Experts,
It seems that Roy had the best solution in my case. It began to work when the VBAProject name was changed and then checked in the References section.
Thanks
Cook09
2016-09-01_14-28-42.jpg
It seems that Roy had the best solution in my case. It began to work when the VBAProject name was changed and then checked in the References section.
Thanks
Cook09
2016-09-01_14-28-42.jpg
ASKER
Thanks...
Pleased to help