Hi Don, we've finally figured out what our issue was and I wanted to provide an update. When we configured our ASP.NET website to connect to the database (ORACLE 12c), we use TNSNAMES to connect. Some databases requires a .world qualifier to connect while others can just use the SID without any .world qualifier. However, we add the .world to all of our connections just to make sure since we thought it made no difference, but apparently that makes a very big difference with Crystal Reports. We've been expirencing some odd issues as well with our ASP.NET application, so we believe it's a combination of using Oracle 12c and doing the .world qualifier. Once we removed the .world qualifier from the connection setup, we got the good performance with Crystal.
We're working with our DBA team now to configured our databases to be the same as our QA environment which doesn't need the .world qualifier to connect.
Thank you for all your help with the issue.