MS-Excel VBA file (XLA) saving problem

[Arvind Jagtap]

Hello,


I have written one MS-Excel add-in. One day I modified it and saved. When I
closed Excel and I found the changes are lost. They don't get saved. Since
then I could not save a single byte in that XLA file. I tried many things,
but in vain.

At last I reinstalled MS-Office hoping this will solve the problem. But this
didn't work. Please help me.


Is it a known bug? If yes, what is the workaround?


Thanks,

Arvind

 

[Dave Peterson]

Are you sure you're saving to the location you want? Maybe you have an updated
file in a different location?

I've never had any trouble saving from the VBE (making sure that the .xla
project was the active project first), but I've read posts from others that say
they have.

You could try this to save your addin:
hit alt-f11 to open the VBE
hit ctrl-g to see the immediate window

type something like:
workbooks("myaddinnamehere.xla").save

Test with a minor change, then close excel and reopen to see if it worked.

Some have put a module in that addin with a procedure that does the same kind of
thing.

Option Explicit
Sub SaveMeNow()
thisworkbook.save
end sub

And just run that whenever they want.

 

[Arvind Jagtap]

Hi Dave,

I have confirmed that the same file is in use. I searched my whole hard disk
to find the same file name. I deleted other files to kept only one copy.

After confirming the file is same, I watched the file in the windows
explorer and I found some surprizing things. When I start MS-Excel, the
modified date time of XLA file changes to current date time and remains the
same till I close the MS-Excel. As soon as I close the MS-Excel, the
modified date time revertes back to old date time. When I press save button
in visual basic editor the modified date time doesn't change.

As you said, I inserted the "thisworkwook.save" in the Workbook_BeforeClose
subroutine and... it could save the file. Thank you very much for providing
this idea. Now I can continue my work with this work around.

If you come to know the reason behind this abnormal behaviour, please let me
know.

Thanks and regards,
Arvind Jagtap

 

[Dave Peterson]

The date/time changes for every file you open--that's just the way excel works.

I don't have a guess why just clicking on File|Save inside the VBE doesn't work
for you. It's always worked for me.

(Irritating question follows!)

Are you positive that the .xla's project is the active project when you hit
File|Save (or click the Save icon)?

All that written, I've read a few posts by pretty smart people that have
experienced the same thing--that's where I picked up the suggested work-around.

(I have no idea what the problem could be!)

 

[Arvind Jagtap]

Hi Dave,

I check every time the active project before pressing save button. I
exclusive click on the project name or place cursor in the specified add-in
program before saving. But still it is not saving the file.

It was working on my machine for many years. It stopped working since 1/2
months. I reinstalled MS-Office for this purpose but in vain.

If I find the reason behind this, I will definitely let you know.

Thanks ands regards,
Arvind Jagtap

 

[Dave Peterson]

Please post back if you do find the solution.

I'm sure the people who have the same problem would like to know a solution--and
google would have it, too!

Hi Dave,

I check every time the active project before pressing save button. I
exclusive click on the project name or place cursor in the specified add-in
program before saving. But still it is not saving the file.

It was working on my machine for many years. It stopped working since 1/2
months. I reinstalled MS-Office for this purpose but in vain.

If I find the reason behind this, I will definitely let you know.

Thanks ands regards,
Arvind Jagtap

 

[rcelleri]

I have the exact same problem

I have the exact same problem. Any changes I make in VB are not save, the xla modify date is the date and time when Excel is opened and is then reverted to the original modify date when I close Excel. The IMMEDIATE window workaround works for me as well. I am wondering if you ever found a permanent solution. Thank you.