Area Sub Function not calculating correctly

[cnash52]

Could someone take a look at my Public Sub Area ()? It looks like it is calculating the area between the two graphs incorrectly and it is very important this piece is accurate. I need to calculate the difference between the areas of the two graph lines and list that difference in cell (A,94). A is the row in reference. The Sub is found in Sheet 6 of the attached excel sheet (sheet example with data) and below:

Please Login or Register  to view this content.

ExcelArea.xlsb

Thank you very much in advance.

[MrShorty]

Debugging can be as important as coding. Is there a specific part of debugging this that you need help with? I cannot see anything wrong in a quick perusal. Why do you think it is giving you an incorrect answer? What answer do you expect.

Here's how I would go about debugging this:

1) Set up a scenario where I know what the answer should be -- and where I know all of the intermediate values along the way. If you know the solution and intermediate values to either one of the scenarios in your sample, that should be good enough.
2) Add Stop statements at key points in the procedure. One should probably be right after the block If that is calculating Area1 and Area2
3) Run the code. When it stops, check the values for each variable and see if the value currently stored matches the value I know it to be. If everything matches, then continue to the next stop statement (or step through one line at a time).
4) Continue this until you can identify the calculation steps that are different from what you know them to be. Then you can focus on those quantities and calculation steps to figure out what you need to do differently.

I know that this can get tedious and frustrating. We'll be happy to help where we can.

If it helps, I set up one test case that I think should help (assuming I understand what you are trying to do here). This case should exactly match the red and green curves in your graph, so that the area between the test row and your curves should be 0. It obviously isn't, but it might be a good test case to see what is going on.