>Does anyone see a problem with creating new methods and properties in classes and using the same names VFP already uses.
>
>I'm creating my own control from a container and want to add a 'Requery' method to it (it doesn't have one now).
>
>I'm just paranoid the VFP will decide to add one in some later release and it will cause a problem.
>
>tia
A couple of points:
1. As a general rule I NEVER use any names VFP already uses. That practice WILL come back and bite you.
2. My personal preference is to use a prefix for custom properties/methods e.g. "MyApp". You would then create MyApp_Property1, MyApp_Method1, etc. I use this approach because I work with a commercial framework that already has tons of custom properties and methods, and this technique lets me easily find mine amongst all the others.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up