Multiple versions of Visio on the same machine?

[vbecker]

Does anyone know if you can run multiple versions of Visio on the same machine? Our users logon to Terminal Servers for their desktop (almost nothing is installed locally) so all user applications are installed on the Terminal Servers, not the workstations. Some of our users need Visio Professional and some only need Visio Standard. Can anyone tell me if both of these versions could exist on the same server at the same time (by installing them into different directories)

 

[billyjoe jimbob]

I have a somewhat similar problem.

I used Visio2k2 for quite a while before upgrading to Visiio2k3. I have to be able to import Microstation .dgn files, review them, mark them up and repost them as Microstation files again or sometimes as just about anything else; .ppt, .pdf, .doc, etc, ad nauseum

Problem is, though, that because 2k3 doesn't support .dgn any more (whoopie!!) I've had to reload 2k2 back onto the same machine that also has 2k3 residing on it. OK

Problem is that all of my file associations are AFU. And I can't reassign them for some screwy reason. Pleasantly, some of the previously associated files still respond with a double click but some don't. Seemingly, Windows can't differentiate between the two versions as being different installations

Also, when I double click an old 2k2 Visio file, instead of it coming up using the same version of Visio, it seems to kinda be a little iffy. Sometimes if comes up using the 2k2 Visio and sometimes it comes up using the 2k3 version

Also, when I start 2k3 after running a 2k2 session, I get all kinds of windows messages concerning "Installing Visio 2k3, yadda, etc.". Same thing happens in the other direction, i.e. running 2k2 after running 2k3

I'm running Windows 2k 5.00.2195, SP4

C'mon guys, I'm dyin' out here. Gimme shelter...

 

[Al Edlund]

I also have multiple versions installed.

a.) they do in fact reinstall/reconfigure themselves when you flip between
them. This is a known issue
b.) there were a lot of things that disappeared when v2003 came out, thus
the need for some of us to
keep multiple versions. Not a lot of promise in getting them back.
c.) if you touch a file with V2003 and don't save it as V2002 it will
probably be saved as V2003, thus
the reason for files bouncing between levels. You can save to
V2000/V2002 from V2003, so some
should be recoverable

Al

I have a somewhat similar problem.

I used Visio2k2 for quite a while before upgrading to Visiio2k3. I have to

be able to import Microstation .dgn files, review them, mark them up and
repost them as Microstation files again or sometimes as just about anything
else; .ppt, .pdf, .doc, etc, ad nauseum.

Problem is, though, that because 2k3 doesn't support .dgn any more

(whoopie!!) I've had to reload 2k2 back onto the same machine that also has
2k3 residing on it. OK.

Problem is that all of my file associations are AFU. And I can't reassign

them for some screwy reason. Pleasantly, some of the previously associated
files still respond with a double click but some don't. Seemingly, Windows
can't differentiate between the two versions as being different
installations.

Also, when I double click an old 2k2 Visio file, instead of it coming up

using the same version of Visio, it seems to kinda be a little iffy.
Sometimes if comes up using the 2k2 Visio and sometimes it comes up using
the 2k3 version.

Also, when I start 2k3 after running a 2k2 session, I get all kinds of

windows messages concerning "Installing Visio 2k3, yadda, etc.". Same thing
happens in the other direction, i.e. running 2k2 after running 2k3.