Ok, Build 41 was pulled due to a problem with keywords and alias parsing.  The documentation has been updated, and it is explained a bit below as well. * * * * * * * * Build #42, 10/9/2007 * * * * * * * * ***** NOTES ***** Certain keywords are required to be bracketed for usage. Examples: key statistics user We have updated the error stack as well to read like this:

Error 592: Invalid token in statement: select Error 509: Invalid statement: select Error 617: Name or alias cannot be reserved word: user

Note that the inner error tells you the exact keyword with the problem. This should help in diagnosing the problem. This can almost always be corrected by [] the keyword like this:

select [user] from tablename;

If you have a column name that is also a function name (like STR or TRIM) you should also bracket the column. Some of these restrictions ARE changes.  This is part of our attempt to be more SQL Server compliant getting ready for the TSQL Procs.  I apologize for us not fully documenting these changes prior to the release of Build 41. We should have released as a development build and gotten more feedback.  Lesson learned. **************** ISSUES AND FIXES **************** #277: Column names Key causing errors - Keywords must be bracketed when used in where and order by clauses. #278: Group By failing - KEYWORD usage in group by requires [] around the keyword column correctly now. #183: VB.NET sample project compilation problem - Fixed OTHER NON TICKETED ITEMS ************************