V
Vernell
Why you should know SQL syntax when Access query builder generates the SQL
for you?
for you?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Rick Brandt
Vernell said:Why you should know SQL syntax when Access query builder generates the SQL
for you?
Some SQL cannot be done in the GUI builder, (non equi-joins, UNIONs, etc.), and
it's a good skill when using SQL in code. Eliminates having to open a query
design window and copying the SQL from it.
B
Brendan Reynolds
In addition to the points that Rick makes elsewhere in this thread, learning
SQL will also enable you to communicate with other developers. If you ask a
query-related question in a newsgroup, for example, you're likely to get an
answer in the form of a SQL statement, because it is much more concise and
less open to misinterpretation than trying to explain, step by step, how to
achieve the result using the graphical query designer. And then there are
all the other circumstances in which SQL syntax is used in Access - opening
a recordset, using a DLookup or DCount, the WhereCondition argument of the
OpenForm and OpenReport methods, etc.
SQL will also enable you to communicate with other developers. If you ask a
query-related question in a newsgroup, for example, you're likely to get an
answer in the form of a SQL statement, because it is much more concise and
less open to misinterpretation than trying to explain, step by step, how to
achieve the result using the graphical query designer. And then there are
all the other circumstances in which SQL syntax is used in Access - opening
a recordset, using a DLookup or DCount, the WhereCondition argument of the
OpenForm and OpenReport methods, etc.
M
M.L. Sco Scofield
Rick and Brendan are very correct. There are a *lot* of query related things
that you can only do if you know SQL. As good as the query builder is, it
does have limitations.
This group would have been an OK place to ask a Access SQL "language"
question. (The microsoft.public.access.queries group might have been a
better choice.) His question, however, was about SQL Server "the product."
That's why I suggested one of the SQL Server groups and pointed him to the
SQL Server home page.
Sco
M.L. "Sco" Scofield, Microsoft Access MVP, MCSD, MCP, MSS, A+
Denver Area Access Users Group Vice President www.DAAUG.org
MS Colorado Events Administrator www.MSColoradoEvents.com
Useful Metric Conversion #18 of 19: 8 nickels = 2 paradigms (My personal
favorite)
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
that you can only do if you know SQL. As good as the query builder is, it
does have limitations.
This group would have been an OK place to ask a Access SQL "language"
question. (The microsoft.public.access.queries group might have been a
better choice.) His question, however, was about SQL Server "the product."
That's why I suggested one of the SQL Server groups and pointed him to the
SQL Server home page.
Sco
M.L. "Sco" Scofield, Microsoft Access MVP, MCSD, MCP, MSS, A+
Denver Area Access Users Group Vice President www.DAAUG.org
MS Colorado Events Administrator www.MSColoradoEvents.com
Useful Metric Conversion #18 of 19: 8 nickels = 2 paradigms (My personal
favorite)
Miscellaneous Access and VB "stuff" at www.ScoBiz.com