>The problem with logging is that it's rarely done in a way that's exensible and doesn't add overhead to the system. There are ways to log that don't add alot of overhead, but how you do it depends on why and what you log.
>
>>I decided to move the logging part back to the caller. I am logging in the text file string like this
>>
>>"Calling Remote ModifyPass On {0} with: {1}", ip, invokeString

I guess in our case since we're re-writting VFP code and we're used to logging, we use a Logging class that adds strings to the local file.

The call to this method looks like this

Logging.Log(3, "Some string"); where the first parameter is verbosity level (so, if the verbosity level is 1, then nothing gets logged).

I haven't looked closely into the actual implementation of that class, but it's used in many of our applications.