Maybe off topic question

[Ken Tucker [MVP]]

Hi,

They should peacefully coexist.

Ken
--------------------
OK, I didn't know where to start to ask for help with this question, but
here goes. I have a Windows 2000 Pro computer with a single partition on
the hard drive. I want to installed the following software on it:

Microsoft Office 2000 Professional (for Access work)
Microsoft Office 2003 Professional (for Access work)
Microsoft Visual Basic version 6
Microsoft Visual Studio 2003 Professional ( for .Net work)

Will these programs conflict with each other? If so, what would be a better
solution?

Thanks,
Thomas

 

[Ken Dopierala Jr.]

Hi Thomas,

I don't know about the two offices working together but I would imagine they
would be fine. When you install make sure you install in this order:

Office 2000
Office 2003
VB6
VS.Net

I've seen problems on system where Office XP or VB6 were installed before
VS.Net. As for installing Office 2000 before Office 2003 I put them in that
order because it just sounded logical. Good luck! Ken.

 

[chanmmn]

I have VB6 and VB.NET in my PC. I did get some error when I try to coexist
Office 2000 and Office XP previously. But why do you need 2 offices in the
same PC?

chanmm

 

[TD]

OK, I didn't know where to start to ask for help with this question, but
here goes. I have a Windows 2000 Pro computer with a single partition on
the hard drive. I want to installed the following software on it:

Microsoft Office 2000 Professional (for Access work)
Microsoft Office 2003 Professional (for Access work)
Microsoft Visual Basic version 6
Microsoft Visual Studio 2003 Professional ( for .Net work)

Will these programs conflict with each other? If so, what would be a better
solution?

Thanks,
Thomas

 

[Herfried K. Wagner [MVP]]

[...]

Notice that your system's date/time settings are wrong. Please correct
them.

 

[Adam Goossens]

I haven't experienced them myself, but some of my colleagues have
reported issues when attempting to co-exist Office 2000 and Office 2003.
Specifically in the area of the object libraries that are used. They
report problems with Access 2000 defaulting to the Access 2003 object
libraries no matter what the Reference settings are.

I'm quite sceptical about this since it makes no sense to me what so
ever. For the moment I've got Office 2000 set up on a Virtual PC
(attempting to mimic the client setup as best as possible). I'll have to
test out their claims one day. Heck, I'll do it on Thursday (public
holiday tomorrow - yay!)

As for VB6.0 and VS.NET, I've had no troubles at all. The two work side
by side without complaint. So far. *touch wood*

Regards,
-Adam.

 

[Adam Goossens]

The company I work for does most of it's development in Access 2003
using the Access 2000 file format.

The biggest problem with that is that some of our clients use Access
2000 - and Access 2000 is missing some important features that Access
2003 contains (i.e. OpenArgs for reports). I'm still bemused as to why
Access 2003-specific features aren't disabled when using the Access 2000
file format. But, that's the breaks. Then again, I could force the
application to use the Access 2000 object library....but I digress.

I almost got caught one day - I was going to deliver a DB to a client
and I was unaware they ran Access 2000 (I was certain it was '03).
Unfortunately I'd been using the Report.OpenArgs property for a while,
so you can bet my application truly borked itself when I tested it under
2000 (yeah, I know, my bad on the testing there).

Needless to say that hasn't happened since

Regards,
-Adam.