We are currently migrating our sequel 6.5 databases to sequel 2005
We have a handful of vb6 apps that connect to the current 6.5 database.
Can anyone recommend the "best practice" for connecting vb6 apps to sequel
2005 databases ?
Thanks in advance.
Sure, but my books only discuss SQL Server, not "sequel" ;)
The ConnectionString used to connect to a SQL Server 2005 engine is very
similar to the one you're using to access a SQL Server 6.5 engine with a
couple of differences:
* First, use the new SNAC (SQL Native Client) provider instead of
SQLOLEDB. This is installed with all versions of SQL Server 2005. See
http://msdn2.microsoft.com/en-us/data/aa937705.aspx for more information.
* Next, consider that SQL Server 2005 can be installed as a named
instance. This permits you to have both SQL Server 6.5 and SQL Server 2005
installed on the same server. If you have used a named instance, you can
address it using the machine/server name followed by the instance name--like
this:
Dim con As New ADODB.Connection
con.ConnectionString = "Provider=SQLNCLI;" _
& "Server=MyServer/MySQLServer2005InstanceName;" _
& "Database=AdventureWorks;" _
& "Integrated Security=SSPI;" _
& "DataTypeCompatibility=80;" _
& "MARS Connection=True;"
con.Open
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"PhilEvans" <PhilEvans@.discussions.microsoft.com> wrote in message
news:409E884C-5165-48D1-A88B-77E802BCFC40@.microsoft.com...
> We are currently migrating our sequel 6.5 databases to sequel 2005
> We have a handful of vb6 apps that connect to the current 6.5 database.
> Can anyone recommend the "best practice" for connecting vb6 apps to sequel
> 2005 databases ?
> Thanks in advance.
>
Showing posts with label current. Show all posts
Showing posts with label current. Show all posts
Friday, February 17, 2012
Connecting a vb6 app to a sequel 2005 database
We are currently migrating our sequel 6.5 databases to sequel 2005
We have a handful of vb6 apps that connect to the current 6.5 database.
Can anyone recommend the "best practice" for connecting vb6 apps to sequel
2005 databases ?
Thanks in advance.Sure, but my books only discuss SQL Server, not "sequel" ;)
The ConnectionString used to connect to a SQL Server 2005 engine is very
similar to the one you're using to access a SQL Server 6.5 engine with a
couple of differences:
* First, use the new SNAC (SQL Native Client) provider instead of
SQLOLEDB. This is installed with all versions of SQL Server 2005. See
http://msdn2.microsoft.com/en-us/data/aa937705.aspx for more information.
* Next, consider that SQL Server 2005 can be installed as a named
instance. This permits you to have both SQL Server 6.5 and SQL Server 2005
installed on the same server. If you have used a named instance, you can
address it using the machine/server name followed by the instance name--like
this:
Dim con As New ADODB.Connection
con.ConnectionString = "Provider=SQLNCLI;" _
& "Server=MyServer/MySQLServer2005InstanceName;" _
& "Database=AdventureWorks;" _
& "Integrated Security=SSPI;" _
& "DataTypeCompatibility=80;" _
& "MARS Connection=True;"
con.Open
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"PhilEvans" <PhilEvans@.discussions.microsoft.com> wrote in message
news:409E884C-5165-48D1-A88B-77E802BCFC40@.microsoft.com...
> We are currently migrating our sequel 6.5 databases to sequel 2005
> We have a handful of vb6 apps that connect to the current 6.5 database.
> Can anyone recommend the "best practice" for connecting vb6 apps to sequel
> 2005 databases ?
> Thanks in advance.
>
We have a handful of vb6 apps that connect to the current 6.5 database.
Can anyone recommend the "best practice" for connecting vb6 apps to sequel
2005 databases ?
Thanks in advance.Sure, but my books only discuss SQL Server, not "sequel" ;)
The ConnectionString used to connect to a SQL Server 2005 engine is very
similar to the one you're using to access a SQL Server 6.5 engine with a
couple of differences:
* First, use the new SNAC (SQL Native Client) provider instead of
SQLOLEDB. This is installed with all versions of SQL Server 2005. See
http://msdn2.microsoft.com/en-us/data/aa937705.aspx for more information.
* Next, consider that SQL Server 2005 can be installed as a named
instance. This permits you to have both SQL Server 6.5 and SQL Server 2005
installed on the same server. If you have used a named instance, you can
address it using the machine/server name followed by the instance name--like
this:
Dim con As New ADODB.Connection
con.ConnectionString = "Provider=SQLNCLI;" _
& "Server=MyServer/MySQLServer2005InstanceName;" _
& "Database=AdventureWorks;" _
& "Integrated Security=SSPI;" _
& "DataTypeCompatibility=80;" _
& "MARS Connection=True;"
con.Open
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"PhilEvans" <PhilEvans@.discussions.microsoft.com> wrote in message
news:409E884C-5165-48D1-A88B-77E802BCFC40@.microsoft.com...
> We are currently migrating our sequel 6.5 databases to sequel 2005
> We have a handful of vb6 apps that connect to the current 6.5 database.
> Can anyone recommend the "best practice" for connecting vb6 apps to sequel
> 2005 databases ?
> Thanks in advance.
>
Sunday, February 12, 2012
Connect to SQL2000 & SQL 2005
Our current program use ADO to connect oto SQL2000 and run fine.
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:
> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:
> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
Subscribe to:
Posts (Atom)