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.

complex query!

Hi,
I have Below query with me. but it's showing me error i.e "[Microsoft]
[ODBC SQL Server Driver]Syntax error or access violation"
I am not able to understand what to do exactly ' Please help
Query:
----
SELECT sla.sla_sc, incident.incident_id, incident.inc_resolve_due,
incident.inc_resolve_act,
incident.inc_close_date, incident.inc_status, usr_group.usr_group_sc,
incident.date_logged,
incident.time_to_resolve, inc_data.total_service_time,
incident.inc_resolve_sla, inc_cat.inc_cat_sc
FROM (((incident INNER JOIN inc_data ON
incident.incident_id=inc_data.incident_id) INNER JOIN assyst_usr
ON incident.assyst_usr_id=assyst_usr.assyst_usr_id) INNER JOIN sla ON
incident.sla_id=sla.sla_id) INNER JOIN inc_cat ON
incident.inc_cat_id=inc_cat.inc_cat_id) INNER JOIN usr_group ON
assyst_usr.usr_group_id=usr_group.usr_group_id WHERE sla.sla_sc<>''
AND
usr_group.usr_group_sc='" & SERVICE DESK & "' AND
((incident.date_logged>={27/12/2006)
AND incident.date_logged<{29/12/2006}) OR
(incident.inc_close_date>={27/12/2006}
AND incident.inc_close_date<{27/12/2006})OR(incident.inc_status = 'n')or(incident.inc_status = 'c'))
ORDER BY sla.sla_sc"
---Instead of braces, enclose your date literals in single quotes. Braces are
used as the ODBC escape sequence.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Abhi" <bawejaji@.gmail.com> wrote in message
news:1176547837.456693.297880@.y80g2000hsf.googlegroups.com...
> Hi,
> I have Below query with me. but it's showing me error i.e "[Microsoft]
> [ODBC SQL Server Driver]Syntax error or access violation"
> I am not able to understand what to do exactly ' Please help
> Query:
> ----
> SELECT sla.sla_sc, incident.incident_id, incident.inc_resolve_due,
> incident.inc_resolve_act,
> incident.inc_close_date, incident.inc_status, usr_group.usr_group_sc,
> incident.date_logged,
> incident.time_to_resolve, inc_data.total_service_time,
> incident.inc_resolve_sla, inc_cat.inc_cat_sc
> FROM (((incident INNER JOIN inc_data ON
> incident.incident_id=inc_data.incident_id) INNER JOIN assyst_usr
> ON incident.assyst_usr_id=assyst_usr.assyst_usr_id) INNER JOIN sla ON
> incident.sla_id=sla.sla_id) INNER JOIN inc_cat ON
> incident.inc_cat_id=inc_cat.inc_cat_id) INNER JOIN usr_group ON
> assyst_usr.usr_group_id=usr_group.usr_group_id WHERE sla.sla_sc<>''
> AND
> usr_group.usr_group_sc='" & SERVICE DESK & "' AND
> ((incident.date_logged>={27/12/2006)
> AND incident.date_logged<{29/12/2006}) OR
> (incident.inc_close_date>={27/12/2006}
> AND incident.inc_close_date<{27/12/2006})OR(incident.inc_status => 'n')or(incident.inc_status = 'c'))
> ORDER BY sla.sla_sc"
> ---
>|||Try this:-
Some of the braces and { braces are not required:-
SELECT sla.sla_sc, incident.incident_id, incident.inc_resolve_due,
incident.inc_resolve_act,
incident.inc_close_date, incident.inc_status, usr_group.usr_group_sc,
incident.date_logged,
incident.time_to_resolve, inc_data.total_service_time,
incident.inc_resolve_sla, inc_cat.inc_cat_sc
FROM incident INNER JOIN inc_data ON
incident.incident_id=inc_data.incident_id INNER JOIN assyst_usr
ON incident.assyst_usr_id=assyst_usr.assyst_usr_id INNER JOIN sla ON
incident.sla_id=sla.sla_id INNER JOIN inc_cat ON
incident.inc_cat_id=inc_cat.inc_cat_id INNER JOIN usr_group ON
assyst_usr.usr_group_id=usr_group.usr_group_id WHERE sla.sla_sc<>''
AND
usr_group.usr_group_sc='" & SERVICE DESK & "' AND
((incident.date_logged>='27/12/2006')
AND incident.date_logged<'29/12/2006') OR
(incident.inc_close_date>='27/12/2006'
AND incident.inc_close_date<'27/12/2006')OR(incident.inc_status ='n')
or(incident.inc_status = 'c')
ORDER BY sla.sla_sc
Thanks
Hari
"Abhi" <bawejaji@.gmail.com> wrote in message
news:1176547837.456693.297880@.y80g2000hsf.googlegroups.com...
> Hi,
> I have Below query with me. but it's showing me error i.e "[Microsoft]
> [ODBC SQL Server Driver]Syntax error or access violation"
> I am not able to understand what to do exactly ' Please help
> Query:
> ----
> SELECT sla.sla_sc, incident.incident_id, incident.inc_resolve_due,
> incident.inc_resolve_act,
> incident.inc_close_date, incident.inc_status, usr_group.usr_group_sc,
> incident.date_logged,
> incident.time_to_resolve, inc_data.total_service_time,
> incident.inc_resolve_sla, inc_cat.inc_cat_sc
> FROM (((incident INNER JOIN inc_data ON
> incident.incident_id=inc_data.incident_id) INNER JOIN assyst_usr
> ON incident.assyst_usr_id=assyst_usr.assyst_usr_id) INNER JOIN sla ON
> incident.sla_id=sla.sla_id) INNER JOIN inc_cat ON
> incident.inc_cat_id=inc_cat.inc_cat_id) INNER JOIN usr_group ON
> assyst_usr.usr_group_id=usr_group.usr_group_id WHERE sla.sla_sc<>''
> AND
> usr_group.usr_group_sc='" & SERVICE DESK & "' AND
> ((incident.date_logged>={27/12/2006)
> AND incident.date_logged<{29/12/2006}) OR
> (incident.inc_close_date>={27/12/2006}
> AND incident.inc_close_date<{27/12/2006})OR(incident.inc_status => 'n')or(incident.inc_status = 'c'))
> ORDER BY sla.sla_sc"
> ---
>

Compatible versions of Ms SQL Server, ODBC driver, Driver Manager and ODBC API s

Hi,

Please help share with me if you know the version compatibility matrix of Ms SQL Server, ODBC driver (sqlsrv32.dll), Driver Manager (odbc32.dll) and ODBC API spec. For instance, how can I know Ms SQL Server 2000 can work with which version of sqlsrv32.dll, a particular version of sqlsrv32.dll can work with which version of odbc32.dll and a certain version of sqlsrv32.dll/odbc32.dll conforms to which version of ODBC API spec (e.g. 3.5).

Any help will be appreciated.

Thanks,

vtluu.Instead of sweating bullets trying to juggle chainsaws, why not just use the current MDAC (http://msdn.microsoft.com/data/mdac/)?

-PatP

Compatibility of ODBC 2000 vs ODBC 2003

Will there be a compatibility issue between my client ODBC
version 2000.80.194 and the SQL server 2003.I assume you are referring to SQL Server 2005. There is no SQL Server 2003.
The client version you are referring to is the one that shipped with SQL
2000. The SQL 2000 clients will work fine against a SQL 2005 server, but
they wont be able to access all of the new features.
Brannon
"chanjo" <anonymous@.discussions.microsoft.com> wrote in message
news:181f01c48c62$c7433290$a501280a@.phx.gbl...
> Will there be a compatibility issue between my client ODBC
> version 2000.80.194 and the SQL server 2003.

Compatibility of ODBC 2000 vs ODBC 2003

Will there be a compatibility issue between my client ODBC
version 2000.80.194 and the SQL server 2003.
I assume you are referring to SQL Server 2005. There is no SQL Server 2003.
The client version you are referring to is the one that shipped with SQL
2000. The SQL 2000 clients will work fine against a SQL 2005 server, but
they wont be able to access all of the new features.
Brannon
"chanjo" <anonymous@.discussions.microsoft.com> wrote in message
news:181f01c48c62$c7433290$a501280a@.phx.gbl...
> Will there be a compatibility issue between my client ODBC
> version 2000.80.194 and the SQL server 2003.