>>Does anyone see a problem with creating new methods and properties in classes and using the same names VFP already uses.
>>
>1. As a general rule I NEVER use any names VFP already uses. That practice WILL come back and bite you.
>

Al, Roi,
I try to always use method names that are familiar so my own language requirements don't grow and grow.
I add Release to controls that don't have them. I add Requery or Show as custom methods where I need that behavior. I have the Visual Interdev Scripting Ojbect Model on my wall so I have access to the MS naming of properties and methods from many other classes. So I commonly add methods and properties like:
Advise()
Submit()
Move()
MoveNext()
Open()
State
Write()
Do()
BookMark
ActiveJob
ThisReport

Just trying to add a contrarian point of view.

Charlie