>>>Do you really think anyone here wants to look at hundreds of lines of code? You alos totally evaded my point of refactoring the vfp code to .net. You can't see how .net would help you, becuase you still think in vfp term or use whatever method you may happen to run across without learning the why's and wherefores of the code.
>>>
>>>As to what you've posted, its a complete mess and needs to be seriously redone. Those methods are not complex, they are a pile of italian pasta waiting to cause nightmarish problems.
>>>
>>>Do yourself a favor and listen to what the others have been telling you. You read, but do you understand? I think not, you'll end up doing it the way you've always done it, expecting a different result and then wondering why it doesn't work.
>>
>>I read and understand. What I showed you is the method I have as input - VFP method. I need to duplicate its output.
>>
>>So, given that VFP method I showed you how exactly should I approach re-doing it in C# to arrive at the same XML string I need to pass back?
>
>
>This is called problem reduction. Transform a problem into a number/sequence of smaller (sub)problems
>
>A (sub) problem can easily be method
>
>It's possible that a sub problem can be divided again in smaller problems

That's exactly what I just done. For that method we were talking about I made about 6 different sub-tasks. I may try to make them even smaller. The problem is to keep it working after re-factoring. I also don't like the fact I need to pass many parameters from one method to the other, so I think I may do it better.