Visio For Enterprise Architects has BUGS!!!! (AND IS CRAPPY!!!)

[Coleen]

I still think Microsoft's Visual Studio's version of Visio is CRAPPY!!! I
was just viewing a set of sample User Interface screens that I created in
Visio (with Excel pasted tables), and I clicked on the print button to print
the set of sample screens. The ENTIRE application closed. Now when I open
Visio, and try to re-open the file I just printed, I get a message ".....mc
fuel supplier screens .vsd is already open for editing by CHolley on
247405W2k. Would you like to open a copy?" CHolley is me, and it is not
open for editing, 'cause it just bombed!!! This is the second time today
this has happened! The first time I just thought that I had accidentally
closed it. This time, I KNOW I didn't, I was working in it! The only way
to get rid of this problem is for me to COMPLETELY reboot my system to
unlock the files! That is absolutely RIDICULOUS!!! When is a fix for this
poor application going to come out???

 

[Karsten Farrell]

Hi Coleen, thanks for writing this:

I still think Microsoft's Visual Studio's version of Visio is CRAPPY!!! I
was just viewing a set of sample User Interface screens that I created in
Visio (with Excel pasted tables), and I clicked on the print button to print
the set of sample screens. The ENTIRE application closed. Now when I open
Visio, and try to re-open the file I just printed, I get a message ".....mc
fuel supplier screens .vsd is already open for editing by CHolley on
247405W2k. Would you like to open a copy?" CHolley is me, and it is not
open for editing, 'cause it just bombed!!! This is the second time today
this has happened! The first time I just thought that I had accidentally
closed it. This time, I KNOW I didn't, I was working in it! The only way
to get rid of this problem is for me to COMPLETELY reboot my system to
unlock the files! That is absolutely RIDICULOUS!!! When is a fix for this
poor application going to come out???

The fix might already be there. You don't mention your O/S version, but
MSKB article 813415 (WinXP) at this URL:

http://support.microsoft.com/default.aspx?scid=kb;en-us;813415

has this Cause listed:

<quote>
When the .NET application quits unexpectedly, the .NET Framework cannot
call the Unregister() function for the decoupled provider. Therefore,
the decoupled provider registration persists.
</quote>

The KB article talks about getting an "access denied" error instead of
an "already open" error ... so this might not apply to your situation.
But the scenario you described certainly sounds like the same cause.
Maybe you found a new bug. <g>

A supported fix is available, but you have to contact Microsoft support
to get it (apparently to verify that this is indeed the cause of your
problem).

BTW, since I don't work for Microsoft, I can't comment on when a fix
will be available. Like you, I'm also just a humble user of this
application ... trying to get it to work for me. Visio has some really
frustrating parts, I agree, but it's not as bad as some of the other
apps I have to work with. Small consolation.

 

[Coleen]

Thanks for Replying Karsten

I know I've said some strong things about Microsoft's versions of Visio, but
I used the previous version done by Vision Corp (V5.0A), which granted is
older and doesn't have all of the "Cool" templates, but on the whole, I
think it works better! I'm just trying to create simple DFD's and some
sample Windows application sample screens - and all I have had is problems!
So, I'm sure you (and Microsoft) can understand my frustration!

Thanks for the advice & link. I have sent a copy of it to our department in
charge of installing software and fixes, so hopefully we can get rid of the
problem!