By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,916 Members | 1,286 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,916 IT Pros & Developers. It's quick & easy.

sql server 2000

P: n/a
I have loaded on my computer Visual Studio.Net Enterprise Architect
2002. I want to load Visual Studio.Net Enterprise Architect 2003. I
really don't need VS.Net 2002 and was going to uninstall it from my
computer. First question do I need to know of any problems that might
occur if I uninstall VS.Net 2002 then install VS.Net 2003. The second
question, when I installed VS.Net 2002 I also installed SQL Server
2000 Developer. If I uninstall VS.Net 2002 will I lose SQL Server
2000 Developer. I hear SQL Server 2000 Developer does not come with
the VS.Net 2003. Oh I know I'm pressing my luck but does the VS.Net
2003 come with a water down version of Crystal Reports like VS.Net
2002 Thanks for any help.
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I only have vs.net3 on my primary workstation, but vs.net2 and vs.net3
on both my laptop and home pc. vs.net3 does not have crystal rpts like
vs.net2, but it appears like crystal rpts went away when I loaded
vs.net3. Maybe it is still there somewhere (but I don't use crystal
rpts). I just don't see menus or icons for crystal rpts anymore. Yeah,
and I don't think you get any version of Sql Server with vs.net3. If
you have the room, I would not uninstall vs.net2. I did not have any
problems having both vs.net2 and vs.net3 (and also vs6) on these
machines. As for sql Server, I have personal edition loaded on both of
these guys (and Sql Server 2k Enterprise on my work server - which is
also my primary workstation). Sql Server Enterprise will only run on a
server computer. This won't interfere with any version of Office either
(97, 2k, 2002). I have em all.

And a plug for vs.net3, I used to write lots of ActiveX dlls in VB6 to
use in Access and Excel. They aren't ActiveX in DotNet. And way easier
to create and manipulate. Not as touchy as the VB6 version. The best
part is that you can create DotNet dlls to add DotNet functionality to
your Access and Excel Apps. No more looping to push and pull data
between Office and Sql Server (or Oracle). You can use the DotNet
dataAdapters. And if you do ASP, Asp.Net blows com Asp out of the water
in functionality and ease of programming. Asp.Net blows DreamWeaver out
of the water too.

Rich

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.