> Hello,
> I am using trusted windows user connection to SQL
server.
> I created an ODBC link from Access to SQL server. I am
> able to modify data in tables through SQL Enterprise
> Manager however I am not able to modify them in Access.
> What is missing?You need to create a primary key or unique index on any SQLS tables
you want to modify from Access.
--mary
On Sat, 17 Apr 2004 13:34:26 -0700, "JIM.H."
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>server.|||Why do I have to do that? And if my primary key is based
on many columns will that cuse any problem?
>--Original Message--
>You need to create a primary key or unique index on any
SQLS tables
>you want to modify from Access.
>--mary
>On Sat, 17 Apr 2004 13:34:26 -0700, "JIM.H."
><anonymous@.discussions.microsoft.com> wrote:
>
Access.[vbcol=seagreen]
>.
>|||Why? because it won't work if you don't. Access can't locate the row
on the server, update it, and guarantee data integrity if the table
doesn't have a PK. If your PK is based on too many columns, then you
should consider a surrogate PK. A good starting point would be
"Database Design for Mere Mortals: A Hands-On Guide to Relational
Database Design" by Mike Hernandez.
--Mary
On Sun, 18 Apr 2004 17:58:46 -0700, "JIM.H."
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Why do I have to do that? And if my primary key is based
>on many columns will that cuse any problem?
>SQLS tables
>Access.
Showing posts with label trusted. Show all posts
Showing posts with label trusted. Show all posts
Friday, February 24, 2012
access-SQL ODBC link
> Hello,
> I am using trusted windows user connection to SQL
server.
> I created an ODBC link from Access to SQL server. I am
> able to modify data in tables through SQL Enterprise
> Manager however I am not able to modify them in Access.
> What is missing?
You need to create a primary key or unique index on any SQLS tables
you want to modify from Access.
--mary
On Sat, 17 Apr 2004 13:34:26 -0700, "JIM.H."
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>server.
|||Why do I have to do that? And if my primary key is based
on many columns will that cuse any problem?
>--Original Message--
>You need to create a primary key or unique index on any
SQLS tables[vbcol=seagreen]
>you want to modify from Access.
>--mary
>On Sat, 17 Apr 2004 13:34:26 -0700, "JIM.H."
><anonymous@.discussions.microsoft.com> wrote:
Access.
>.
>
|||Why? because it won't work if you don't. Access can't locate the row
on the server, update it, and guarantee data integrity if the table
doesn't have a PK. If your PK is based on too many columns, then you
should consider a surrogate PK. A good starting point would be
"Database Design for Mere Mortals: A Hands-On Guide to Relational
Database Design" by Mike Hernandez.
--Mary
On Sun, 18 Apr 2004 17:58:46 -0700, "JIM.H."
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Why do I have to do that? And if my primary key is based
>on many columns will that cuse any problem?
>SQLS tables
>Access.
> I am using trusted windows user connection to SQL
server.
> I created an ODBC link from Access to SQL server. I am
> able to modify data in tables through SQL Enterprise
> Manager however I am not able to modify them in Access.
> What is missing?
You need to create a primary key or unique index on any SQLS tables
you want to modify from Access.
--mary
On Sat, 17 Apr 2004 13:34:26 -0700, "JIM.H."
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>server.
|||Why do I have to do that? And if my primary key is based
on many columns will that cuse any problem?
>--Original Message--
>You need to create a primary key or unique index on any
SQLS tables[vbcol=seagreen]
>you want to modify from Access.
>--mary
>On Sat, 17 Apr 2004 13:34:26 -0700, "JIM.H."
><anonymous@.discussions.microsoft.com> wrote:
Access.
>.
>
|||Why? because it won't work if you don't. Access can't locate the row
on the server, update it, and guarantee data integrity if the table
doesn't have a PK. If your PK is based on too many columns, then you
should consider a surrogate PK. A good starting point would be
"Database Design for Mere Mortals: A Hands-On Guide to Relational
Database Design" by Mike Hernandez.
--Mary
On Sun, 18 Apr 2004 17:58:46 -0700, "JIM.H."
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Why do I have to do that? And if my primary key is based
>on many columns will that cuse any problem?
>SQLS tables
>Access.
Thursday, February 16, 2012
accessing SQL Server behind a firewall
I am trying to get to an instance of SQL Server behind a
firewall via port 1450, but I get an error message : "Not
associated with a trusted SQL Server Connection". Do I
need to use a different port? Somehow register port 1450?
Port 1433 is being used for a SQL Server instance on
another machine.
sounds like you're trying to use windows authentication and it can't get
through the firewall.
jjjjj wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
|||No, I'm using SQL Server authentication. I can get to the
default database fine. There seems to be an issue with
using port 1450.
>--Original Message--
>sounds like you're trying to use windows authentication
and it can't get[vbcol=seagreen]
>through the firewall.
>
>jjjjj wrote:
message : "Not[vbcol=seagreen]
1450?
>.
>
|||Is it a named or default instance? Use Server Network Utility to check port numbers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
>I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
|||It is a default instance on the machine but not the
firewall default instance.
>--Original Message--
>Is it a named or default instance? Use Server Network
Utility to check port numbers.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"jjjjj" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
message : "Not[vbcol=seagreen]
1450?
>
>.
>
|||Hi
It should not make an difference if there is another instance on another
server.
Ports are opened with a IP address:Port combination. You can have a 1000 SQL
servers, all using the same port number, as long as each server has a
different IP address.
Regards
Mike
"jjjjj" wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
>
|||> It is a default instance on the machine but not the
> firewall default instance.
I'm sorry, but I didn't get that. What is a "firewall default instance"?
I think Mike's post gives you the information you need. Find out what port number your SQL server
uses (again, use Server Network Utility). Then open in the firewall for that IP Address and port
number combination.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:19da01c4a18e$a365eb10$a401280a@.phx.gbl...[vbcol=seagreen]
> It is a default instance on the machine but not the
> firewall default instance.
> Utility to check port numbers.
> message
> message : "Not
> 1450?
firewall via port 1450, but I get an error message : "Not
associated with a trusted SQL Server Connection". Do I
need to use a different port? Somehow register port 1450?
Port 1433 is being used for a SQL Server instance on
another machine.
sounds like you're trying to use windows authentication and it can't get
through the firewall.
jjjjj wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
|||No, I'm using SQL Server authentication. I can get to the
default database fine. There seems to be an issue with
using port 1450.
>--Original Message--
>sounds like you're trying to use windows authentication
and it can't get[vbcol=seagreen]
>through the firewall.
>
>jjjjj wrote:
message : "Not[vbcol=seagreen]
1450?
>.
>
|||Is it a named or default instance? Use Server Network Utility to check port numbers.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
>I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
|||It is a default instance on the machine but not the
firewall default instance.
>--Original Message--
>Is it a named or default instance? Use Server Network
Utility to check port numbers.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"jjjjj" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
message : "Not[vbcol=seagreen]
1450?
>
>.
>
|||Hi
It should not make an difference if there is another instance on another
server.
Ports are opened with a IP address:Port combination. You can have a 1000 SQL
servers, all using the same port number, as long as each server has a
different IP address.
Regards
Mike
"jjjjj" wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
>
|||> It is a default instance on the machine but not the
> firewall default instance.
I'm sorry, but I didn't get that. What is a "firewall default instance"?
I think Mike's post gives you the information you need. Find out what port number your SQL server
uses (again, use Server Network Utility). Then open in the firewall for that IP Address and port
number combination.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:19da01c4a18e$a365eb10$a401280a@.phx.gbl...[vbcol=seagreen]
> It is a default instance on the machine but not the
> firewall default instance.
> Utility to check port numbers.
> message
> message : "Not
> 1450?
accessing SQL Server behind a firewall
I am trying to get to an instance of SQL Server behind a
firewall via port 1450, but I get an error message : "Not
associated with a trusted SQL Server Connection". Do I
need to use a different port? Somehow register port 1450?
Port 1433 is being used for a SQL Server instance on
another machine.sounds like you're trying to use windows authentication and it can't get
through the firewall.
jjjjj wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.|||No, I'm using SQL Server authentication. I can get to the
default database fine. There seems to be an issue with
using port 1450.
>--Original Message--
>sounds like you're trying to use windows authentication
and it can't get
>through the firewall.
>
>jjjjj wrote:
>> I am trying to get to an instance of SQL Server behind a
>> firewall via port 1450, but I get an error
message : "Not
>> associated with a trusted SQL Server Connection". Do I
>> need to use a different port? Somehow register port
1450?
>> Port 1433 is being used for a SQL Server instance on
>> another machine.
>.
>|||Is it a named or default instance? Use Server Network Utility to check port numbers.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
>I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.|||It is a default instance on the machine but not the
firewall default instance.
>--Original Message--
>Is it a named or default instance? Use Server Network
Utility to check port numbers.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"jjjjj" <anonymous@.discussions.microsoft.com> wrote in
message
>news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
>>I am trying to get to an instance of SQL Server behind a
>> firewall via port 1450, but I get an error
message : "Not
>> associated with a trusted SQL Server Connection". Do I
>> need to use a different port? Somehow register port
1450?
>> Port 1433 is being used for a SQL Server instance on
>> another machine.
>
>.
>|||Hi
It should not make an difference if there is another instance on another
server.
Ports are opened with a IP address:Port combination. You can have a 1000 SQL
servers, all using the same port number, as long as each server has a
different IP address.
Regards
Mike
"jjjjj" wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
>|||> It is a default instance on the machine but not the
> firewall default instance.
I'm sorry, but I didn't get that. What is a "firewall default instance"?
I think Mike's post gives you the information you need. Find out what port number your SQL server
uses (again, use Server Network Utility). Then open in the firewall for that IP Address and port
number combination.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:19da01c4a18e$a365eb10$a401280a@.phx.gbl...
> It is a default instance on the machine but not the
> firewall default instance.
> >--Original Message--
> >Is it a named or default instance? Use Server Network
> Utility to check port numbers.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >http://www.karaszi.com/sqlserver/default.asp
> >http://www.solidqualitylearning.com/
> >
> >
> >"jjjjj" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
> >>I am trying to get to an instance of SQL Server behind a
> >> firewall via port 1450, but I get an error
> message : "Not
> >> associated with a trusted SQL Server Connection". Do I
> >> need to use a different port? Somehow register port
> 1450?
> >> Port 1433 is being used for a SQL Server instance on
> >> another machine.
> >
> >
> >.
> >
firewall via port 1450, but I get an error message : "Not
associated with a trusted SQL Server Connection". Do I
need to use a different port? Somehow register port 1450?
Port 1433 is being used for a SQL Server instance on
another machine.sounds like you're trying to use windows authentication and it can't get
through the firewall.
jjjjj wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.|||No, I'm using SQL Server authentication. I can get to the
default database fine. There seems to be an issue with
using port 1450.
>--Original Message--
>sounds like you're trying to use windows authentication
and it can't get
>through the firewall.
>
>jjjjj wrote:
>> I am trying to get to an instance of SQL Server behind a
>> firewall via port 1450, but I get an error
message : "Not
>> associated with a trusted SQL Server Connection". Do I
>> need to use a different port? Somehow register port
1450?
>> Port 1433 is being used for a SQL Server instance on
>> another machine.
>.
>|||Is it a named or default instance? Use Server Network Utility to check port numbers.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
>I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.|||It is a default instance on the machine but not the
firewall default instance.
>--Original Message--
>Is it a named or default instance? Use Server Network
Utility to check port numbers.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"jjjjj" <anonymous@.discussions.microsoft.com> wrote in
message
>news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
>>I am trying to get to an instance of SQL Server behind a
>> firewall via port 1450, but I get an error
message : "Not
>> associated with a trusted SQL Server Connection". Do I
>> need to use a different port? Somehow register port
1450?
>> Port 1433 is being used for a SQL Server instance on
>> another machine.
>
>.
>|||Hi
It should not make an difference if there is another instance on another
server.
Ports are opened with a IP address:Port combination. You can have a 1000 SQL
servers, all using the same port number, as long as each server has a
different IP address.
Regards
Mike
"jjjjj" wrote:
> I am trying to get to an instance of SQL Server behind a
> firewall via port 1450, but I get an error message : "Not
> associated with a trusted SQL Server Connection". Do I
> need to use a different port? Somehow register port 1450?
> Port 1433 is being used for a SQL Server instance on
> another machine.
>|||> It is a default instance on the machine but not the
> firewall default instance.
I'm sorry, but I didn't get that. What is a "firewall default instance"?
I think Mike's post gives you the information you need. Find out what port number your SQL server
uses (again, use Server Network Utility). Then open in the firewall for that IP Address and port
number combination.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jjjjj" <anonymous@.discussions.microsoft.com> wrote in message
news:19da01c4a18e$a365eb10$a401280a@.phx.gbl...
> It is a default instance on the machine but not the
> firewall default instance.
> >--Original Message--
> >Is it a named or default instance? Use Server Network
> Utility to check port numbers.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >http://www.karaszi.com/sqlserver/default.asp
> >http://www.solidqualitylearning.com/
> >
> >
> >"jjjjj" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:4a0301c4a186$995460f0$a501280a@.phx.gbl...
> >>I am trying to get to an instance of SQL Server behind a
> >> firewall via port 1450, but I get an error
> message : "Not
> >> associated with a trusted SQL Server Connection". Do I
> >> need to use a different port? Somehow register port
> 1450?
> >> Port 1433 is being used for a SQL Server instance on
> >> another machine.
> >
> >
> >.
> >
Subscribe to:
Posts (Atom)