Hi Ludek,
Thanks for your response. After I was getting the sub report to run when I put it in a different place on the report, I figured I would rebuild the report by scratch going from sub report to sub report. Well to make a long story short the problem went away after the report was rebuilt. The "problem" report was originally tied to a different system that used tables instead of stored procedures. I used that report and remapped the fields to point to the new ones in the stored procedure. I can only assume that there may have been something there that crystal reports did not like.
Thanks again
Brad