>Sorry I got it wrong.

Glad I saw it that early (You replied to Ken about it!) and we could clear it up.

>I too use [] with SQL server often and my workaround was to name #define variables with awkward prefixes to prevent a collision.

I´m not sure I understand. Example?

What *I* was referring to was the mystery around 'Fox' db functionality to come in C#3 / VB3 (actually .Net) / Orcas. Anders Hejlsberg, the topmost C# guru, lifted the veil of secrecy at the PDC. In the meantime there are numerous Level 900 ;-) articles at
http://msdn.microsoft.com/netframework/future/linq/

When Anders talked about "LINQ allows query expressions to benefit from ... compile-time syntax checking, static typing and IntelliSense that was previously available only to imperative code."...

I thought we could have even *design* time syntax checking and Intellisense in VFP *very* cheaply, if the editor and Intellisense treated the [] delimiters like they´re treated at pre-compile time - transparently.

"select * from authors" would be a string and opaque anyway.
[select * from authors] could be syntax checked and Intellisense could kick in - just analoguous to what´s actually a find and replace at pre-comiple time. E.g.

#define db_tbl "authors"
[select * from db_tbl]

So what´s your take on this?
Cheers
G