Yeah, it might be very good thing to do like following:

Use sometable object MyTable
select Mytable
scan all
MyTable.Field = 'something' && !!!
endscan

? MyTable.Sum('Field1')
MyTable.Update(.T.,.T.)
MyTable.Revert()
MyTable.Skip(10)
MyTable.GoTop

etc etc

>True enough Mike, and I agree. Hopefully, the programmer would be on-the-ball enough to pay attention to naming conventions. Actually, the wrapper class approach bears tremendous merit. Consider:
>
>SCATTER NAME THIS.ioMyEntity
>
>where the current table has some the structure:
>
>emp_name
>emp_ssan
>emp_id
>
>The wrapper class cstEmployee might then have the following:
>
>cstEmployee.qcEmployeeName( )
>cstEmployee.qcSSAN( )
>cstEmployee.qiEmployeeID( )
>
>The query methods then have the knowledge of how to access the data brought in using the SCATTER instruction. Client objects to cstEmployee are then free to be constructed only having to know about these queries.
>
>Like I said, the wrapper class notion has a lot of merit.
>
>Larry