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" wrote in message
...
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 wrote:

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