[AccessD] events question

I have no idea what you mean, John. If I do a project-wide search for
SortByColumn I find it quickly (granted, I use Rick Fisher's Find and
Replace; another alternative is Speed Ferret -- but either way, if Joe
SixPack wants to monkey with the code in the absence of the requisite tools,
then every instance of damage is Joe's fault not mine). If I find one
occurrence that is not the declaration, I stop the search and double-click
the word, then press Shift+F2 and I'm in the function.

And what the hell is Joe doing cruising the code and deciding what's
necessary and what is not? That kind of customer belongs on my list of
Customers To Fire.

Further, if Joe SixPack touches the code then any consequences are not my
responsibility, any more than if Joe incorrectly prices a 74-inch
flat-screen TV at $300. Not my problem!

As the old adage goes:
I charge $80/hour.
If you want to watch, it's $150/hour.
If you want to help, it's $300/hour.

This is not to say that I dislike working in teams. In fact, I am a
proponent of what is called the XP (eXtreme Programming) school. But this is
not equivalent to working alongside Joe SixPack. I'll go further. If Joe
SixPack wants to monkey with my code, I'm "hands off" until he screws
himself. Then I turn the clock on and everything is billable.

Arthur

On 12/7/07, jwcolby <jwcolby at colbyconsulting.com> wrote:
>
> Arthur,
>
> In general I try to dissuade people from doing that for the simple reason
> that the name of the function is not easily findable.  Joe Six-pack
> searches
> for SortByColumn in his code window, and (not understanding what it does)
> not finding it referenced anywhere decides that can be safely
> deleted.  Only
> when the user actually clicks on a control that references that function
> will the problem be discovered.  No compile error because the control
> property references a non-existent function.  BAD!
>
> Sometimes the best ideas have side effects that make it not such a good
> idea.
>
> At least if a control scanner is setting the property programmatically,
> the
> name of the function will be found and this error avoided.
>
> I do like your sort by column thingy though.  Done at the framework level
> that one will be a keeper.
>