PC Review
Forums
Newsgroups
Microsoft Excel
Microsoft Excel Crashes
File won't save in 2003
Forums
Newsgroups
Microsoft Excel
Microsoft Excel Crashes
File won't save in 2003
![]() |
File won't save in 2003 |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
I thought I'd post this having wasted a lot of time yesterday - may save you
some! Our company has a template with a lot of VBA code (over 100 pages when pasted into Word) and, having worked fine in 97, it started refusing to save in 2003. I've found the reason is that we have a default Excel file type for saving set (through GPO) as 97/2003/5.0/95 rather than the usual M/soft Office Excel Workbook. Either the 5.0/95 aspect of this format or perhaps a bug/lazy omission in the conversion process means that too much VBA code will stop the file saving this way. So, simple fix: choose Microsoft Office Excel Workbook as the file type from the Save As dialog box. |
|
|
|
#2 |
|
Guest
Posts: n/a
|
It's interesting that this problem also affected someone! I've been having
this very annoying problem with some of my files with "tons" of VBA code. I couldn't explain why. They simply won't save when I click save. However, my case is even worse. There is simply no way I can save them manually. Absolutely no way at all. I MUST go to the Immediate window of VBA Editor and type the VBA statement to save those files every time. (The only way I can fix them is to rebuild the whole file. But sometimes it's not very possible because of the time required, and the problem reappears quickly.) Anyway, this is not a question. So no answer required. Just share with you my experience. :> (Well, if you want to play with some of the really complex files I mentioned, go to my web site.) Regards, Edwin Tam edwintam@vonixx.com http://www.vonixx.com "Martin" wrote: > I thought I'd post this having wasted a lot of time yesterday - may save you > some! > > Our company has a template with a lot of VBA code (over 100 pages when > pasted into Word) and, having worked fine in 97, it started refusing to save > in 2003. > > I've found the reason is that we have a default Excel file type for saving > set (through GPO) as 97/2003/5.0/95 rather than the usual M/soft Office Excel > Workbook. Either the 5.0/95 aspect of this format or perhaps a bug/lazy > omission in the conversion process means that too much VBA code will stop the > file saving this way. > > So, simple fix: choose Microsoft Office Excel Workbook as the file type from > the Save As dialog box. |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

