on 2024 Dec 19 5:00 PM
Is there a way to prevent Crystal Reports 2020 asking for login information for dynamic parameters?
Our users use the report via a viewer that our ERP system uses. It passes along the login.
Request clarification before answering.
Hi Greg,
Ah, FireDAC must have a Client Database connector that CR uses to connect to it.
CR 2016 is a 32 bit application and CR 2020 is a 64 bit application so it requires a 64 bit Client.
The way CR works is when the DB connection is made CR stores the log on info in memory and releases the connection so the Client doesn't get hit with potentially 100's of connection requests. Normal behaviour...
I suspect what FireDAC is doing is releasing the connection, so each CR parameter will open the connection to pass the parameter to the Client/DB. FireDAC appears to be closing each connection. Because CR Parameters must be set before the connection is made, it's like a Stored Procedure with parameters, the value must be set before the log on info is attempted.
If you enable CRLogger, KBA 1603398 - How to trace data source connections in Crystal Reports using crlogger? [Video]
The log file may show what is happening...
I suggest contacting FireDAC support and ask them if they have a 64 bit Client or if they could have a look at your issue, the log file may help them determine what is happening and why the connection is lost every time a refresh is completed.
Nothing in CR configuration to make this work, no difference between CR 2016 and CR 2020 has changed for this work flow...
Don
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
60 | |
10 | |
8 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.