>While I value having fun with this - I´ll sponsor you a drink if you finally give your POV to my suggestions here and in # 1055316.
>Thanks
>G

Hi Guenter,

While I agree that it would be great to have SPT statements in VFP benefit from syntax checking, Intellisense and other features at design-time, I think that the most difficult part would be the actual implementation of such features; whereas their triggering would be the easy part :).
Yet, there's a lot to do on SQL SELECT syntax checking in VFP, where things like

SELECT * FROM source INTO destination ORDER BY

(.. note the missing argument on the ORDER BY clause),
are causing only run-time errors (i.e. SQL: Coulmn ORDER is not found) while the statement is considered ok at compile time. Some may argue that due to the declarative nature of SQL, this may not be a syntax error, though it's definitely ambigous. <g>
As for Intellisense, I am wondering if/how the current benefits for SQL statements could be extended. Some may argue using remote views for bringing data structures into the development context. Unfortunately, I haven't had much experience with RVs. But if the RVs were beneficial in this respect, then issues like the one above could be further clarified through Intellisense detecting that ORDER is not really a data column.

On the other hand there's LINQ ...and suddenly all these issues have a name.

:)