Hi All,

I have an add-in that I have built myself and use on the 3 PC's I have to
use on different sites. I also have a spreadsheet that I use on all 3
sites. The spreadsheet uses macros and UDF's from within the add-in.

All works fine until I move the worksheet from one PC to another, once
loaded on the new PC it requires the "link" to be updated in order to work
(i.e. you have to point it to the location of the add-in on the new pc)

Is there any advice anyone can give in order to make my worksheet more
portable. I do-not want to include the code from the add-in within my
workbook if at all possible.

2 other bits of potentially useful information (1) I have had a go at using
refernces but I presume these are specific to 1 PC?
(2) I don't understand how / when you should use a class module - is this a
potential solution here?

Ta

Andi

Not enough information to be sure ....

If your addin is loaded on each machine and the workbook has no code in it
then the addin should be available to the instance of excel and work on "any"
file.

If you are discussing changing the addin (workbook) and moving it to a new
machine the process is based on how/where it was loaded, XLStart vs library
vs XLAddin
in XLStart you would simply save the new addin into folder overwriting the
old file.

Alternatively, there could be an issue created by the code in you addin...

post back with more info.

"Andibevan" wrote:

Hi All,

I have an add-in that I have built myself and use on the 3 PC's I have to
use on different sites. I also have a spreadsheet that I use on all 3
sites. The spreadsheet uses macros and UDF's from within the add-in.

All works fine until I move the worksheet from one PC to another, once
loaded on the new PC it requires the "link" to be updated in order to work
(i.e. you have to point it to the location of the add-in on the new pc)

Is there any advice anyone can give in order to make my worksheet more
portable. I do-not want to include the code from the add-in within my
workbook if at all possible.

2 other bits of potentially useful information (1) I have had a go at using
refernces but I presume these are specific to 1 PC?
(2) I don't understand how / when you should use a class module - is this a
potential solution here?

Ta

Andi

I think I may need to change where the add-in is loaded as I want the code
in my spreadsheet to be able to call the UDF's in my add-in and it to appear
as though they are just a normal part of excel - i.e. there is no problems
with having to update links.

I will do some reading about the options relating to loading add-ins.

"Vacation's Over" wrote in message
...
Not enough information to be sure ....

If your addin is loaded on each machine and the workbook has no code in it
then the addin should be available to the instance of excel and work on
"any"
file.

If you are discussing changing the addin (workbook) and moving it to a new
machine the process is based on how/where it was loaded, XLStart vs
library
vs XLAddin
in XLStart you would simply save the new addin into folder overwriting the
old file.

Alternatively, there could be an issue created by the code in you addin...

post back with more info.

"Andibevan" wrote:

Hi All,

I have an add-in that I have built myself and use on the 3 PC's I have
to
use on different sites. I also have a spreadsheet that I use on all 3
sites. The spreadsheet uses macros and UDF's from within the add-in.

All works fine until I move the worksheet from one PC to another, once
loaded on the new PC it requires the "link" to be updated in order to
work
(i.e. you have to point it to the location of the add-in on the new pc)

Is there any advice anyone can give in order to make my worksheet more
portable. I do-not want to include the code from the add-in within my
workbook if at all possible.

2 other bits of potentially useful information (1) I have had a go at
using
refernces but I presume these are specific to 1 PC?
(2) I don't understand how / when you should use a class module - is
this a
potential solution here?

Ta

Andi