|
|
You're in the
vb.net upgrade
group:VB.Net 2003 Standard edition limitations
vb.net upgrade:
with it. The webpage says it will talk to SQL Server, but it won't. MS sems to have blocked that out. I bought it to learn how to use VB.net and most of my work envolves SQL server. Is there some registry value I could tweek to fix this? I did notice I can link an Access db table to SQL and connect ot the Access DB, which effectively passes me through, But I need to play with stored Procs. Thanks in advance twscannell@hotmail.com
TW,
What specifically is the error that you are getting that you seem to think it will not talk to SQL Server? Is the error in the IDE? Is the error in the compiling of the code you entered? Or is the error in the execution of the code that was compiled? Of course I am presuming that you actually have an SQL Server that you are able to talk to with other tools. Hope this helps Jay [quoted text, click to view] "TW Scannell" <twscannell@hotmail.com> wrote in message news:eOulB8boDHA.3732@tk2msftngp13.phx.gbl... > I bought the standard version in July or so and finaly got around to playing > with it. The webpage says it will talk to SQL Server, but it won't. MS sems > to have blocked that out. I bought it to learn how to use VB.net and most of > my work envolves SQL server. Is there some registry value I could tweek to > fix this? I did notice I can link an Access db table to SQL and connect ot > the Access DB, which effectively passes me through, But I need to play with > stored Procs. > > Thanks in advance > twscannell@hotmail.com > >
Thanks for responding,
This is a definitely a limitation of the Standard edition, At least the one I have. I am using the Server Explorer. I create a new connection object to a SQL 7.0 database that I have used extensively with VB6.0. I test the connection and it connects fine. In the wizard, when I say "OK" to the create connection, I get a message from "Server Explorer" that says: "Unable to Connect to database: It is only possible to connect to SQL Server Desktop engine databases or Microsoft Access databases with this version of Visual Studio" If you go to Amazon.com's page for VB.NET standard Edition and read the reviews, you will see that other people have run into the same limitations. Maybe I have an older version. There used to be a page on the MS website that listed the different features of Standard vs Professional versions. I can't find that now, so maybe there is a newer version of VB.net that doesn't have these limits. I bought this in July. The version for the "Development Environment" is 7.1.3088. the Framework is 1.1.4332 Thanks Again [quoted text, click to view] "TW Scannell" <twscannell@hotmail.com> wrote in message news:eOulB8boDHA.3732@tk2msftngp13.phx.gbl... > I bought the standard version in July or so and finaly got around to playing > with it. The webpage says it will talk to SQL Server, but it won't. MS sems > to have blocked that out. I bought it to learn how to use VB.net and most of > my work envolves SQL server. Is there some registry value I could tweek to > fix this? I did notice I can link an Access db table to SQL and connect ot > the Access DB, which effectively passes me through, But I need to play with > stored Procs. > > Thanks in advance > twscannell@hotmail.com > >
So what youare saying is I can connect to a SQL server if I don't use the
Server Explorer? That works for me in it is exactly what I want to do. I will give it a try and let you know. Thanks TW Scannell [quoted text, click to view] "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message news:bo5em9$17mfnp$2@ID-208219.news.uni-berlin.de... > * "TW Scannell" <twscannell@hotmail.com> scripsit: > > I bought the standard version in July or so and finaly got around to playing > > with it. The webpage says it will talk to SQL Server, but it won't. MS sems > > to have blocked that out. I bought it to learn how to use VB.net and most of > > my work envolves SQL server. Is there some registry value I could tweek to > > fix this? I did notice I can link an Access db table to SQL and connect ot > > the Access DB, which effectively passes me through, But I need to play with > > stored Procs. > > There should be no limitation if you create connection/... objects in > the code. Are you using the "Server Explorer" to create the connection? > Which error message do you get? > > -- > Herfried K. Wagner > MVP · VB Classic, VB.NET > <http://www.mvps.org/dotnet> > > Improve your quoting style: > <http://learn.to/quote> > <http://www.plig.net/nnq/nquote.html>
Could you please give me the "ConnectionString" format for the login and
password data pairs? login=duffus? User="duffus"? Username="duffus"? pwd=chopper? Password="Chopper"? Thanks again [quoted text, click to view] "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message news:bo5em9$17mfnp$2@ID-208219.news.uni-berlin.de... > * "TW Scannell" <twscannell@hotmail.com> scripsit: > > I bought the standard version in July or so and finaly got around to playing > > with it. The webpage says it will talk to SQL Server, but it won't. MS sems > > to have blocked that out. I bought it to learn how to use VB.net and most of > > my work envolves SQL server. Is there some registry value I could tweek to > > fix this? I did notice I can link an Access db table to SQL and connect ot > > the Access DB, which effectively passes me through, But I need to play with > > stored Procs. > > There should be no limitation if you create connection/... objects in > the code. Are you using the "Server Explorer" to create the connection? > Which error message do you get? > > -- > Herfried K. Wagner > MVP · VB Classic, VB.NET > <http://www.mvps.org/dotnet> > > Improve your quoting style: > <http://learn.to/quote> > <http://www.plig.net/nnq/nquote.html>
Thanks to VB.net, I am unemployed. Now I am supposed to spend 2 weeks
unemployment checks to buy the product that outdated me. Life is full of parodies and Microsoft is getting rich from many of them. Thanks for the help. TW [quoted text, click to view] "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow@email.msn.com> wrote in message http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/news:OZNjNyhoDHA.1632@TK2MSFTNGP10.phx.gbl... > TW, > > This is a definitely a limitation of the Standard edition, At least the > one > > I have. I am using the Server Explorer. I create a new connection object > to a SQL > Correct, Server Explorer in VB.NET Standard edition is limited! > > However you can still use the System.Data.SqlClient.SqlConnection class to > connect to an SQL Server, as it is part of the Framework itself. > > frlrfSystemDataSqlClientSqlConnectionClassTopic.asp [quoted text, click to view] > > The 'fix' for Server Explorer is to upgrade to VB.NET Professional or > Enterprise Editions, or simply do not use the Server Explorer. I would > recommend upgrading to one of the Enterprise versions. > > Hope this helps > Jay > > "TW Scannell" <twscannell@hotmail.com> wrote in message > news:%23Ti26LhoDHA.964@TK2MSFTNGP10.phx.gbl... > > Thanks for responding, > > This is a definitely a limitation of the Standard edition, At least the > one > > I have. > > I am using the Server Explorer. I create a new connection object to a SQL > > 7.0 database that I have used extensively with VB6.0. I test the > connection > > and it connects fine. In the wizard, when I say "OK" to the create > > connection, I get a message from "Server Explorer" that says: > > "Unable to Connect to database: > > It is only possible to connect to SQL Server Desktop engine databases or > > Microsoft Access databases with this version of Visual Studio" > > If you go to Amazon.com's page for VB.NET standard Edition and read the > > reviews, you will see that other people have run into the same > limitations. > > Maybe I have an older version. There used to be a page on the MS website > > that listed the different features of Standard vs Professional versions. I > > can't find that now, so maybe there is a newer version of VB.net that > > doesn't have these limits. I bought this in July. The version for the > > "Development Environment" is 7.1.3088. the Framework is 1.1.4332 > > > > Thanks Again > > > > "TW Scannell" <twscannell@hotmail.com> wrote in message > > news:eOulB8boDHA.3732@tk2msftngp13.phx.gbl... > > > I bought the standard version in July or so and finaly got around to > > playing > > > with it. The webpage says it will talk to SQL Server, but it won't. MS > > sems > > > to have blocked that out. I bought it to learn how to use VB.net and > most > > of > > > my work envolves SQL server. Is there some registry value I could tweek > to > > > fix this? I did notice I can link an Access db table to SQL and connect > ot > > > the Access DB, which effectively passes me through, But I need to play > > with > > > stored Procs. > > > > > > Thanks in advance > > > twscannell@hotmail.com > > > > > > > > > > > >
TW,
[quoted text, click to view] > This is a definitely a limitation of the Standard edition, At least the to a SQLone > I have. I am using the Server Explorer. I create a new connection object Correct, Server Explorer in VB.NET Standard edition is limited! However you can still use the System.Data.SqlClient.SqlConnection class to connect to an SQL Server, as it is part of the Framework itself. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemDataSqlClientSqlConnectionClassTopic.asp The 'fix' for Server Explorer is to upgrade to VB.NET Professional or Enterprise Editions, or simply do not use the Server Explorer. I would recommend upgrading to one of the Enterprise versions. Hope this helps Jay [quoted text, click to view] "TW Scannell" <twscannell@hotmail.com> wrote in message news:%23Ti26LhoDHA.964@TK2MSFTNGP10.phx.gbl... > Thanks for responding, > This is a definitely a limitation of the Standard edition, At least the one > I have. > I am using the Server Explorer. I create a new connection object to a SQL > 7.0 database that I have used extensively with VB6.0. I test the connection > and it connects fine. In the wizard, when I say "OK" to the create > connection, I get a message from "Server Explorer" that says: > "Unable to Connect to database: > It is only possible to connect to SQL Server Desktop engine databases or > Microsoft Access databases with this version of Visual Studio" > If you go to Amazon.com's page for VB.NET standard Edition and read the > reviews, you will see that other people have run into the same limitations. > Maybe I have an older version. There used to be a page on the MS website > that listed the different features of Standard vs Professional versions. I > can't find that now, so maybe there is a newer version of VB.net that > doesn't have these limits. I bought this in July. The version for the > "Development Environment" is 7.1.3088. the Framework is 1.1.4332 > > Thanks Again > > "TW Scannell" <twscannell@hotmail.com> wrote in message > news:eOulB8boDHA.3732@tk2msftngp13.phx.gbl... > > I bought the standard version in July or so and finaly got around to > playing > > with it. The webpage says it will talk to SQL Server, but it won't. MS > sems > > to have blocked that out. I bought it to learn how to use VB.net and most > of > > my work envolves SQL server. Is there some registry value I could tweek to > > fix this? I did notice I can link an Access db table to SQL and connect ot > > the Access DB, which effectively passes me through, But I need to play > with > > stored Procs. > > > > Thanks in advance > > twscannell@hotmail.com > > > > > >
I finally got it to work by creating the connection in code. Thanks to all.
The trick seems to be the addition of the data pair "Trusted_Connection=False" All of the samples that I looked at were using a trusted connection, which is apparently the default. Even though I included the User Id and Password data pairs, they were apparently ignored until I added the "Trusted_Connection=False" pair. Here is the connection string that finally worked: Dim ConnectionString As String = "Server=""ServerName"";workstation id=""QUAIL-SPRINGS"";packet size=4096;integrated security=SSPI;data source=""ServerName\DataBaseName"";persist security info=False;initial catalog=pubs;Trusted_Connection=False;User ID=""SomeUserName"";Password=""drumstix""" Thanks again. TW [quoted text, click to view] "TW Scannell" <twscannell@hotmail.com> wrote in message news:eOulB8boDHA.3732@tk2msftngp13.phx.gbl... > I bought the standard version in July or so and finaly got around to playing > with it. The webpage says it will talk to SQL Server, but it won't. MS sems > to have blocked that out. I bought it to learn how to use VB.net and most of > my work envolves SQL server. Is there some registry value I could tweek to > fix this? I did notice I can link an Access db table to SQL and connect ot > the Access DB, which effectively passes me through, But I need to play with > stored Procs. > > Thanks in advance > twscannell@hotmail.com > >
TW,
As I stated: you can use the SqlConnection object from Code with VB.NET Standard. I even gave you a link with an example. Hope this helps Jay [quoted text, click to view] "TW Scannell" <twscannell@hotmail.com> wrote in message news:%23D9ScaioDHA.2188@TK2MSFTNGP11.phx.gbl... > Thanks to VB.net, I am unemployed. Now I am supposed to spend 2 weeks > unemployment checks to buy the product that outdated me. Life is full of > parodies and Microsoft is getting rich from many of them. > > Thanks for the help. > > TW > > > "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow@email.msn.com> wrote in message > news:OZNjNyhoDHA.1632@TK2MSFTNGP10.phx.gbl... > > TW, > > > This is a definitely a limitation of the Standard edition, At least the > > one > > > I have. I am using the Server Explorer. I create a new connection object > > to a SQL > > Correct, Server Explorer in VB.NET Standard edition is limited! > > > > However you can still use the System.Data.SqlClient.SqlConnection class to > > connect to an SQL Server, as it is part of the Framework itself. > > > > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/ > frlrfSystemDataSqlClientSqlConnectionClassTopic.asp > > > > The 'fix' for Server Explorer is to upgrade to VB.NET Professional or > > Enterprise Editions, or simply do not use the Server Explorer. I would > > recommend upgrading to one of the Enterprise versions. > > > > Hope this helps > > Jay > > > > "TW Scannell" <twscannell@hotmail.com> wrote in message > > news:%23Ti26LhoDHA.964@TK2MSFTNGP10.phx.gbl... > > > Thanks for responding, > > > This is a definitely a limitation of the Standard edition, At least the > > one > > > I have. > > > I am using the Server Explorer. I create a new connection object to a > SQL > > > 7.0 database that I have used extensively with VB6.0. I test the > > connection > > > and it connects fine. In the wizard, when I say "OK" to the create > > > connection, I get a message from "Server Explorer" that says: > > > "Unable to Connect to database: > > > It is only possible to connect to SQL Server Desktop engine databases or > > > Microsoft Access databases with this version of Visual Studio" > > > If you go to Amazon.com's page for VB.NET standard Edition and read the > > > reviews, you will see that other people have run into the same > > limitations. > > > Maybe I have an older version. There used to be a page on the MS website > > > that listed the different features of Standard vs Professional versions. > I > > > can't find that now, so maybe there is a newer version of VB.net that > > > doesn't have these limits. I bought this in July. The version for the > > > "Development Environment" is 7.1.3088. the Framework is 1.1.4332 > > > > > > Thanks Again > > > > > > "TW Scannell" <twscannell@hotmail.com> wrote in message > > > news:eOulB8boDHA.3732@tk2msftngp13.phx.gbl... > > > > I bought the standard version in July or so and finaly got around to > > > playing > > > > with it. The webpage says it will talk to SQL Server, but it won't. MS > > > sems > > > > to have blocked that out. I bought it to learn how to use VB.net and > > most > > > of > > > > my work envolves SQL server. Is there some registry value I could > tweek > > to > > > > fix this? I did notice I can link an Access db table to SQL and > connect > > ot > > > > the Access DB, which effectively passes me through, But I need to play > > > with > > > > stored Procs. > > > > > > > > Thanks in advance > > > > twscannell@hotmail.com > > > > > > > > > > > > > > > > > > > >
* "TW Scannell" <twscannell@hotmail.com> scripsit:
[quoted text, click to view] > I bought the standard version in July or so and finaly got around to playing > with it. The webpage says it will talk to SQL Server, but it won't. MS sems > to have blocked that out. I bought it to learn how to use VB.net and most of > my work envolves SQL server. Is there some registry value I could tweek to > fix this? I did notice I can link an Access db table to SQL and connect ot > the Access DB, which effectively passes me through, But I need to play with > stored Procs. There should be no limitation if you create connection/... objects in the code. Are you using the "Server Explorer" to create the connection? Which error message do you get? -- Herfried K. Wagner MVP · VB Classic, VB.NET <http://www.mvps.org/dotnet> Improve your quoting style: <http://learn.to/quote>
* "TW Scannell" <twscannell@hotmail.com> scripsit:
[quoted text, click to view] > So what youare saying is I can connect to a SQL server if I don't use the > Server Explorer? That works for me in it is exactly what I want to do. I > will give it a try and let you know. You will have to create the connection object in the source code. Information on connection strings for SQL Server: <http://www.connectionstrings.com/> -> "SQL Server" -- Herfried K. Wagner MVP · VB Classic, VB.NET <http://www.mvps.org/dotnet>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
March 2007
April 2007
May 2007
July 2007
August 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |