>>Just something to think about...
>>
>>Selecting NO workarea is tricky by itself.
>>Just a few examples. As you know, SELECT command selects only between existing workareas, or you SELECT 0 for unused area. Select NO workarea can be done only by closing the table in the current area. If you have the grid in the form, the specifically selected workarea automatically switches to the grid workarea if the grid gets focus.
>
>Yes, that's why I've had a wish list item for some time to make this easier. And I suppose that grids will always present the problem. But SELECT 0 should always do the trick (except grids), no?
>
>>
>>Following a good naming convention for the fields and variables minimizes the possibility of mixing them.
>
>But as you know, "good naming convention" is in the eye of the beholder! Some people, for instance, insist on using Hungarian (or a variation) even on field names!
>
>I think that even over-using "m." is far safer than never using it.
>
>cheers


SELECT 0 should be good enough (unless there is something like grids in sight :)

I myself typically use some kind of prefixes on the fields. But in corporate environment it might be not possible - often you are given the "approved" table structures where fields like SYSTEM, NAME, NOTE are left and right. :)

BTW, just yesterday I had somebody came to me with a statement: "There is something weird in FoxPro! I assigned 5 characters to the variable and LEN(source1) shows me 255 in the Debug window!" Guess what... :)