> >
> > But in the case of queries, please use query aliases.
> >
> >

SELECT C.col1, C.col2, O.col2, O.col3 
> >  FROM Customers AS c JOIN Orders AS O ON C.key=O.key 

> > It can make big multi-table queries oh so much easier to read. The View and Query Designers support this when use the Add Table dialog.
> >
> > Another standard for many SQL publishers is to put SQL keywords in upper case, table names i proper case and column names in lower case. Inceases readability.
> >
> > Yet another naming standard. Table names are plural, column names singualar. I dislike the VFP convention of prefixing a datatype letter to column names, but I like the advise in the HGelp topic 'Object Naming Conventions" and "Naming Conventions" (except for table column naming).
> >
> > -Anders
> >
> > -Anders
>
> Personally I find Customers.Col1 easier to read then C.Col1
>
> Regards
> Tushar


I agree for such a small example. But it becomes a very different reading - and writing - experience when there are twentyfive columns from six tables, their JOIN conditions and a slew of WHERE conditions and ORDER BY columns are added and 15-byte long table names are repeated fifty times in the query. That is also the way a query utility writes it by default ,but please consider the plight of the poor bastard who has to write all of it by hand, and spell it right every F time.
No siree, not on my watch.

-Anders