AutoRecover in Office 2000

A customer of mine recently had a problem with Excel 2000 – yes lots of people are still using Office 2000 as it’s very fast and does most of what they need. It had crashed and they hadn’t saved their changes in a few hours.

Now, if this had been Office 2003/2007 the next time they opened Excel it would have prompted them with an “AutoRecovered” version of their file. By default Excel 2003/2007 AutoRecover an open worksheet every 10 minutes – this can be changed.

But this didn’t seem to be the case with Excel 2000. I had thought it was available in Excel 2000 but nothing could be found in Tools | Options. It was there in Word 2000 in Tools | Options | Save so what was the deal?

Turns out that, by default, AutoRecover isn’t installed in Excel 2000. It’s there as an Add-In. You must first install the Add-In by going to Tools | Add-Ins and choosing the “Autosave” Add-In. Once this installs you’ll see the Autosave option in the Tools menu. Clicking it will allow you to configure the time interval and whether all sheets or just the active sheet should be accounted for.

How bizarre, and how frustrating for my customer, that this feature was available but not put there by default. Very annoying.

Comments

Unknown said…

Interesting and beautiful blog lovely presentation thanks for sharing your views. please keep this...

we24support@1 888 399 9656
we24support
we24support-webeden

20 June 2012 at 08:56

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more... but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box: \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in: UPDATE tbSingletonData SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Logon Scripts in Group Policy not running

Problem Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful. Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...

Artifact Weblog

Search This Blog