>>Some people (likely to keep their typing down) rely totally on VFP (for example) to do it's default behaviour and so save additional line by letting VFP do it for them. My preference is to (virtually) always code things like "ALL" after SCAN or "USE IN..." for tables/cursors regardless, SELECT after a CREATE CURSOR, etc. I use "m." where it should be used and some people detest that.
>
>As I see it, a prerequisite for EVERY professional VFP-developer is a thorough knowledge of the DEFAULT behavior!
>
>If a developer writes a SQL-statement and the next command is always a SELECT of the just created table or cursor, then the first thought that comes to my mind is that this developer was unsure about the capabilities and possibilities of VFP, and probably a relative beginner.

I understand that. And I don't care what the (next) reader thinks I am, but rather how well they can work with the code.