Re: How do I unlock FILE access?

You will not be able to delete a file in use, or thought to be in use. The
short filenames will display with the dir command with dir /x. You can use
Command Line Help with /? after the command to tell you how to use the
commands.

"Dave Peterson" wrote:

> Maybe if you put quotes around the long file name:
>
> del "this is a long file name that can be deleted.xls"
>
> worked ok for me in winxp.
>
> But maybe it wasn't deleted, because the OS saw that file as locked.
>
> You may want to experiment with an unlocked file with a long name just so you
> know the next time.
>
> rcmodelr wrote:
> >
> > Thanks for your efforts, but last night, I again tried everything that had
> > previously been unsuccessful at releasing the files. But first I tried
> > deleting the files through the command prompt.
> >
> > The system gave the LONG filenames when I typed Dir/w
> >
> > But the Del command refused to recognize ANY long filenames.
> >
> > Then I went back and tried rebooting the computer AGAIN... Files were still
> > indicated as already in use by me...
> >
> > Then I added the /regserver command switch to the Excel command line.
> > Afterwards (this was the SECOND time I tried these same things), the computer
> > STILL said the files were already in use.
> >
> > Then, I (for the THIRD time) rebooted the computer. NOTHING done different
> > this time compared to the last times.... But this time, after using Excel's
> > /regserver command line switch AND rebooting the computer, the system FINALLY
> > released the files so they are once again accessible without having the
> > forced READ-ONLY setting.
> >
> > BUT... my trying to delete the files from the command prompt brings up
> > another question...
> >
> > Why is it that the dir command will show the LONG filenames, but the del
> > command will NOT recognize LONG filenames? And, how can I force the dir
> > command to give the SHORT filenames so I can probably identify the bad file
> > by creation date, and have the name displayed in a format that the del
> > command WILL recognize???
> >
> > If it matters for this, the computer at work has Windows 2000 as its
> > installed operating system, and in the Windows Accessories menu lists Command
> > Prompt as one of theitems available.
> >
> > "Dave Peterson" wrote:
> >
> > > I really meant the rebooting the network suggestion only if the file was saved
> > > on a network share--not on the local drive. (If it's saved on a local drive,
> > > then rebooting the network should not make any difference.)
> > >
> > > If you shell to the command prompt, you can issue a DIR command like:
> > >
> > > dir /x /p
> > >
> > > /x means show both long and short names
> > > /p will fill the screen, then pause
> > >
> > > dir /?
> > >
> > > will show you a whole bunch of options.
> > >
> > > I used winXP Home and shelled to the command prompt by:
> > > windows start button|Run
> > > cmd
> > > (hit enter)
> > >
> > > ====
> > > But if windows thinks that file should be locked, then I don't think you'll have
> > > any luck with the old DOS command to delete the file.
> > >
> > > ====
> > >
> > > And just double checking...
> > >
> > > You've rebooted your local pc and you've deleted the files in windows temp
> > > folder, right?
> > >
> > > windows start button|run
> > > %temp%
> > > (and hit enter)
> > >
> > > is a quick way to get there.
> > >
> > >
> > >
> > >
> > >
> > >
> > > rcmodelr wrote:
> > > >
> > > > Yes, it IS connected to the companies network. NO.. I am UNABLE TO try
> > > > re-booting the server. I have Administrator access privelages on the
> > > > computer I work at, but have NO access rights to the main server system.
> > > >
> > > > I had thought of BYPASSING Windows and DELETING the files through DOS.
> > > >
> > > > However, TWO of the files are named with Windows accepted LONG filenames
> > > > (DOS will show as Truncated/serialized filenames) Any EASY way to figure out
> > > > what DOS would find on the computer's hard drive as the filename? (the files
> > > > themselves ARE saved on the hard drive of the computer I work with and NOT
> > > > some drive somewhere else in the network.)
> > > >
> > > > If it would help... without directory paths, here is ONE of the filenames as
> > > > Excel and Windows see it:
> > > >
> > > > Daily Live Bird Weight *** (BOTH SHIFTS)0811.xls
> > > >
> > > > And there are literally DOZENS of files on the SAME directory by the ALMOST
> > > > SAME name (Only difference being that the 0811 is the plant's run-date Month
> > > > and DAY) and there are currently about 3 month's worth of similarly named
> > > > files in that directory so a file from 2 - 3 months ago can be opened to find
> > > > average driver turn-around time from the farm they are catching birds at so
> > > > arrival time estimate for third load from farm can be calculated when the
> > > > plant starts running low on birds and starts calling me asking when the next
> > > > load will be there.
> > > >
> > > > "Dave Peterson" wrote:
> > > >
> > > > > Is that file on a network share?
> > > > >
> > > > > If yes, maybe rebooting that server would help.
> > > > >
> > > > >
> > > > >
> > > > > rcmodelr wrote:
> > > > > >
> > > > > > Before you say I should:
> > > > > > Type "C:\Program Files\Microsoft Office\Office\Excel.Exe" /regserver
> > > > > > (include the quotes) -- adapt to fit your path. (to force Excel to
> > > > > > RE-register itself...)
> > > > > >
> > > > > > I already tried that, and both Excel AND Windows still say I am already
> > > > > > accessing those files so they can be opened as READ ONLY, but I STILL CAN NOT
> > > > > > DELETE or rename the files.
> > > > > >
> > > > > > "rcmodelr" wrote:
> > > > > >
> > > > > > > This morning, at work, I was using Excel to track data on trucks at work.
> > > > > > > During break, I opened another Excel document to view. Shortly after the
> > > > > > > second Excel document was opened, another truck came in. When I tried to go
> > > > > > > back to the spread*** file to record the info for the truck that came in,
> > > > > > > Excel went idle for 30 seconds, then came back with a READ ERROR saying it
> > > > > > > had tried reading a memory address that was un-readable. When I clicked OK
> > > > > > > on the read error message box, Excel SHUT DOWN COMPLETELY...
> > > > > > >
> > > > > > > When I RE-started Excel, and tried loading the truck info file that was
> > > > > > > supposed to be activating when the memory read error occurred, Excel reported
> > > > > > > that I (well, MY UserID) was accessing that file elsewhere, and Excel would
> > > > > > > therefore ONLY open it as a READ-ONLY file. It gave the SAME "protection"
> > > > > > > message when it tried opening my Personals.xla file.
> > > > > > >
> > > > > > > To be able to record the info on the trucks, I had to save the file under a
> > > > > > > NEW NAME so the data could be saved.
> > > > > > >
> > > > > > > Afterward, I even tried RE-BOOTING the computer, THEN accessing the file,
> > > > > > > and Excel STILL says the Personals and truck file have been RESTRICTED by MY
> > > > > > > UserID so they are STILL only accessible in READ-ONLY mode. So I tried
> > > > > > > DELETING them with Windows Explorer, which says the files CAN NOT BE DELETED
> > > > > > > because my userID has restricted access to these files through Excel.
> > > > > > >
> > > > > > > How can I get Excel AND Windows to REMOVE the protection from these NO
> > > > > > > LONGER NEEDED files? I have a couple new macros to add to my Personals file,
> > > > > > > but Excel won't allow me to do so, stating that the Personals file is already
> > > > > > > in use BY ME so it can be opened ONLY in READ-ONLY mode, and I CAN NOT save
> > > > > > > it if I want to.
> > > > >
> > > > > --
> > > > >
> > > > > Dave Peterson
> > > > >
> > >
> > > --
> > >
> > > Dave Peterson
> > >
>
> --
>
> Dave Peterson
>
.