>Hi everybody,
>
>About 4 business days ago I got a complex footprint assigned to me. There are two forms and one class involved with complex convoluted logic written several years ago by a person who has long since left the company. The class uses gridhittest method.
>
>I've been looking at the code and making numerious changes trying to fix few bugs. Unfortunately, each attempt to fix the problems resolve in something new and ugly surfacing. I am basically ready to give up and ask my manager to assign another developer to this problem. I will release what I currently have, I think.
>
>The problem here is:
>
>1. We need to fix the problem in 2 versions of software. The code base is different, so we would need to apply similar fixes in two versions
>
>2. I've been working with the latest version and, as I said, made a numerous changes. At this point I am not even sure that all of my changes are correct or if they solve the problem or introduce the new one.
>
>I am wondering how to handle such situation and admit that I am beaten here?
>
>Also, I've been working on C# code for a while, but because I got that assignment, I had to put that project aside for the time being.
>
>Any ideas?
>
>My manager is a very nice person and I guess I can call her and tell that I need a break from this assignment. Just need to get up the courage to call. I am also not certain how will it work.
>
>Thanks in advance.

Is this the Dapfor.net.ui ?

I've spent a lot of my career doing project rescue - i.e. trying to figure out some code that never quite worked written by some guy who is now in hiding ;-) It is easy to get to a point where you realize the path you have been going down trying to fix his stuff isn't working. That means you understand the problem better now than you did at first.

Sometimes the fastest way to get to a better place is to roll back to where it was when you took it over and rethink your design assumptions about how to fix it, knowing what you know now.

Releasing something you know has problems or that isn't really a solution is not a good idea and if you haven't fixed it at this point it is probably because there was a better path to a solution.