Re: Understanding SQL Connection

Rick,
Thanks again! You did exactly what I asked.... pointed me in the right
direction. After looking carefully at the linked table setup dialog boxes, I
finally came to the "Save Password" checkbox tucked neatly at the bottom
right of the "Link Table" dialog box. ( Seems like a very strange place to
put that option, but, what do I know?)

Based on my understanding, we won't be able to use NT security due to the
production SQL server being hosted by a 3rd party on an external domain.

So, this leads me to my follow-ups. Under what conditions would my
application need to 'refresh the link' to the tables, thereby requiring the
deletion and re-linking you mentioned in your post? Is there a way to ensure
the tables stay linked, with the SQL username and password I supply during
the table linking steps? Does Access keep this information somewhere that
can be programatically controlled? Is there just a better way to do this
then using the standard linked table senario?

Thanks,
Bernie

"Rick Brandt" wrote:

> "bernadou" <bernadou@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:099FE1C3-9B70-490E-B67A-592FA8644058@xxxxxxxxxxxxxxxx
> >I have some linked SQL 2005 tables in my Access front end. I went through
> > the linked table wizard and created a DSN. I then went into the DSN and
> > added the correct username and password that 'should' authenticate Access
> > each time it needs to connect. Sample DSN below:
>
> Look at your DSN entry again where you entered a UserName and Password. Those
> entries are not what you think they are. They are associated with the checkbox
> labeled...
>
> Connect to SQL Server to obtain default settings for the additional
> configuration options.
>
> In other words it means "While I am creating this DSN use these credentials to
> get some default settings from the server". It does not mean that those
> credentials are automatically passed when the DSN is actually used later on.
>
> Now...when you create linked tables using that DSN you will have to supply
> credentials and you should be given the option to save them as part of the table
> link definition. That would allow for that link to be used without supplying
> credentials later on. If the link is refreshed later on though you might lose
> the credentials and the link would have to be deleted and recreated to put them
> back.
>
> With SQL Server it is best to set it up using Trusted Connections (Integrated
> Security). This passes the Windows Domain credentials to the server so the user
> is never prompted.
>
> --
> I don't check the Email account attached
> to this message. Send instead to...
> RBrandt at Hunter dot com
>
>
>
>
>
>
.

Relevant Pages

  • Re: Understanding SQL Connection
    ... > the linked table wizard and created a DSN. ... Connect to SQL Server to obtain default settings for the additional ... In other words it means "While I am creating this DSN use these credentials to ... With SQL Server it is best to set it up using Trusted Connections (Integrated ...
    (microsoft.public.access.forms)
  • cannot access website
    ... Nerve.com--this started a few weeks ago; I do not get the error message on ... Microsoft OLE DB Provider for ODBC Drivers Error '80040e4d' ... Not defined as a valid user of a trusted SQL Server connection. ... The DSN used to connect to the Commerce database is misconfigured to use ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Balancing security needs in ADO.NET applications
    ... See my article http://www.developer.com/db/article.php/3693236 that shows how to put together a hierarchical TableAdapter using SPs. ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server credentials or the application's logon/pw. ... all they can do is run specific SPs that carefully guard the data and do not permit gross operations like dropping tables or changing rights. ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Invalid authorization specification
    ... Does your application use a DSN to connect to SQL Server? ... DSN is setup correctly on the client machine. ... How to troubleshoot connectivity issues in SQL Server 2000 - ...
    (microsoft.public.sqlserver.connect)
  • Re: Login failed for user . The user is not associated with a trusted SQL Server connection.
    ... he never mentioned he is impersonating in asp.net - so no delegation needed. ... Cassini runs with the credentials of the interactive user - which seems to have access to sql - in contrast to the local ASPNET account - which i am trying to tell him since 2 days.... ... yes - use explicit credentials and enable mixed mode auth in sql server to get this to work. ...
    (microsoft.public.dotnet.security)