Excel hanging on SaveAs

[Zarch]

I have a workbook which refuses to save once data has been imported. I am not
using an ActiveWorkbook.OnSave command and have tried turning everything I
can think of back on i.e. ScreenIpdating=True, EnableEvents=True,
IgnoreRemoteRequests=False, have unprotected the worksheets and macros and
unhidden all rows & columns.
Whether I try to SaveAs programatically, or via the Excel User Interface, I
sometimes get a status bar message of 'Calculating Cells 0%' - so I have
tried Application.CalculateBeforeSave = False. I have also run Windows
Update to ensure that the Verclsid.exe glitch is not the cause.
The save creates a 16KB file with a name such as 7ACA2000 or 8C805000, but
that is as far as it gets. CPU usage goes to 100% and even leaving it for
half an hour does not allow it to complete a save.

If I strip out most of the imported data then it will save after a lot of
thought. What processes could be occurring to make the save take so long?


This is the Event Viewer log

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 11/10/2007
Time: 09:33:41
User: N/A
Computer: PRIVATE
Description:
Hanging application EXCEL.EXE, version 11.0.8146.0, hang module hungapp,
version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 45 58 43 45 4c 2e EXCEL.
0018: 45 58 45 20 31 31 2e 30 EXE 11.0
0020: 2e 38 31 34 36 2e 30 20 .8146.0
0028: 69 6e 20 68 75 6e 67 61 in hunga
0030: 70 70 20 30 2e 30 2e 30 pp 0.0.0
0038: 2e 30 20 61 74 20 6f 66 .0 at of
0040: 66 73 65 74 20 30 30 30 fset 000
0048: 30 30 30 30 30 00000

 

[Barb Reinhardt]

Don't know if this helps

http://support.microsoft.com/default.aspx/kb/157951

The OnSave property has been replaced by the BeforeSave event in Microsoft
Excel 97.

The OnSave property was introduced in Microsoft Excel for Windows 95,
version 7.0, but still can be used in Microsoft Excel 97. The OnSave property
returns or sets the name of a Visual Basic procedure to run after the user
invokes either the Save or Save As command, but before the workbook is
actually saved. Consider the following items when you use the OnSave
property:

• The procedure that is specified to run with the OnSave property must take
one Boolean argument (see the example below).
• Only Visual Basic procedures are supported by this property; Microsoft
Excel version 4.0 Macro Language procedures are not supported.
• The value of the OnSave property is not saved with the workbook; it must
be reset each time the workbook is opened.
• This event is not called if the workbook is saved when a macro or mail
command runs, or when an embedded workbook is updated.