Connecting from Windows (VB6.0) app to SQL on Internet

Hello,
We have a client-server application written in VB 6.0 that connects to a
SQL Server instance on the local network. We're interested to know if we are
able to use our same VB 6.0 application but connect to a SQL Server that is
hosted on a web domain. That is, if we have our SQL database hosted by a
service provider on the internet, are we able to simply change our connection
string in our application so that we connect to this SQL Server instance and
not the SQL Server on the LAN? If possible we hope to avoid having to
rewrite our application as a .NET application...
Thanks.
Yes that's doable. It's not unusual to develop applications
locally and then change the connection string to access the
"live" database.
-Sue
On Fri, 21 Jan 2005 01:17:02 -0800, aglanz
<aglanz@.discussions.microsoft.com> wrote:

>Hello,
> We have a client-server application written in VB 6.0 that connects to a
>SQL Server instance on the local network. We're interested to know if we are
>able to use our same VB 6.0 application but connect to a SQL Server that is
>hosted on a web domain. That is, if we have our SQL database hosted by a
>service provider on the internet, are we able to simply change our connection
>string in our application so that we connect to this SQL Server instance and
>not the SQL Server on the LAN? If possible we hope to avoid having to
>rewrite our application as a .NET application...
>Thanks.
|||In your connection, you would specify the IP address of the hosting server.
http://www.able-consulting.com/ADO_Conn.htm
"aglanz" <aglanz@.discussions.microsoft.com> wrote in message
news:9E786AE0-5D0C-48DA-86BC-B39F9871CC03@.microsoft.com...
> Hello,
> We have a client-server application written in VB 6.0 that connects to
a
> SQL Server instance on the local network. We're interested to know if we
are
> able to use our same VB 6.0 application but connect to a SQL Server that
is
> hosted on a web domain. That is, if we have our SQL database hosted by a
> service provider on the internet, are we able to simply change our
connection
> string in our application so that we connect to this SQL Server instance
and
> not the SQL Server on the LAN? If possible we hope to avoid having to
> rewrite our application as a .NET application...
> Thanks.
|||Hi,
Can you please let me know how did you connect vb6.0 with MS-SQLServer in a network(LAN)?Iam facing a problem of connecting MS-SQLServer with vb6.0 on the network what i mean is clients cant access the sqlserver?
Regards
Jack

Quote:

Originally posted by aglanz
Hello,
We have a client-server application written in VB 6.0 that connects to a
SQL Server instance on the local network. We're interested to know if we are
able to use our same VB 6.0 application but connect to a SQL Server that is
hosted on a web domain. That is, if we have our SQL database hosted by a
service provider on the internet, are we able to simply change our connection
string in our application so that we connect to this SQL Server instance and
not the SQL Server on the LAN? If possible we hope to avoid having to
rewrite our application as a .NET application...
Thanks.

Connecting from Windows (VB6.0) app to SQL on Internet

Hello,
We have a client-server application written in VB 6.0 that connects to a
SQL Server instance on the local network. We're interested to know if we ar
e
able to use our same VB 6.0 application but connect to a SQL Server that is
hosted on a web domain. That is, if we have our SQL database hosted by a
service provider on the internet, are we able to simply change our connectio
n
string in our application so that we connect to this SQL Server instance and
not the SQL Server on the LAN? If possible we hope to avoid having to
rewrite our application as a .NET application...
Thanks.Yes that's doable. It's not unusual to develop applications
locally and then change the connection string to access the
"live" database.
-Sue
On Fri, 21 Jan 2005 01:17:02 -0800, aglanz
<aglanz@.discussions.microsoft.com> wrote:

>Hello,
> We have a client-server application written in VB 6.0 that connects to
a
>SQL Server instance on the local network. We're interested to know if we a
re
>able to use our same VB 6.0 application but connect to a SQL Server that is
>hosted on a web domain. That is, if we have our SQL database hosted by a
>service provider on the internet, are we able to simply change our connecti
on
>string in our application so that we connect to this SQL Server instance an
d
>not the SQL Server on the LAN? If possible we hope to avoid having to
>rewrite our application as a .NET application...
>Thanks.|||In your connection, you would specify the IP address of the hosting server.
http://www.able-consulting.com/ADO_Conn.htm
"aglanz" <aglanz@.discussions.microsoft.com> wrote in message
news:9E786AE0-5D0C-48DA-86BC-B39F9871CC03@.microsoft.com...
> Hello,
> We have a client-server application written in VB 6.0 that connects to
a
> SQL Server instance on the local network. We're interested to know if we
are
> able to use our same VB 6.0 application but connect to a SQL Server that
is
> hosted on a web domain. That is, if we have our SQL database hosted by a
> service provider on the internet, are we able to simply change our
connection
> string in our application so that we connect to this SQL Server instance
and
> not the SQL Server on the LAN? If possible we hope to avoid having to
> rewrite our application as a .NET application...
> Thanks.

Connect Two Databases Together

I am interested in having two databases that are on the same server
connected together. I have the individual databases but I also want to have
a common database that keeps stored procedures to do things such as changing
password. I don't want to cut and paste them into each database each time
plus if I ever made a change I am creating a lot of work for myself.
Users would have the same login and password for the two databases. What is
the simpliest way to set this up?
Thanks
Can
There are several options, ranging from linking tables, to managing them
both with common scripts. It really depends on why you want them to be
separate databases instead of a single database, and then why you want
certain things in common -- ease of maintenance, security, or something
else?
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Can" <Can@.discussions.microsoft.com> wrote in message
news:74E21166-FD11-46E5-AF30-A7415D2D331D@.microsoft.com...
> I am interested in having two databases that are on the same server
> connected together. I have the individual databases but I also want to
> have
> a common database that keeps stored procedures to do things such as
> changing
> password. I don't want to cut and paste them into each database each time
> plus if I ever made a change I am creating a lot of work for myself.
> Users would have the same login and password for the two databases. What
> is
> the simpliest way to set this up?
> Thanks
> Can
>
|||I am looking to llink stored procedures, not tables, from one database to
another for ease of maintenance. What direction do you suggest?
"Jeff A. Stucker" wrote:

> There are several options, ranging from linking tables, to managing them
> both with common scripts. It really depends on why you want them to be
> separate databases instead of a single database, and then why you want
> certain things in common -- ease of maintenance, security, or something
> else?
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Senior Consultant
> www.rapidigm.com
> "Can" <Can@.discussions.microsoft.com> wrote in message
> news:74E21166-FD11-46E5-AF30-A7415D2D331D@.microsoft.com...
>
>

Connect Two Databases Together

I am interested in having two databases that are on the same server
connected together. I have the individual databases but I also want to have
a common database that keeps stored procedures to do things such as changing
password. I don't want to cut and paste them into each database each time
plus if I ever made a change I am creating a lot of work for myself.
Users would have the same login and password for the two databases. What is
the simpliest way to set this up?
Thanks
CanThere are several options, ranging from linking tables, to managing them
both with common scripts. It really depends on why you want them to be
separate databases instead of a single database, and then why you want
certain things in common -- ease of maintenance, security, or something
else?
Cheers,
'(' Jeff A. Stucker
\
Senior Consultant
www.rapidigm.com
"Can" <Can@.discussions.microsoft.com> wrote in message
news:74E21166-FD11-46E5-AF30-A7415D2D331D@.microsoft.com...
> I am interested in having two databases that are on the same server
> connected together. I have the individual databases but I also want to
> have
> a common database that keeps stored procedures to do things such as
> changing
> password. I don't want to cut and paste them into each database each time
> plus if I ever made a change I am creating a lot of work for myself.
> Users would have the same login and password for the two databases. What
> is
> the simpliest way to set this up?
> Thanks
> Can
>|||I am looking to llink stored procedures, not tables, from one database to
another for ease of maintenance. What direction do you suggest?
"Jeff A. Stucker" wrote:

> There are several options, ranging from linking tables, to managing them
> both with common scripts. It really depends on why you want them to be
> separate databases instead of a single database, and then why you want
> certain things in common -- ease of maintenance, security, or something
> else?
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Senior Consultant
> www.rapidigm.com
> "Can" <Can@.discussions.microsoft.com> wrote in message
> news:74E21166-FD11-46E5-AF30-A7415D2D331D@.microsoft.com...
>
>