Why Would Add-In Macro Not Be Accessible?
 

I posted this in the General Questions area and I think it should have been
here so here it is ... again.

I have a number of Excel reports that are running on a server at work on set
frequencies (typically daily). I created an add-in for a generic print
routine so all the reports could use it to do the automated printing. The
add-in is loaded in
Excel on the server and shows in the list of add-ins.
What is happening, is that some workbooks do not recognize the add-in
anymore (ie., "macro not found"). It does not affect all workbooks though.
They all used to work fine in the past.
I can open the VB Editor and see the add-in listed in the Project Explorer.
I can open it and see the code too.

The only way to fix it for these workbooks is to copy the code and insert it
into a new module in the workbook.

Any idea why this is happening and how to fix it so it only uses the add-in
macros?

--
Edwin Kelly
Houston, TX

Why Would Add-In Macro Not Be Accessible?
 

for macro to call macro in other workbook/addin the first workbook need have
a refernce to addin set in Tools, References in the vbe. or else use the
run method like this: run "addin.xla!macroname"


"Edwin Kelly" wrote in message
...
|I posted this in the General Questions area and I think it should have been
| here so here it is ... again.
|
| I have a number of Excel reports that are running on a server at work on
set
| frequencies (typically daily). I created an add-in for a generic print
| routine so all the reports could use it to do the automated printing. The
| add-in is loaded in
| Excel on the server and shows in the list of add-ins.
| What is happening, is that some workbooks do not recognize the add-in
| anymore (ie., "macro not found"). It does not affect all workbooks
though.
| They all used to work fine in the past.
| I can open the VB Editor and see the add-in listed in the Project
Explorer.
| I can open it and see the code too.
|
| The only way to fix it for these workbooks is to copy the code and insert
it
| into a new module in the workbook.
|
| Any idea why this is happening and how to fix it so it only uses the
add-in
| macros?
|
| --
| Edwin Kelly
| Houston, TX

Why Would Add-In Macro Not Be Accessible?
 

Ok thanks. So I guess it is impossible to call a macro that way and pass
variable the macro needs?
--
Edwin Kelly
Houston, TX


"Homey" wrote:

for macro to call macro in other workbook/addin the first workbook need have
a refernce to addin set in Tools, References in the vbe. or else use the
run method like this: run "addin.xla!macroname"


"Edwin Kelly" wrote in message
...
|I posted this in the General Questions area and I think it should have been
| here so here it is ... again.
|
| I have a number of Excel reports that are running on a server at work on
set
| frequencies (typically daily). I created an add-in for a generic print
| routine so all the reports could use it to do the automated printing. The
| add-in is loaded in
| Excel on the server and shows in the list of add-ins.
| What is happening, is that some workbooks do not recognize the add-in
| anymore (ie., "macro not found"). It does not affect all workbooks
though.
| They all used to work fine in the past.
| I can open the VB Editor and see the add-in listed in the Project
Explorer.
| I can open it and see the code too.
|
| The only way to fix it for these workbooks is to copy the code and insert
it
| into a new module in the workbook.
|
| Any idea why this is happening and how to fix it so it only uses the
add-in
| macros?
|
| --
| Edwin Kelly
| Houston, TX

Why Would Add-In Macro Not Be Accessible?
 

no problem either way to pass argument. if setting refence normal call work
okay. if using run:

Run "MyAddin.xla!SubToCall", "abc"

"Edwin Kelly" wrote in message
...
| Ok thanks. So I guess it is impossible to call a macro that way and pass
| variable the macro needs?
| --
| Edwin Kelly
| Houston, TX
|
|
| "Homey" wrote:
|
| for macro to call macro in other workbook/addin the first workbook need
have
| a refernce to addin set in Tools, References in the vbe. or else use
the
| run method like this: run "addin.xla!macroname"
|
|
| "Edwin Kelly" wrote in message
| ...
| |I posted this in the General Questions area and I think it should have
been
| | here so here it is ... again.
| |
| | I have a number of Excel reports that are running on a server at work
on
| set
| | frequencies (typically daily). I created an add-in for a generic
print
| | routine so all the reports could use it to do the automated printing.
The
| | add-in is loaded in
| | Excel on the server and shows in the list of add-ins.
| | What is happening, is that some workbooks do not recognize the add-in
| | anymore (ie., "macro not found"). It does not affect all workbooks
| though.
| | They all used to work fine in the past.
| | I can open the VB Editor and see the add-in listed in the Project
| Explorer.
| | I can open it and see the code too.
| |
| | The only way to fix it for these workbooks is to copy the code and
insert
| it
| | into a new module in the workbook.
| |
| | Any idea why this is happening and how to fix it so it only uses the
| add-in
| | macros?
| |
| | --
| | Edwin Kelly
| | Houston, TX
|
|

Why Would Add-In Macro Not Be Accessible?
 

Check your other post.

Edwin Kelly wrote:

I posted this in the General Questions area and I think it should have been
here so here it is ... again.

I have a number of Excel reports that are running on a server at work on set
frequencies (typically daily). I created an add-in for a generic print
routine so all the reports could use it to do the automated printing. The
add-in is loaded in
Excel on the server and shows in the list of add-ins.
What is happening, is that some workbooks do not recognize the add-in
anymore (ie., "macro not found"). It does not affect all workbooks though.
They all used to work fine in the past.
I can open the VB Editor and see the add-in listed in the Project Explorer.
I can open it and see the code too.

The only way to fix it for these workbooks is to copy the code and insert it
into a new module in the workbook.

Any idea why this is happening and how to fix it so it only uses the add-in
macros?

--
Edwin Kelly
Houston, TX

--

Dave Peterson