1. do you have a test and live environment? Make sure all of your views and stored procs are the same in both. Make sure ALL of your sources in your report (and subreports) are pointing to the LIVE source.

NOTE: I have this set up and can't tell you how many times I have forgot to update 1 little thing and it all goes to pot. Very hard to figure out what you are missing.

2. check your select statement to make sure you did not filter out items you think you should be getting.

3. If you are using joins and or select statement in crystal, mimic it in SQL to verify that crystal should be seeing the data. Just becasue you can see it in SQL does not mean you did not filter it out by the time the report is displaying.

 

OMG. I figured it out and I'm none too happy but I'll get over it.  My database is an Advantage database underlying a medical billing app that I'll call Alpha (because I certainly would not want to call out the @$!!%^$ software company by name).

 

Anyway, it just dawned on me (OK, I should have figured this out before) that we did an upgrade on the same day that was the endpoint for my data.  A lot was going on that day so the correlation wasn't as obvious to me as it should have been.

 

In any event, the data tables were renamed and relocated in this upgrade.  The old tables were in c:/alpha and the new tables are in c:/alpha/data.  Now that I know this, I thought I could simply use the Datasource Location function to  point CR in the right direction.

 

This is where I (still) need your help.

 

Using the either Database Expert or the Datasource Location function, I only see the standard database tree (Current Connections, Favorites, Hisotry, etc.) but I do not see how to repoint CR.  CR sees the old c:/alpha location (which still has the legacy files in it) but apparently does not see c:/alpha/data.  How do I force CR to look at C:/alpha/data?

 

Thanks.