commenting in Access SQL
Guille
in Access?
For example, in Oracle when you put '--' in a line the
rest of the line is ignored by the sql interpreter
Tom Ellison
Microsoft Access comes with two database engines: Jet and MSDE.
MSDE supports the '-' syntax you mention, plus /* */ commenting.
Jet supports no commenting.
Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts
Michel Walsh
Note that Access removes the comments, even from MS SQL Server, if
you use Access UI.
Hoping it may help,
Vanderghast, Access MVP
"Tom Ellison" <tell...@jcdoyle.com> wrote in message
news:ujdrkv40ls22or54s...@4ax.com...
Guille
>.
>
Tom Ellison
imposed. These limits are:
Total size of a database 2 GB (same as Jet)
Number of simultaneous threads (this would require considerable
explanation and even greater analysis of whether it might impact your
application if you have a large number of users).
There are considerable advantages to MSDE, but some drawbacks. The
most substantial of these is that it is a considerable project to
learn it.
The ability to expand an existing system to more users and more data
with only the purchase of a full SQL Server version is a considerable
advantage when applicable.
There is a separate install for the "engine" of MSDE. You would
likely put this on only one computer - the one where the "backend"
data resides.
If the only reason you would consider switching is to get commenting,
then I would suggest it is unlikely you would gain enough to be worth
the effort to learn MSDE.
You could keep a text version of your queries in text based files,
using Notepad or another editor, which contain all the comments you
want. Place the comments between the SQL. Work in this text when
writing SQL or when you want to review the comments. Past the
uncommented version from there into the queries. This is a partially
satisfactory alternative.
Guille
>.
>
Steven Zillmer
See http://www.microsoft.com/sql/msde/default.asp
It's essentially a workstation version of SQL server
intended for use only by applications on the workstation.
It provides better performance, etc., compared to the Jet
Engine, but deploying it to workstations is a more
complicated issue. No more "here's your one-file Access
application."
>.
>
Michel Walsh
I am far from convinced that it provides better performance, mainly if
you refer to "applications on the workstation". It is, on the contrary,
humanly perceptively slower than Jet. You, and any reader having both on
their PC, can make the test all by yourself (themselves):
Make a table, Ds, one field, D, 10 records with values from 0 to 9.
Make a query (view) bringing the table Ds 6 times, and select the field
from each table. The expected result should have 1Meg-rows (1E6). Do it in
Jet, should get the last record generated in less than 20 sec., under
Access. The same, under MS SQL Server, after you remove the default limit of
displaying 10 000 rows, still under Access, should take about 3 minutes (as
order of magnitude, may vary from computer to computer). The difference is
mainly due to the fact that MS SQL Server log its modifications, making it
more robust against connection failure, but at a price... in the opposite
direction than to the "better performance"...
For any reader that is interested to make the test, or just to learn and
experiment, having Office 2000 or more recent, it may be that MSDE is on a
directory of the main Office CD and my not have been installed with Office.
There is also a Developer version available for about 60.00$US, and which
has better tools and help than MSDE (more for deployment than for
development, IMHO).
Vanderghast, Access MVP
"Steven Zillmer" <I-eat-spam-...@potatochip.com> wrote in message
news:0de101c36e4d$bdb46840$a601...@phx.gbl...