Running Crystal Report in Epicor 10

Today is our first day “live” on Epicor 10.1.400.24.

So far so good… but we have about 80 Crystal Reports from our old Vantage 8.03 system that I need to be able to use in Epicor 10 until I can get them all re-written.

For all of the reports I’ve changed the connection in Crystal Reports from “ODBC” to “OLE DB (ADO)” to connect them to my SQL database. I’ve added them all to the menu structure in Epicor 10 and they work great.

So what’s the problem?

Well, they only work great from the menu structure in Epicor 10 when they are ran from my PC.

If I log on to Epicor 10 from any other PC I cannot run any of the Crystal Reports in Epicor.

On any other PC, I click a Crystal Report in the menu structure. The “Crystal Custom Report Maintenance” window comes up, just like it should. When I click the magnifying glass icon, a login box appears, asking for the password for the “sa” account on the SQL server. I type it in and press ok, but it asks for it again. Endlessly in a loop.

Any insight into what I’m missing?

Steven

I’m wondering in menu setup what the the Program Types are?
“BAQ Report” or “Custom report Link”
i.e. using an XML file generated by E10 or somehow connecting directly to the database?

If these are custom report links you might need to duplicate your connection/credentials at each workstation.

Thanks for jumping in.

The program type says “Crystal Custom Report Link”.

Is there a way to create a OLE DB (ADO) connection at each workstation?

Steven

My Epicor reporting consultant says that OLE DB (ADO) connections are stored in the report file itself.

ADO, ODBC
There should be a way to set up credentials for all users but will depend on how the reports look.

If you have access to EpicWeb might check there for answerbooks that go over some of the options

Off the top of my head here are a few of the ways
Crystal ADO to connect to the XML files generated by the system for BAQ reports
Crystal ODBC - set up ODBC DSNs on each local system for custom reports that connect directly to the database
Or you might be able to embed credentials right inside the Crystal report
And in E10 - you might be able to use Company Maintenance - Email and Reporting - the fields for the ODBC connection?

Solved!

Our consultant noticed that I had a different version of the “SQL Server Native Client 11.0” driver. We downloaded the latest driver and the issue was solved.

Thanks for all your help!

Steven

PS - Sorry. The new driver wasn’t the only change. I had to uncheck the “Integrated Security” box and add a username and password for an account on the SQL db when setting up the OLE DB (ADO) connection.

1 Like

Steven - did you have to install the driver on the server or each work station?

On each workstation.