MGFoster said:
Duane Hookom wrote:
I also lurk/post in microsoft.public.sqlserver.programming and they
demand that posters put in a DDL of the tables they are working w/, some
sample data in INSERT statements & the complete query SQL.
MGFoster,
Yup, they're pretty draconian over there. Getting a response from Mr.
Celko can be quite an experience, too. However, given the ease with
which a simple laid-out T-SQL script can create all tables and load
them with data, ready made for a volunteer to use the important part
of their minimal time and available brainpower on, it just makes sense
for it to be a basic requirement (not that lots of people don't ignore
it).
It isn't so easy with Access, as it largely provides no easy way (not
even VBA) of doing what T-SQL can. You can make a quick table via the
GUI, but have no DDL. Worse, if you make a big complicated table in
the GUI, and accidentally delete that table before you back up that
day . . . oops, you have to painstakingly recreate it by hand.
Personaly, I only use the GUI rarely for Table or Query design. I
just pound out the DDL/DML, and save away the Queries. I find it to
be far more useful to have a Drop and Create Query than laboriously go
through the GUI each time. Although there are a few bits here and
there that Access will let you do, that JET's CREATE isn't so good it.
Access' Design View for Tables has long lacked a "Script DDL" function
to output a simple printed listed of the SQL involved. (At least it
isn't there in MS Access 2000.)
Sincerely,
Chris O.