XLA File

[Access101]

I've created an XLA file and saved it to the add in directory so that it
appears in the Add In list, and I can check it or uncheck it.

I can also close XL, then click directly on the XLA file, which opens up XL,
but I cannot see XLA file name on the title bar, only Book1. And tit's not
in the Windows menu either. However, it shows up in teh VBE Alt 11.

How do I open up the XLA file itself so I can end up making changes and
SAVING it?

Any help is appreciated.

 

[Bob Phillips]

The whole point of an XLA is that it is a code file, not a data spreadsheet,
so it gets hidden and you shouldn't be making changes to it. You don't
really want an XLA>

 

[Sheeloo]

Change the extension to XLS, edit and then save as XLA again.

 

[Peo Sjoblom]

Maybe you want the xlt which is a template? That way when you open the
template it will open a copy
of that file and if you want to make changes you just save over the old one

--


Regards,


Peo Sjoblom

 

[Harald Staff]

When you alter VBA code and all thet in the VB editor, hover the Save button
there and you'll see "Save xxx.xla", which the button does on click. This is
how you save changes to the code/userform/classes part of addins.

If you need to change it's invisible worksheets, go to ThisWorkbook module
and set property IsAddin to False. Now you can edit the sheets in Excel. Set
IsAddin to True again and save in the VB editor.

Note that addins doesn't prompt "save changes?" on exit, so you must know
what you are doing here.

HTH. Best wishes Harald

 

[Access101]

I must be misunderstanding this response.

Because my understanding is that unless every programmer were perfect, they
would at some point have a need to go back into the XLA and fix a bug.

However, setting the IsAddin Property to False solved the issue.

 

[Access101]

this is excellent. Thank you so much.

A customized toolbar that had been accidently attached to this file needed
to be removed, and then have the ability to save the file.

I did not need to change code, which obviously could have been done in the
VBE without having to use the IsAddin False concept.

So thank you very much for answering my question and providing the exact
solution that I needed!!!!

 

[Bob Phillips]

If you are just talking about changing the code, you can do that in the
VBIDE, and then save it there.

If you change the IsAddin property, what is the point. IsAddin = False -
what does that suggest to you?