computer unable to connect to sql

My specific computer is not able to connect to SQL through ODBC link, anyone
have any ideas what can block a computer? Please read relevant information
below
-Other users on their computers can log into database using DNS
-I can log into database if I am logged onto a different computer
-Other users logged onto my computer cannot access the database
The purpose for this is I have created many DAPs, queries etc in access for
a time tracking program we use. Last week we upsized the database to MSDE
to mitigate corruption. To try and save time, I am trying to recreate the
access database (front end) using linked tables so all my queries, DAPs, etc
will work.
If this is the wrong group for this question, please direct me to the
correct location. Also I am not an IT or database admin so I am not sure if
I supplied all the information needed. If more info needed, just tell me
what you need.
Many Thanks
Paul D
"PaulD" <nospam> wrote in message
news:uvBZweOMGHA.208@.tk2msftngp13.phx.gbl...
: My specific computer is not able to connect to SQL through ODBC link,
anyone
: have any ideas what can block a computer? Please read relevant information
: below
:
: -Other users on their computers can log into database using DNS
: -I can log into database if I am logged onto a different computer
: -Other users logged onto my computer cannot access the database
:
: The purpose for this is I have created many DAPs, queries etc in access
for
: a time tracking program we use. Last week we upsized the database to MSDE
: to mitigate corruption. To try and save time, I am trying to recreate the
: access database (front end) using linked tables so all my queries, DAPs,
etc
: will work.
:
: If this is the wrong group for this question, please direct me to the
: correct location. Also I am not an IT or database admin so I am not sure
if
: I supplied all the information needed. If more info needed, just tell me
: what you need.
:
: Many Thanks
: Paul D
:
Found the answer, in the library configuration changed network libraries
from TCP/IP to Named Pipes and all is well.

Compiling ideas about security

Dear gurus,
We have got front-end and back-end app write in VB6 which at the beginning
retrieve information of paramount importance through XP registry, info such
as: login, password, strategic folders and so on. Well, I have been thinking
in change this and maybe storing that information in Sql tables help us to
display better our hindrances as well as holes security.
-Storing these data in Sql tables and encrypting the data there (how?)
-Storing these data in XML ??
Any help will be greatly welcomed.
Thanks in advance,
EnricHi Enric,
I see a small problem with storing your login info in SQL tables.
What would happen if your SQL password were to change? How would the app
retrieve the changed password if it can't login to the DB to begin with? :)
In terms of storing it in XML files or any config files for that matter,
what we did was we wrote a custom encryption/decryption function to handle
the read and write. To be more specific, we implemented the triple-DES
algorithm.
Hope this helps.
EK
"Enric" wrote:

> Dear gurus,
> We have got front-end and back-end app write in VB6 which at the beginning
> retrieve information of paramount importance through XP registry, info suc
h
> as: login, password, strategic folders and so on. Well, I have been thinki
ng
> in change this and maybe storing that information in Sql tables help us to
> display better our hindrances as well as holes security.
> -Storing these data in Sql tables and encrypting the data there (how?)
> -Storing these data in XML ??
> Any help will be greatly welcomed.
> Thanks in advance,
> Enric
>|||Why not use Windows Domain level security rather than create your own
security layer?
Password recovery mechanisms are inherent security weaknesses, so don't
store the password at all. Instead, store a secure hash of the password with
salt. The MS Crypto API provides the tools to do this.
David Portas
SQL Server MVP
--|||It sounds like you are basically wanting to query sensitive information from
it's designated location (Active Directory) and save it off where it is more
accessable. But accessable to whom? There are probably developers in your IT
department with admin logins to SQL Server. Unless this is part of some
disaster recovery plan, and the data is placed offsite in a safe deposit
box, I do not see the need for it.
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:B8CB31DE-F58E-4DB8-BE68-586E387DF217@.microsoft.com...
> Dear gurus,
> We have got front-end and back-end app write in VB6 which at the beginning
> retrieve information of paramount importance through XP registry, info
such
> as: login, password, strategic folders and so on. Well, I have been
thinking
> in change this and maybe storing that information in Sql tables help us to
> display better our hindrances as well as holes security.
> -Storing these data in Sql tables and encrypting the data there (how?)
> -Storing these data in XML ?
> Any help will be greatly welcomed.
> Thanks in advance,
> Enric
>