Greetings.
I have a C# Windows app that connects to a remote SQL Server over the
Internet to download records. The application works great until a user
tries to run the query from behind ISA. Is there anything I can do in
the code or configure on the ISA box to allow the connection?
Thank you in advance for your help.In message <1110557721.844982.74370@.z14g2000cwz.googlegroups.com>,
HardBap <hardbap@.gmail.com> writes
>Greetings.
>I have a C# Windows app that connects to a remote SQL Server over the
>Internet to download records. The application works great until a user
>tries to run the query from behind ISA. Is there anything I can do in
>the code or configure on the ISA box to allow the connection?
>Thank you in advance for your help.
>
You will probably need to add some packet filters into ISA to open the
ports being used for the connection etc.
--
Andrew D. Newbould E-Mail: newsgroups@.NOSPAMzadsoft.com
ZAD Software Systems Web : www.zadsoft.com
Showing posts with label internet. Show all posts
Showing posts with label internet. Show all posts
Sunday, 25 March 2012
Connect to remote server
From Enterprise Manager on my PC, how do I connect to a remote server over
the internet - I have the IP address, User Name and Password.
the internet - I have the IP address, User Name and Password.
ThanksWhen creating an SQL connection using SQL Server EM you will need to:
Configure the server alias
Create the SQL connection.
Configure the Server alias
Open SQL Server Client Network Utility.
When Client Network Utility opens, click on the Alias tab.
Click on the Add button.
In the Server Alias text box enter a name for your SQL connection.
Select TCP/IP under Network libraries
Enter the IP address of the Server your SQL database is located on, in
the Server name text box.
Click on the OK button.
Your Server alias will now be configured, click on the Apply button.
Click on the OK button.
Create Connection
Open SQL Server Enterprise Manager
When Enterprise Manager opens, right click SQL Server Group and select
New SQL Server Registration.
The Register SQL Server wizard will now open.
Click on the Next button.
>From the Available Servers drop down menu, select the server alias you
created earlier.
Click on the Add button.
The server should now be listed under Added servers, click on the Next
button.
When the next dialog box appears select 'The SQL Server login
information that was assigned to me by the system administrator' (see
above).
Click on the Next button.
Enter your Login name and Password - this will be used every time you
connect to your SQL server. Click on the Next button.
Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
selected and 'SQL Server Group' is selected for Group name.
Click on the Next button.
When the next dialog box opens you can click on the Finish button.
Your SQL Connection will now be created.
HTH
Paul|||Paul
That works fine, thanks.
<stpaul_71@.yahoo.com> wrote in message
news:1102537081.548714.60980@.z14g2000cwz.googlegro ups.com...
> When creating an SQL connection using SQL Server EM you will need to:
> Configure the server alias
> Create the SQL connection.
> Configure the Server alias
> Open SQL Server Client Network Utility.
> When Client Network Utility opens, click on the Alias tab.
> Click on the Add button.
> In the Server Alias text box enter a name for your SQL connection.
> Select TCP/IP under Network libraries
> Enter the IP address of the Server your SQL database is located on, in
> the Server name text box.
> Click on the OK button.
> Your Server alias will now be configured, click on the Apply button.
> Click on the OK button.
>
> Create Connection
> Open SQL Server Enterprise Manager
> When Enterprise Manager opens, right click SQL Server Group and select
> New SQL Server Registration.
> The Register SQL Server wizard will now open.
> Click on the Next button.
>>From the Available Servers drop down menu, select the server alias you
> created earlier.
> Click on the Add button.
> The server should now be listed under Added servers, click on the Next
> button.
> When the next dialog box appears select 'The SQL Server login
> information that was assigned to me by the system administrator' (see
> above).
> Click on the Next button.
> Enter your Login name and Password - this will be used every time you
> connect to your SQL server. Click on the Next button.
> Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
> selected and 'SQL Server Group' is selected for Group name.
> Click on the Next button.
> When the next dialog box opens you can click on the Finish button.
> Your SQL Connection will now be created.
>
> HTH
> Paul
Thursday, 22 March 2012
connect to mysql database with visual c++ in C
what is the best way to talk to a mysql database using C over the internet? sockets? an api within windows? any helpful starting points would be great. 3rd party libraries are out of the question, i would prefer to code it myself or use an api call. regards.
I'd suggest you start by looking at ODBC.
Connect to MSDE Instance via Internet.
I am trying to connect to a MSDE instance across the internet.
I installed it at my house and can connect from work no problem.
Installed it at a customers and I can not connect to it.
I can access their Linksys router and have the correct ports forwarded (I
tried setting the DMZ on, it made no difference) 1434 UPD and 3605 TCP
(although I have them set to BOTH at this time)
Netstat -an shows that both 3605 and 1434 are listening.
TELNET 72.XXX.XXX.50 3605
(I also tried TELNET 72.XXX.XXX.50\InstanceName 3605) didn't know if I
needed the instance name.
Does nothing. But if I telnet my computer at home it clears the screen like
it should.
I have turned off their windows firewall and disabled their McAfee firewall
but no change.
I also open port 79 (we do some communication before we open SQL Server) and
it communicates fine. So I think I have the router set up OK.
Does anyone have any ideas?
Thanks in advance,
Rob
PS. It was installed as follows:
setup SAPWD=XXXX DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RRRob,
Always difficult ones.
I found that TCP and UDP 1433-1434 open on both inbound and outbound solved
my problems. Also, I had problems if there were 2 NICS involved. Always
configure connections for the lowest IP in the range.
The other issues I've had with MSDE was that MSDE did not enable the TCp/IP
protocol by default. Use Enterprise manager, r-click the server, properties,
network config and check that tcp/ip and named pipes are enabled protocols.
Jamie.
"Rob" wrote:
> I am trying to connect to a MSDE instance across the internet.
> I installed it at my house and can connect from work no problem.
> Installed it at a customers and I can not connect to it.
> I can access their Linksys router and have the correct ports forwarded (I
> tried setting the DMZ on, it made no difference) 1434 UPD and 3605 TCP
> (although I have them set to BOTH at this time)
> Netstat -an shows that both 3605 and 1434 are listening.
> TELNET 72.XXX.XXX.50 3605
> (I also tried TELNET 72.XXX.XXX.50\InstanceName 3605) didn't know if I
> needed the instance name.
> Does nothing. But if I telnet my computer at home it clears the screen li
ke
> it should.
> I have turned off their windows firewall and disabled their McAfee firewal
l
> but no change.
> I also open port 79 (we do some communication before we open SQL Server) a
nd
> it communicates fine. So I think I have the router set up OK.
> Does anyone have any ideas?
> Thanks in advance,
> Rob
> PS. It was installed as follows:
> setup SAPWD=XXXX DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=R
R
>
>
I installed it at my house and can connect from work no problem.
Installed it at a customers and I can not connect to it.
I can access their Linksys router and have the correct ports forwarded (I
tried setting the DMZ on, it made no difference) 1434 UPD and 3605 TCP
(although I have them set to BOTH at this time)
Netstat -an shows that both 3605 and 1434 are listening.
TELNET 72.XXX.XXX.50 3605
(I also tried TELNET 72.XXX.XXX.50\InstanceName 3605) didn't know if I
needed the instance name.
Does nothing. But if I telnet my computer at home it clears the screen like
it should.
I have turned off their windows firewall and disabled their McAfee firewall
but no change.
I also open port 79 (we do some communication before we open SQL Server) and
it communicates fine. So I think I have the router set up OK.
Does anyone have any ideas?
Thanks in advance,
Rob
PS. It was installed as follows:
setup SAPWD=XXXX DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RRRob,
Always difficult ones.
I found that TCP and UDP 1433-1434 open on both inbound and outbound solved
my problems. Also, I had problems if there were 2 NICS involved. Always
configure connections for the lowest IP in the range.
The other issues I've had with MSDE was that MSDE did not enable the TCp/IP
protocol by default. Use Enterprise manager, r-click the server, properties,
network config and check that tcp/ip and named pipes are enabled protocols.
Jamie.
"Rob" wrote:
> I am trying to connect to a MSDE instance across the internet.
> I installed it at my house and can connect from work no problem.
> Installed it at a customers and I can not connect to it.
> I can access their Linksys router and have the correct ports forwarded (I
> tried setting the DMZ on, it made no difference) 1434 UPD and 3605 TCP
> (although I have them set to BOTH at this time)
> Netstat -an shows that both 3605 and 1434 are listening.
> TELNET 72.XXX.XXX.50 3605
> (I also tried TELNET 72.XXX.XXX.50\InstanceName 3605) didn't know if I
> needed the instance name.
> Does nothing. But if I telnet my computer at home it clears the screen li
ke
> it should.
> I have turned off their windows firewall and disabled their McAfee firewal
l
> but no change.
> I also open port 79 (we do some communication before we open SQL Server) a
nd
> it communicates fine. So I think I have the router set up OK.
> Does anyone have any ideas?
> Thanks in advance,
> Rob
> PS. It was installed as follows:
> setup SAPWD=XXXX DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=R
R
>
>
connect to different SQL via SP
I have three locations: SQL1, SQL2 and SQL3. SQL1 is a Developers Edition on
my local workstation. SQL2 is out on the internet, remote from SQL3 which is
also out there on the internet. Currently, I have a DTS on SQL1 that copies
data from SQL3 over to SQL2. Problem: I would like to get this on a
schedule. I don't want to schedule it on my SQL1 machine and I'm not allowed
DTS packages on SQL2 and SQL3 because they are on shared plans. That leaves
me with scheduling SPs through the use of ASP pages.
Is it possible to transfer data between SQL2 and SQL3 in an SP?
thanks!shank
Have you looked at linked servers? For more details please refer to the BOL
"shank" <shank@.tampabay.rr.com> wrote in message
news:%230vAUpgIGHA.1124@.TK2MSFTNGP10.phx.gbl...
>I have three locations: SQL1, SQL2 and SQL3. SQL1 is a Developers Edition
>on my local workstation. SQL2 is out on the internet, remote from SQL3
>which is also out there on the internet. Currently, I have a DTS on SQL1
>that copies data from SQL3 over to SQL2. Problem: I would like to get this
>on a schedule. I don't want to schedule it on my SQL1 machine and I'm not
>allowed DTS packages on SQL2 and SQL3 because they are on shared plans.
>That leaves me with scheduling SPs through the use of ASP pages.
> Is it possible to transfer data between SQL2 and SQL3 in an SP?
> thanks!
>|||I have just been advised by our webhost that they do not allow Linked
Servers due to security issues.
Is there another way to connect through an SP?
In short, I need to automate transfer of data from SQL3 to SQL2 without
Linked Servers or DTS packages.
thanks!
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uEltjujIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> shank
> Have you looked at linked servers? For more details please refer to the
> BOL
> "shank" <shank@.tampabay.rr.com> wrote in message
> news:%230vAUpgIGHA.1124@.TK2MSFTNGP10.phx.gbl...
>
my local workstation. SQL2 is out on the internet, remote from SQL3 which is
also out there on the internet. Currently, I have a DTS on SQL1 that copies
data from SQL3 over to SQL2. Problem: I would like to get this on a
schedule. I don't want to schedule it on my SQL1 machine and I'm not allowed
DTS packages on SQL2 and SQL3 because they are on shared plans. That leaves
me with scheduling SPs through the use of ASP pages.
Is it possible to transfer data between SQL2 and SQL3 in an SP?
thanks!shank
Have you looked at linked servers? For more details please refer to the BOL
"shank" <shank@.tampabay.rr.com> wrote in message
news:%230vAUpgIGHA.1124@.TK2MSFTNGP10.phx.gbl...
>I have three locations: SQL1, SQL2 and SQL3. SQL1 is a Developers Edition
>on my local workstation. SQL2 is out on the internet, remote from SQL3
>which is also out there on the internet. Currently, I have a DTS on SQL1
>that copies data from SQL3 over to SQL2. Problem: I would like to get this
>on a schedule. I don't want to schedule it on my SQL1 machine and I'm not
>allowed DTS packages on SQL2 and SQL3 because they are on shared plans.
>That leaves me with scheduling SPs through the use of ASP pages.
> Is it possible to transfer data between SQL2 and SQL3 in an SP?
> thanks!
>|||I have just been advised by our webhost that they do not allow Linked
Servers due to security issues.
Is there another way to connect through an SP?
In short, I need to automate transfer of data from SQL3 to SQL2 without
Linked Servers or DTS packages.
thanks!
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uEltjujIGHA.3176@.TK2MSFTNGP12.phx.gbl...
> shank
> Have you looked at linked servers? For more details please refer to the
> BOL
> "shank" <shank@.tampabay.rr.com> wrote in message
> news:%230vAUpgIGHA.1124@.TK2MSFTNGP10.phx.gbl...
>
Monday, 19 March 2012
Connect through NAT router
I need to connect to SQL Server 2000 across the Internet. SQL Server is
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill Todd
Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com
|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill Todd
Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com
|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh
Connect through NAT router
I need to connect to SQL Server 2000 across the Internet. SQL Server is
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill Todd
Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com
|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill Todd
Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com
|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh
Connect through NAT router
I need to connect to SQL Server 2000 across the Internet. SQL Server is
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill ToddBill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill ToddBill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh
Thursday, 8 March 2012
Connect across Internet through NAT router
I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill ToddI found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill ToddI found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd
Connect across Internet through NAT router
I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill Todd
I found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill Todd
I found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd
Connect Access to SQL Server AND Local ODBC Connection
I have a customer that wants me to create a database and use a back end of
SQL Server (hosted on the Internet for his site). This would normally be
easy to create the front end with an ADP and continue life as normal. But,
in order to connect his accounting program to this program that I am
creating, I also need the ADP/MDB to connect to his local ODBC Link
(Business Vision Connect!) This is the software that is installed on the
local machine to speak to the accounting software. I can get Connect! to
work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
at this point, I can get one or the other to work...
Does anyone know of a way to get SQL Server to work with an MDB without
asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
System DSN) to work in an ADP? I have also tried creating a file DSN (for
Connect!) which looks like it could work with an ADP, but since the
Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
Any ideas would be great!!!
Thanks,
Shawn
You can connect an mdb to SQL Server by creating linked tables or by
using pass-through queries. You supply the connection string in code.
From the MDB, create a DAO TableDef object for the linked tables, and
QueryDef objects for the pass-through queries (which return read-only
result sets). HTH,
Mary
On Wed, 16 Jun 2004 20:27:05 -0400, "Shawn Oatley"
<notmyemail@.address.com> wrote:
>I have a customer that wants me to create a database and use a back end of
>SQL Server (hosted on the Internet for his site). This would normally be
>easy to create the front end with an ADP and continue life as normal. But,
>in order to connect his accounting program to this program that I am
>creating, I also need the ADP/MDB to connect to his local ODBC Link
>(Business Vision Connect!) This is the software that is installed on the
>local machine to speak to the accounting software. I can get Connect! to
>work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
>at this point, I can get one or the other to work...
>Does anyone know of a way to get SQL Server to work with an MDB without
>asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
>System DSN) to work in an ADP? I have also tried creating a file DSN (for
>Connect!) which looks like it could work with an ADP, but since the
>Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
>Any ideas would be great!!!
>Thanks,
>Shawn
>
|||Shawn,
Find a way to make the ADP work. Linked tables with mdb are a nightmare. Modifying pass through queries on the fly bloats your database and are much harder to maintain than sprocs. Linked tables create excessive connection/locking which leads to DEADLO
CKS. Linked tables should *not be even considered*when the database is accesses through the internet.
Here is a link to a site with numereous connections string examples. http://www.able-consulting.com/ADO_Conn.htm
"Shawn Oatley" wrote:
> I have a customer that wants me to create a database and use a back end of
> SQL Server (hosted on the Internet for his site). This would normally be
> easy to create the front end with an ADP and continue life as normal. But,
> in order to connect his accounting program to this program that I am
> creating, I also need the ADP/MDB to connect to his local ODBC Link
> (Business Vision Connect!) This is the software that is installed on the
> local machine to speak to the accounting software. I can get Connect! to
> work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
> at this point, I can get one or the other to work...
> Does anyone know of a way to get SQL Server to work with an MDB without
> asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
> System DSN) to work in an ADP? I have also tried creating a file DSN (for
> Connect!) which looks like it could work with an ADP, but since the
> Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
> Any ideas would be great!!!
> Thanks,
> Shawn
>
>
SQL Server (hosted on the Internet for his site). This would normally be
easy to create the front end with an ADP and continue life as normal. But,
in order to connect his accounting program to this program that I am
creating, I also need the ADP/MDB to connect to his local ODBC Link
(Business Vision Connect!) This is the software that is installed on the
local machine to speak to the accounting software. I can get Connect! to
work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
at this point, I can get one or the other to work...
Does anyone know of a way to get SQL Server to work with an MDB without
asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
System DSN) to work in an ADP? I have also tried creating a file DSN (for
Connect!) which looks like it could work with an ADP, but since the
Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
Any ideas would be great!!!
Thanks,
Shawn
You can connect an mdb to SQL Server by creating linked tables or by
using pass-through queries. You supply the connection string in code.
From the MDB, create a DAO TableDef object for the linked tables, and
QueryDef objects for the pass-through queries (which return read-only
result sets). HTH,
Mary
On Wed, 16 Jun 2004 20:27:05 -0400, "Shawn Oatley"
<notmyemail@.address.com> wrote:
>I have a customer that wants me to create a database and use a back end of
>SQL Server (hosted on the Internet for his site). This would normally be
>easy to create the front end with an ADP and continue life as normal. But,
>in order to connect his accounting program to this program that I am
>creating, I also need the ADP/MDB to connect to his local ODBC Link
>(Business Vision Connect!) This is the software that is installed on the
>local machine to speak to the accounting software. I can get Connect! to
>work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
>at this point, I can get one or the other to work...
>Does anyone know of a way to get SQL Server to work with an MDB without
>asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
>System DSN) to work in an ADP? I have also tried creating a file DSN (for
>Connect!) which looks like it could work with an ADP, but since the
>Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
>Any ideas would be great!!!
>Thanks,
>Shawn
>
|||Shawn,
Find a way to make the ADP work. Linked tables with mdb are a nightmare. Modifying pass through queries on the fly bloats your database and are much harder to maintain than sprocs. Linked tables create excessive connection/locking which leads to DEADLO
CKS. Linked tables should *not be even considered*when the database is accesses through the internet.
Here is a link to a site with numereous connections string examples. http://www.able-consulting.com/ADO_Conn.htm
"Shawn Oatley" wrote:
> I have a customer that wants me to create a database and use a back end of
> SQL Server (hosted on the Internet for his site). This would normally be
> easy to create the front end with an ADP and continue life as normal. But,
> in order to connect his accounting program to this program that I am
> creating, I also need the ADP/MDB to connect to his local ODBC Link
> (Business Vision Connect!) This is the software that is installed on the
> local machine to speak to the accounting software. I can get Connect! to
> work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
> at this point, I can get one or the other to work...
> Does anyone know of a way to get SQL Server to work with an MDB without
> asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
> System DSN) to work in an ADP? I have also tried creating a file DSN (for
> Connect!) which looks like it could work with an ADP, but since the
> Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
> Any ideas would be great!!!
> Thanks,
> Shawn
>
>
Connect Access to SQL Server AND Local ODBC Connection
I have a customer that wants me to create a database and use a back end of
SQL Server (hosted on the Internet for his site). This would normally be
easy to create the front end with an ADP and continue life as normal. But,
in order to connect his accounting program to this program that I am
creating, I also need the ADP/MDB to connect to his local ODBC Link
(Business Vision Connect!) This is the software that is installed on the
local machine to speak to the accounting software. I can get Connect! to
work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
at this point, I can get one or the other to work...
Does anyone know of a way to get SQL Server to work with an MDB without
asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
System DSN) to work in an ADP? I have also tried creating a file DSN (for
Connect!) which looks like it could work with an ADP, but since the
Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
Any ideas would be great!!!
Thanks,
ShawnYou can connect an mdb to SQL Server by creating linked tables or by
using pass-through queries. You supply the connection string in code.
From the MDB, create a DAO TableDef object for the linked tables, and
QueryDef objects for the pass-through queries (which return read-only
result sets). HTH,
Mary
On Wed, 16 Jun 2004 20:27:05 -0400, "Shawn Oatley"
<notmyemail@.address.com> wrote:
>I have a customer that wants me to create a database and use a back end of
>SQL Server (hosted on the Internet for his site). This would normally be
>easy to create the front end with an ADP and continue life as normal. But,
>in order to connect his accounting program to this program that I am
>creating, I also need the ADP/MDB to connect to his local ODBC Link
>(Business Vision Connect!) This is the software that is installed on the
>local machine to speak to the accounting software. I can get Connect! to
>work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
>at this point, I can get one or the other to work...
>Does anyone know of a way to get SQL Server to work with an MDB without
>asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
>System DSN) to work in an ADP? I have also tried creating a file DSN (for
>Connect!) which looks like it could work with an ADP, but since the
>Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
>Any ideas would be great!!!
>Thanks,
>Shawn
>|||Shawn,
Find a way to make the ADP work. Linked tables with mdb are a nightmare. M
odifying pass through queries on the fly bloats your database and are much h
arder to maintain than sprocs. Linked tables create excessive connection/lo
cking which leads to DEADLO
CKS. Linked tables should *not be even considered*when the database is acce
sses through the internet.
Here is a link to a site with numereous connections string examples. .able-consulting.com/ADO_Conn.htm" target="_blank">http://www
.able-consulting.com/ADO_Conn.htm
"Shawn Oatley" wrote:
> I have a customer that wants me to create a database and use a back end of
> SQL Server (hosted on the Internet for his site). This would normally be
> easy to create the front end with an ADP and continue life as normal. But
,
> in order to connect his accounting program to this program that I am
> creating, I also need the ADP/MDB to connect to his local ODBC Link
> (Business Vision Connect!) This is the software that is installed on the
> local machine to speak to the accounting software. I can get Connect! to
> work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
> at this point, I can get one or the other to work...
> Does anyone know of a way to get SQL Server to work with an MDB without
> asking for the SQLServer Password OR a way to get his Connect (Regular ODB
C
> System DSN) to work in an ADP? I have also tried creating a file DSN (fo
r
> Connect!) which looks like it could work with an ADP, but since the
> Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
> Any ideas would be great!!!
> Thanks,
> Shawn
>
>
SQL Server (hosted on the Internet for his site). This would normally be
easy to create the front end with an ADP and continue life as normal. But,
in order to connect his accounting program to this program that I am
creating, I also need the ADP/MDB to connect to his local ODBC Link
(Business Vision Connect!) This is the software that is installed on the
local machine to speak to the accounting software. I can get Connect! to
work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
at this point, I can get one or the other to work...
Does anyone know of a way to get SQL Server to work with an MDB without
asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
System DSN) to work in an ADP? I have also tried creating a file DSN (for
Connect!) which looks like it could work with an ADP, but since the
Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
Any ideas would be great!!!
Thanks,
ShawnYou can connect an mdb to SQL Server by creating linked tables or by
using pass-through queries. You supply the connection string in code.
From the MDB, create a DAO TableDef object for the linked tables, and
QueryDef objects for the pass-through queries (which return read-only
result sets). HTH,
Mary
On Wed, 16 Jun 2004 20:27:05 -0400, "Shawn Oatley"
<notmyemail@.address.com> wrote:
>I have a customer that wants me to create a database and use a back end of
>SQL Server (hosted on the Internet for his site). This would normally be
>easy to create the front end with an ADP and continue life as normal. But,
>in order to connect his accounting program to this program that I am
>creating, I also need the ADP/MDB to connect to his local ODBC Link
>(Business Vision Connect!) This is the software that is installed on the
>local machine to speak to the accounting software. I can get Connect! to
>work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
>at this point, I can get one or the other to work...
>Does anyone know of a way to get SQL Server to work with an MDB without
>asking for the SQLServer Password OR a way to get his Connect (Regular ODBC
>System DSN) to work in an ADP? I have also tried creating a file DSN (for
>Connect!) which looks like it could work with an ADP, but since the
>Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
>Any ideas would be great!!!
>Thanks,
>Shawn
>|||Shawn,
Find a way to make the ADP work. Linked tables with mdb are a nightmare. M
odifying pass through queries on the fly bloats your database and are much h
arder to maintain than sprocs. Linked tables create excessive connection/lo
cking which leads to DEADLO
CKS. Linked tables should *not be even considered*when the database is acce
sses through the internet.
Here is a link to a site with numereous connections string examples. .able-consulting.com/ADO_Conn.htm" target="_blank">http://www
.able-consulting.com/ADO_Conn.htm
"Shawn Oatley" wrote:
> I have a customer that wants me to create a database and use a back end of
> SQL Server (hosted on the Internet for his site). This would normally be
> easy to create the front end with an ADP and continue life as normal. But
,
> in order to connect his accounting program to this program that I am
> creating, I also need the ADP/MDB to connect to his local ODBC Link
> (Business Vision Connect!) This is the software that is installed on the
> local machine to speak to the accounting software. I can get Connect! to
> work when it isn't in an ADP. I can get SQL Server to work in an ADP. So,
> at this point, I can get one or the other to work...
> Does anyone know of a way to get SQL Server to work with an MDB without
> asking for the SQLServer Password OR a way to get his Connect (Regular ODB
C
> System DSN) to work in an ADP? I have also tried creating a file DSN (fo
r
> Connect!) which looks like it could work with an ADP, but since the
> Connect! is rather old, it doesn't seem to like to be put into a FileDSN.
> Any ideas would be great!!!
> Thanks,
> Shawn
>
>
Connect throught internet between 2 server.
Hi all,
I 'm in VietNam, i want to use SQL server 2000 to connect to SQL server in China throught the internet. I did it in many way but it did not work, please show me.
Best regardsOriginally posted by thanhtung2003
Hi all,
I 'm in VietNam, i want to use SQL server 2000 to connect to SQL server in China throught the internet. I did it in many way but it did not work, please show me.
Best regards
how did u try to connect?
u can register the remote server in the enterprise manager or directly connect to it through query analyser by providing the ip and username and password.|||Are there any firewalls in between the two locations ... that also sometimes proves to be a major hindrance if sql server ports are not opened up on firewall
I 'm in VietNam, i want to use SQL server 2000 to connect to SQL server in China throught the internet. I did it in many way but it did not work, please show me.
Best regardsOriginally posted by thanhtung2003
Hi all,
I 'm in VietNam, i want to use SQL server 2000 to connect to SQL server in China throught the internet. I did it in many way but it did not work, please show me.
Best regards
how did u try to connect?
u can register the remote server in the enterprise manager or directly connect to it through query analyser by providing the ip and username and password.|||Are there any firewalls in between the two locations ... that also sometimes proves to be a major hindrance if sql server ports are not opened up on firewall
Subscribe to:
Posts (Atom)