Excel error in opening file

  • Thread starter Thread starter Ronald
  • Start date Start date
R

Ronald

When I use Excel to open a single word file like fixedassets.xls
my Excel opens fine. We reloaded Office 97. Even created new
user so not settings carried forward.

The Problem: When opening a compound file like:
Deposit Check November.xls, Excel gives me an error message
"Cannot open 'Deposit.xls cannot be found.'" I click OK then
I get "Cannot open Check.xls." I click OK then get "Cannot
open November.xls." My observation. Any compound file with
spaces cannot open properly. It tries to open each part like it is
a separate file. I have been opening these for
several years. Should not matter
 
Ronald

This is generaly due to the fact that the command line in the shortcut to open
is missing double quotes around the complete path.

"C:\your path\to excel\your file.xls" is proper syntax.

If not using a shortcut, you should try re-registering Excel.

Start>Run "excel.exe /unregserver"(no quotes and note the space before the /
mark).

Then re-register by Start>Run "excel.exe /regserver

You may have to enter your full path to excel.exe....in that case surround
with quotes as in..... "C:\mypath\to Excel\somewhere\excel.exe" /unregserver

Gord Dibben XL2002
 
"Gord";
I had this exact same problem (XL2k on a w2k m/c) and the "re-register"
worked like a charm.
The one thing I didn't do was the "unregserver" command. This wasn't
mentioned on Chip Pearson's site (at least I didn't see it).
Is this important or did I just get lucky (that doesn't happen much!)?
Also, I'd asked (on the ""NewUser's" ng) as to what would cause this to
happen, as I didn't receive any replies I assume that there's an
infinite # of reasons(?). I only ask because I'd never encountered this
before in the years that I've been using XL.
 
Some people have complained that simply using /regserver didn't help, but doing
the /unregserver followed by the /regserver did.

And since it only takes a moment to do each, some people have started including
that in their standard replies. (I have and it looks like Gord has, too.) (And
since it doesn't hurt and stops the poster from coming back for further help,
why not???)

I've only had to use it a couple of times and not using the /unregserver worked
ok both times.

And I have no idea what upsets the windows registry. I figured gremlins <bg>.
 
Thanks.
The only thing that I'd done, that I can think of, was installing
ZoneAlarm (about 3 days prior to the problem).
"Pretty" sure I used XL after that.
Oh well, just another thing in my life I don't understand, maybe my son
can explain it to me (I used to know everything, then I turned 50,
either that or he turned 16!).
 
RWN said:
*Thanks.
The only thing that I'd done, that I can think of, was installing
ZoneAlarm (about 3 days prior to the problem).
"Pretty" sure I used XL after that.
Oh well, just another thing in my life I don't understand, maybe m
son
can explain it to me (I used to know everything, then I turned 50,
either that or he turned 16!).
--
Regards;
Rob
------------------------------------------------------------------------
Dave Peterson said:
Some people have complained that simply using /regserver didn'
Click to expand...
help,
but doing
the /unregserver followed by the /regserver did.

And since it only takes a moment to do each, some people hav started
including
that in their standard replies. (I have and it looks like Gor
Click to expand...
has,
too.) (And
Click to expand...
 
I used regserver and this did not work. I did unregserver then
regserver and now everything is back to normal.

Ron
 
Back
Top