[prev] [thread] [next] [lurker] [Date index for 2004/03/24]
As my time with Visio has continued I've started finding nuggets of
consistency within Visio operation that have reduced the resulting
irritation to the point where I'm actually getting some semi-decent work
done with it in not too much time. Today I produced a bit of design
where I was actually able to sit back with a contented and probably smug
smile on my face and think to myself: "You know, that's actually quite a
nice bit of work. I like that."
And then I hit Save.
Visio popped up a little warning to the effect that my file "rule
gui.vsd" had become corrupted somehow, and that it couldn't be saved,
but that I might be able to salvage my work from "~rule gui.vsd" and
that I should also close Visio as soon as possible.
The question of how the file had become corrupt despite having loaded
fine at the start of the session and Visio being the only program to
have touched it was knocking at the side of my brain, but I was far too
busy worrying about rescuing the data to notice. Fortunately, after
making a copy of the ~ file ("Copy of ~rule gui.vsd", yes, okay, I just
used Explorer) and quitting Visio, the new file loaded up just fine with
all of my work.
And so I was going to just write this one off to random weirdness until
I tried deleting the old "rule gui.vsd" and renaming the new one back to
that.
Now, when I double click on "rule gui.vsd" to start Visio with the file,
I get:
"Visio cannot open the file because it's not a Visio file."
When I undo the renaming operation in Explorer and double-click the file
(now reverted to "Copy of ~rule gui.vsd") again, it loads up just fine.
And I really was starting to get on with Visio, too.
-- Yoz
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52