Technical Version of Visio?

I heard that there is a Visio Technical version to allow one to to draw
schematics and mechanical drawings. Or is this a library file that I can
download from MS?

There was a Technical version of Visio as well as a Professional version.
With Visio 2003, Visio Technical has been dropped and it's content is now
part of Visio Professional.

John... Visio MVP

Need stencils or ideas? http://www.mvps.org/visio/3rdparty.htm
Need VBA examples? http://www.mvps.org/visio/VBA.htm
Common Visio Questions http://www.mvps.org/visio/common_questions.htm
"Twe" wrote in message
...
I heard that there is a Visio Technical version to allow one to to draw
schematics and mechanical drawings. Or is this a library file that I can
download from MS?

"John Marshall, MVP" wrote :

There was a Technical version of Visio as well as a Professional version.
With Visio 2003, Visio Technical has been dropped and it's content is now
part of Visio Professional.

Further to John's comment - stencils of the "Technical" versions were
compatible with later "non-Technical" - I'm assuming that it is still so.

Personally, I think that Microsoft made a big mistake there. They turned a
good technical program into a mickey-mouse flow charter.

I use Visio for technical diagrams - excellent. But of course the Redmond
dungeon-dwellers and bean-counters wouldn't understand. We have a very apt
Australian epithet for them.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

I completely agree with you.

Unfortunately, there is no-one left at Microsoft to champion the technical
use of Visio.

I really hope that it is not too late for them to listen.

I have even demonstrated to them (Richard Wolf and others) how the embedded
CAD scaling is far worse now than it ever was. They admit it is wrong, but
do not consider it necessary to fix it, because we technical users are not
important enough.

"Pemo" wrote in message
...

"John Marshall, MVP" wrote :

There was a Technical version of Visio as well as a Professional version.
With Visio 2003, Visio Technical has been dropped and it's content is now
part of Visio Professional.

Further to John's comment - stencils of the "Technical" versions were
compatible with later "non-Technical" - I'm assuming that it is still so.

Personally, I think that Microsoft made a big mistake there. They turned
a
good technical program into a mickey-mouse flow charter.

I use Visio for technical diagrams - excellent. But of course the Redmond
dungeon-dwellers and bean-counters wouldn't understand. We have a very
apt
Australian epithet for them.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

Actually, a few of us are still around. And we speak our minds, but that
doesn't mean that Visio will become exclusively targeted at technical users.
The technical market is a difficult customer base for Microsoft to reach
(being geared for the mass market), and this holds true for Visio as a
Microsoft product now. The best way for us to address technical audiences
is to identify the features and issues that technical users have in common
with others. A few examples: drawing mechanics, performance, reporting,
data connectivity, layers. Let me hear about the tech-specific things you
want fixed or improved too, but it is admittedly a difficult sell
internally.

--
Mark Nelson
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

"David Parker" wrote in message
...
I completely agree with you.

Unfortunately, there is no-one left at Microsoft to champion the technical
use of Visio.

I really hope that it is not too late for them to listen.

I have even demonstrated to them (Richard Wolf and others) how the
embedded
CAD scaling is far worse now than it ever was. They admit it is wrong,
but
do not consider it necessary to fix it, because we technical users are not
important enough.

"Pemo" wrote in message
...

"John Marshall, MVP" wrote :

There was a Technical version of Visio as well as a Professional
version.
With Visio 2003, Visio Technical has been dropped and it's content is
now
part of Visio Professional.

Further to John's comment - stencils of the "Technical" versions were
compatible with later "non-Technical" - I'm assuming that it is still
so.

Personally, I think that Microsoft made a big mistake there. They
turned
a
good technical program into a mickey-mouse flow charter.

I use Visio for technical diagrams - excellent. But of course the
Redmond
dungeon-dwellers and bean-counters wouldn't understand. We have a very
apt
Australian epithet for them.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

"Mark Nelson [MS]" wrote:

Actually, a few of us are still around. And we speak our minds, but that
doesn't mean that Visio will become exclusively targeted at technical
users.
The technical market is a difficult customer base for Microsoft to reach
(being geared for the mass market), and this holds true for Visio as a
Microsoft product now. The best way for us to address technical audiences
is to identify the features and issues that technical users have in common
with others. A few examples: drawing mechanics, performance, reporting,
data connectivity, layers. Let me hear about the tech-specific things you
want fixed or improved too, but it is admittedly a difficult sell
internally.

I'm relieved to hear there is a voice of reason still there.

Of course we don't expect technical only; Visio needs to have features
across a spectrum.

I wonder if MS have considered following the very sensible lead of Mozilla
Firefox browser - where there is a range of add-ons to suit different needs
rather than the bloated
one-size-tries-to-fit-all-but-hasn't-got-a-hope-of-a-snowball-in-hell that
is the problem with Internet Explorer bloatware/sieveware.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

"Mark Nelson [MS]" wrote:

Actually, a few of us are still around. And we speak our minds, but that
doesn't mean that Visio will become exclusively targeted at technical
users.
The technical market is a difficult customer base for Microsoft to reach
(being geared for the mass market), and this holds true for Visio as a
Microsoft product now. The best way for us to address technical audiences
is to identify the features and issues that technical users have in common
with others. A few examples: drawing mechanics, performance, reporting,
data connectivity, layers. Let me hear about the tech-specific things you
want fixed or improved too, but it is admittedly a difficult sell
internally.

I'm relieved to hear there is a voice of reason still there.

Of course we don't expect technical only; Visio needs to have features
across a spectrum.

I wonder if MS have considered following the very sensible lead of Mozilla
Firefox browser - where there is a range of add-ons to suit different needs
rather than the bloated
one-size-tries-to-fit-all-but-hasn't-got-a-hope-of-a-snowball-in-hell that
is the problem with Internet Explorer bloatware/sieveware.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

Agreed. We do not need a technical version, we need the technical aspects
of Visio working properly first!
Mark - how do you want to receive comments?

"Pemo" wrote in message
...

"Mark Nelson [MS]" wrote:

Actually, a few of us are still around. And we speak our minds, but that
doesn't mean that Visio will become exclusively targeted at technical
users.
The technical market is a difficult customer base for Microsoft to reach
(being geared for the mass market), and this holds true for Visio as a
Microsoft product now. The best way for us to address technical
audiences
is to identify the features and issues that technical users have in
common
with others. A few examples: drawing mechanics, performance, reporting,
data connectivity, layers. Let me hear about the tech-specific things
you
want fixed or improved too, but it is admittedly a difficult sell
internally.

I'm relieved to hear there is a voice of reason still there.

Of course we don't expect technical only; Visio needs to have features
across a spectrum.

I wonder if MS have considered following the very sensible lead of Mozilla
Firefox browser - where there is a range of add-ons to suit different
needs
rather than the bloated
one-size-tries-to-fit-all-but-hasn't-got-a-hope-of-a-snowball-in-hell that
is the problem with Internet Explorer bloatware/sieveware.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

Agreed. We do not need a technical version, we need the technical aspects
of Visio working properly first!
Mark - how do you want to receive comments?

"Pemo" wrote in message
...

"Mark Nelson [MS]" wrote:

Actually, a few of us are still around. And we speak our minds, but that
doesn't mean that Visio will become exclusively targeted at technical
users.
The technical market is a difficult customer base for Microsoft to reach
(being geared for the mass market), and this holds true for Visio as a
Microsoft product now. The best way for us to address technical
audiences
is to identify the features and issues that technical users have in
common
with others. A few examples: drawing mechanics, performance, reporting,
data connectivity, layers. Let me hear about the tech-specific things
you
want fixed or improved too, but it is admittedly a difficult sell
internally.

I'm relieved to hear there is a voice of reason still there.

Of course we don't expect technical only; Visio needs to have features
across a spectrum.

I wonder if MS have considered following the very sensible lead of Mozilla
Firefox browser - where there is a range of add-ons to suit different
needs
rather than the bloated
one-size-tries-to-fit-all-but-hasn't-got-a-hope-of-a-snowball-in-hell that
is the problem with Internet Explorer bloatware/sieveware.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v

Microsoft is definitely advocating the "range of add-ons to suit different
needs" approach with Visio. However, Microsoft (more so than Visio
Corporation) sees these add-ons being provided by partners and 3rd parties.
We will make sure that Visio is a good platform for development, and we will
address the common issues that users must deal with across the board.

I am always willing to receive direct product feedback and suggestions for
features. Just remove "online" from my posting address for my real e-mail.
Please note that this is not a product support alias. If you are having
difficulties with Visio, your best bets are to post to the newsgroups or
contact Microsoft technical support.

--
Mark Nelson
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

"David Parker" wrote in message
...
Agreed. We do not need a technical version, we need the technical aspects
of Visio working properly first!
Mark - how do you want to receive comments?

"Pemo" wrote in message
...

"Mark Nelson [MS]" wrote:

Actually, a few of us are still around. And we speak our minds, but
that
doesn't mean that Visio will become exclusively targeted at technical
users.
The technical market is a difficult customer base for Microsoft to
reach
(being geared for the mass market), and this holds true for Visio as a
Microsoft product now. The best way for us to address technical
audiences
is to identify the features and issues that technical users have in
common
with others. A few examples: drawing mechanics, performance,
reporting,
data connectivity, layers. Let me hear about the tech-specific things
you
want fixed or improved too, but it is admittedly a difficult sell
internally.

I'm relieved to hear there is a voice of reason still there.

Of course we don't expect technical only; Visio needs to have features
across a spectrum.

I wonder if MS have considered following the very sensible lead of
Mozilla
Firefox browser - where there is a range of add-ons to suit different
needs
rather than the bloated
one-size-tries-to-fit-all-but-hasn't-got-a-hope-of-a-snowball-in-hell
that
is the problem with Internet Explorer bloatware/sieveware.

Pemo

--
,-._|\
/ Oz \ Melbourne
\_,--.x/ Australia
v