Visual Basic .NET Standard vs. SQL Server 2000 Developer Edition
-
I just purchased SQL Server 2000 Developer Edition yesterday from Amazon, and i'm disapointed. when i finally got it up an running, i went to the server explorer in my VB.NET Standard, and when i tried to connect to a database, it said: "Unable to connect to database. It is only possible to connect to SQL Server Desktop Engine databases and Microsoft Access databases with this version of Visual Studio." wtf is up with that? do i need Visual Studio Professional? Enterprise? or do i really have to spend the $2500 on Enterprise Architect? i thought the $50 price tag on SQL Server 2000 Developer Edition meant it was intended for low-budget developers, and considering the $109 price tag on VB.NET Standard, i thought they would go hand-in hand. apparently not. i can connect to the database programmatically just fine, but the inability to do it visualy is very dissapointing any help is appreciated. stephen
-
I just purchased SQL Server 2000 Developer Edition yesterday from Amazon, and i'm disapointed. when i finally got it up an running, i went to the server explorer in my VB.NET Standard, and when i tried to connect to a database, it said: "Unable to connect to database. It is only possible to connect to SQL Server Desktop Engine databases and Microsoft Access databases with this version of Visual Studio." wtf is up with that? do i need Visual Studio Professional? Enterprise? or do i really have to spend the $2500 on Enterprise Architect? i thought the $50 price tag on SQL Server 2000 Developer Edition meant it was intended for low-budget developers, and considering the $109 price tag on VB.NET Standard, i thought they would go hand-in hand. apparently not. i can connect to the database programmatically just fine, but the inability to do it visualy is very dissapointing any help is appreciated. stephen
medicenpringles wrote: but the inability to do it visualy is very dissapointing You're not missing much. I prefer to do my database work in the Enterprise Manager of SQL Server anyway. Hand coding the database code is a much cleaner approach. All your code is contained to exactly where you put it instead of where the Designer wants to put it. The Standard Edition of Visual Studio won't connect the Server Explorer to SQL Server. It's limited to the desktop databases only. Visual Studio Professional and above will work though. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
medicenpringles wrote: but the inability to do it visualy is very dissapointing You're not missing much. I prefer to do my database work in the Enterprise Manager of SQL Server anyway. Hand coding the database code is a much cleaner approach. All your code is contained to exactly where you put it instead of where the Designer wants to put it. The Standard Edition of Visual Studio won't connect the Server Explorer to SQL Server. It's limited to the desktop databases only. Visual Studio Professional and above will work though. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
well to be honest, the only real reason i got Developer Edition was for the enterprise manager. if i only used the free Desktop Engine, would Enterprise Manager sill work with maintaining the databases on the Desktop Engine?
-
well to be honest, the only real reason i got Developer Edition was for the enterprise manager. if i only used the free Desktop Engine, would Enterprise Manager sill work with maintaining the databases on the Desktop Engine?
Frankly, I've never tried it. I think it would work, but it might take a couple of hacks to get it there. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome