View Single Post
  #3   Report Post  
Old November 24th 06, 03:46 AM posted to microsoft.public.excel.misc
goneill3 goneill3 is offline
external usenet poster
 
First recorded activity by ExcelBanter: Nov 2006
Posts: 3
Default Copying worksheet, path/file access error: '\vbxxx.tmp'

Hi Dave,

Thanks for the advice. I had a look at the hyperlink you posted, didn't help
.

I have tried this on multiple workstations and I can always reproduce the
error provided those 3 conditions are met; network file, open the file via
Excel's file open menu, and contains macros.



"Dave Peterson" wrote:

I think that this has come up a couple of times--but I'm not sure if I've
seen/remember the solution.

I suggested this once:

Maybe cleaning up your temp folder will help.

close excel
windows start button|run
%temp%
Delete all those files and folders.

It may be best to do this right after you reboot your pc, so that no other
programs are running that need any of these files.

==
If that doesn't help, try disabling your antivirus software (just temporarily)
to see if that helps.

=======
But never got a reply that it worked.

=====
I searched google again for "\vb" and .tmp and got a few hits.

One of them:
http://groups.google.co.uk/group/mic...1eecaad1c774cc
or
http://snipurl.com/1339g

If you find a solution, please post back--then google will have it for the next
victim.



goneill3 wrote:

I am getting the following error when copying worksheets within a workbook,
path/file access error: '\vbxxx.tmp' but only under very specific condidions.

Open worksheet with macros from network via Execl's file open and copy a
worksheet inside a workbook produces the error.

If the spreadsheet doesn't have any macros, no problems. If I go and add a
macro, which is does nothing other than contain an empty function, I get the
error.
If I open the (network) file via windows explorer I don't have a problem
copying worksheets.
If I copy the files to my local hard drive, no problems copying worksheets.
I have tested this on both Office 2000 and Office 2003 and they both get the
error.
I haven't tested Office 2007 yet.

Any feedback would be appreciated.


--

Dave Peterson