Verify on Every Print

Question

Hi,
We're using embedded Crystal Reports in our C# .NET application. 
So when deployed, no RPT files are distributed because they're embedded in the Crystal Reports project assembly.
All our reports are based on datasets (xsd files).  When creating a report, we connect to a xsd file that resides on a physical path on the development pc, and that dataset structure is then visible in the Database Expert.  In it's properties, there's still a link to the original path.
When printing the report from the application at runtime, a dataset with the same structure is pushed to the report and the data is printed.
By default, on every crystal report, the option 'Verify on Every Print' is checked.
Although the path holding the xsd files that were used to create the report upon, does not exist on the client computer, everything goes fine.  No errors, report is printed fine.
The question is : what does the option 'Verify on Every Print' do exactly when deployed on a client machine ?
I've tested multiple situations (more fields, less fields, renamed fields, etc..) with and without the 'Verify on Every Print' option, but I don't seem to find any differences in behaviour.    Are there any differences ??
Thanks,
Vincent

Answer 1

Hi Vincent,
It is more for connecting to databases directly, XSD files should not change and because they reside in memory you won't see a performance problem.
I suggest you don't use that option, it's more pertinent while designing reports than using published and verified reports.
Thank you
Don