One way to debug reports is this:
- Change your REPORT FORM command to a MODI REPORT command
- Run the application and pick the report
- When the report designer comes up, choose preview
- After the error happens, the report designer should return with the dialog of the offending object activated.
Now you can look at the expression, and the Print When logic, and any other place that might have code associated with it.
>Greetings.
>
>I have a report that returns a "<
> is not an object" when it is run. The only thing is that it happens randomly. Is there an easy way to debug a report form - where it actually tells you which field in which the error is occurring?
>
>This has been happening to us for some time (even before I started here over a year ago) and I would like to figure out what is causing it. The application is in VFP3.
>
>Any ideas are appreciated.
>
>Rhonda
