In Crystal Reports (CR), a report is created and refreshed against a secured database. The report is saved. When the report is opened and refreshed, the user gets prompted to enter a user name and password to access the database.
Why doesn't the report save the log on credentials entered when the report was created?
CR does not save database log on information and will not bypass database security. This is by design in CR. To avoid being prompted to log on to a secured database each time a report is refreshed, use Microsoft Windows authentication. This is known as a trusted connection or operating system authentication. A trusted connection checks a user's network user name and password as authentication. The database server checks this log on information instead of log on information specific to the database.
Your database server must be configured to allow a trusted connection. To find out if your database supports this, consult the database administrator or refer to your database documentation.
DATABASE LOGIN PROMPT SECURITY AUTHENTICATION REFRESH USER NAME PASSWORD Crystal Reports Database prompt NT Authentication , c2011331 , KBA , BI-RA-CR , Crystal Reports designer or BusinessViews Manager , Problem