Re: MS Query Analyser and MS Access

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 04/06/04 

Date: Tue, 06 Apr 2004 11:52:09 -0600

You can't use Query Analyzer to connect to Access. Just
because an application supports SQL doesn't mean you can use
any vendor's tool with it. Additionally, there are different
flavors of SQL - ANSI SQL is the standard SQL language and
every database has different levels of compliance or levels
of what they support in ANSI SQL. And then they have their
own extensions.

-Sue

On Tue, 06 Apr 2004 05:07:47 GMT, "Evan Tomlinson"
<abuse@versign.com> wrote:

>Hi,
>
>As far as I understand MS Access supports the SQL language, thus it should
>be possible to use tools such as MS SQL Query Analyser to connect to your MS
>Access database. But I cannot get this to work.
>
>My thought was to use the path to the file rather than the name of the
>server, but this does not seem to do it. Any wise ideas out here?
>
>
>Thanks!

Relevant Pages

  • Re: SP - output parameter not coming back
    ... > Also I have tested the SP using SQL Query Analyzer and it does not ... If it does not work in query analyzer, it has no chance of working in asp ... > If I do not find out about the output parameter I am considering ... You definitely need to work on the stored procedure so that you can see the ...
    (microsoft.public.inetserver.asp.db)
  • Re: Missing table
    ... execute the commands within Query Analyzer. ... The first piece of sql displays the table owner, type, and the name of the table. ...
    (microsoft.public.sqlserver.server)
  • Re: Cannot edit table data using Enterprise Manager
    ... The point of using Query Analyzer is that you write the ... they could have had the SQL written and been done with it! ... change or insert some words to data string using Replace function is ... Manager wasn't designed to be a data entry tool. ...
    (microsoft.public.sqlserver.tools)
  • Re: performace issue with a stored procedure
    ... in Query Analyzer and look at the results in SQL Profiler. ... The high CPU you are seeing might be due to cursors or some bad SQL choices. ...
    (microsoft.public.sqlserver.programming)
  • Re: Local SQL Queries slow on Dual CPU/hyperthreading hardware
    ... This will tell if the problem is related to the SQL script you send or not. ... anti-virus, network monitoring, etc running? ... but only when hyperthreading is switched on using the same> physical hardware. ... In fact you don't need to run the query at all -> simply parsing it in SQL query analyzer is enough. ...
    (microsoft.public.sqlserver.server)