We recently installed a new case management system that enables users to connect to the SQL2000 database via a client/server app or web server app.  The system has Crystal Reports integrated into it.

Whenever I create a report and add it to the system, it works fine in client/server but generates an error on the web server. The last thing I heard from support was "You have to have use LFREPORTS as the user to develop reports that are to run in the web app." LFREPORTS is a SQL login & database user on the SQL server. LFREPORTS has database roles of public & datareader.

They've also told me that this "user" is "hardcoded" in the report. I have no idea what that means.

LFREPORTS is not a network login and shouldn't have to be, right?

I created an ODBC connection to the database and logged into it with LFREPORTS. The Crystal Report based on that connection causes an error in the client/server app and hangs in the web app.

I'm stumped. I've asked for clarification from support but I feel like I'm playing 20 Questions with them. Does anybody know what they're talking about?

Thanks,
Jessie

I spent all day trying to resolve this. I finally got it fixed after 40 minutes on the phone and a WebEx with support. I had all the pieces installed and configured correctly. It took a "repair" of the service with one of their utilities to set things to rights.