N
Nick Pomponio
I am having a strange problem with Visio files that are
saved as XML. If I try to select any .VDX file, or even hover
the mouse over it, within Windows Explorer, all Explorer
windows close and the desktop "resets" (i.e. all icons
disappear, then sequentially reappear after a 1-2 second delay).
The only way that I can access the files to view the XML or to
delete them is to use the command prompt. This problem occurs
regardless of file location (network, local). I noticed it
several months ago, but, fortunately, I have not needed the VDX
files often. If I change the extension to XML, the problem does
not occur; I can select it as normal.
My wild guess is that selecting or hovering the mouse over the VDX
file causes the shell to attempt to retrieve information from it
in order to provide text for the pop-up "baloon" box within Windows
Explorer; that explains the slight delay before the reset happens.
Here are the outputs of the related assoc and ftype commands:
c:\>assoc .vdx
.vdx=Visio.Drawing.6
c:\>ftype Visio.Drawing.6
Visio.Drawing.6="C:\Program Files\Microsoft Office\Visio10\visio.exe"
"%1"
I would greatly appreciate any help, as this perplexing problem
greatly reduces productivity when working with the VDX files.
Thanks,
-Nick Pomponio
saved as XML. If I try to select any .VDX file, or even hover
the mouse over it, within Windows Explorer, all Explorer
windows close and the desktop "resets" (i.e. all icons
disappear, then sequentially reappear after a 1-2 second delay).
The only way that I can access the files to view the XML or to
delete them is to use the command prompt. This problem occurs
regardless of file location (network, local). I noticed it
several months ago, but, fortunately, I have not needed the VDX
files often. If I change the extension to XML, the problem does
not occur; I can select it as normal.
My wild guess is that selecting or hovering the mouse over the VDX
file causes the shell to attempt to retrieve information from it
in order to provide text for the pop-up "baloon" box within Windows
Explorer; that explains the slight delay before the reset happens.
Here are the outputs of the related assoc and ftype commands:
c:\>assoc .vdx
.vdx=Visio.Drawing.6
c:\>ftype Visio.Drawing.6
Visio.Drawing.6="C:\Program Files\Microsoft Office\Visio10\visio.exe"
"%1"
I would greatly appreciate any help, as this perplexing problem
greatly reduces productivity when working with the VDX files.
Thanks,
-Nick Pomponio