VS.NET 2003 installation niggles

[Dave S]

I installed VS.NET 2003 and the framework on Windows XP Pro and it seems to
have caused problems with VB6 projects which use ODBC data controls to
connect to MS Access XP. I've also been told that this has happened to
someone else at work who had alot of problems with VB6 projects after
installation.
When I installed VS.NET 2003, I uninstalled the previous version of VS.NET
and the framework before installing VS.NET 2003.

The VS.NET 2003 installation also managed to screw up my JVM, so when I go
to sites which use this, my browser now tells me to download it every time
even though I've actually been to the Sun site and downloaded it and the
Java site thinks it's installed on my PC when I go back to the download
page.

Fortunately, I only had one VB6 project which I relied on being compatible
with VS.NET 2003 and according to online documentation VB6 should still be
ok after installing VS.NET 2003, but it doesn't look to be the case.

Any ideas how I can fix these 2 issues, or should I uninstall VS.NET 2003
and attempt to go back to the previous version which didn't have these
problems ?

 

[Scott M.]

I have not heard of any compatability problems with VB6 and .NET. .NET was
designed to co-exist with VB 6. It's true that by installing .NET, you will
upgrading your MDAC and you *may* just need to re-work your db code to
reflect the updated driver. But, going to Access wouldn't give you such
troubles.

I can't think of any reason why .NET would interfere in any way with your
JVM.

It sounds as if you either have a bad install or there is some other issue.