Perfect. That was the exact issue. I had added a command to the database expert that I thought I needed. I deleted it and everything works - apparently I didn't need it to get the results.
Thanks.
Thanks.
--- In vantage@yahoogroups.com, "Vic Drecchio" <vic.drecchio@...> wrote:
>
> Do you have any Crystal parameters or perhaps you have Subreport Links that
> are awry?
>
>
>
> I've seen it happen due to both circumstances above.
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> kurt_hilborn
> Sent: Monday, May 20, 2013 10:24 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Epicor 9 - Sub report in Crytal Reports causing reports
> to go to Prieview
>
>
>
>
>
> Any Ideas on this one?
> I just added a subreport to one of my Crystal Reports that does a DB query
> to pull in extra data that I couldn't get from the report itself.
> The report runs but when you try to print it instead of going directly tot
> he printer it comes up in Preview Mode first. You can print fine after that.
> Then when closing the Preview panel Epicor throws the following error:
> Error Detail
> ============
> Object reference not set to an instance of an object.
>
> Stack Trace
> ===========
> at Epicor.Mfg.Lib.Report.EpiCrystalReport.CleanUpRptList()
> at Epicor.Mfg.Lib.Report.EpiCrystalReport.Dispose(Boolean disposing)
> at Epicor.Mfg.Lib.Report.EpiCrystalReport.Dispose()
> at Epicor.Mfg.UI.App.SysMonitorEntry.Transaction.ProcessAutoPrintRequests()
>
> I've checked the subreport and can't seem to figure out what is causing the
> issue.
>
> Thanks
>
>
>
>
>
> [Non-text portions of this message have been removed]
>