Returning true or false is generally frowned on in a .Net application. In the case we're talking about in this thread, Naomi is dealing with an external C++ application. Unless she can change that program, she has to return a string.

>I know this is not related to the prime topic of this thread, and we might discuss it in a new thread, but "our returned string" grabbed my attention. I understand this is an old concept which came from VFP with the "by reference" approach. But, I try to stay away from that and have each method to simply return True or False for the success of its operation and store the related values in the class property. That can then be easily evolved furthermore without having to change the structure of the class/method.