Hi I am new to Logicity but a long time crystal developer. I have successfuly ran simple reports using Logicity free version. I developed a report today that uses dynamic parameters to select the parameter options from the database and also includes a subreport.

When I run this report from Logicity free I get a login failed every time. I can run other reports successfuly that are pretty vanilla with few if any advanced features or formulas but not this one.

I have a feeling it is trying to select the dynamic parameter content before the login is passed, or its simply not supported but I am not sure.

Anyone know more?

deleted

deleted

deleted

Ok this is really strange. I have officially discovered that simply opening the report file in logicity is causing the I-series to lock my account. If I open the report in logicity, let it lock my account, go into the i-series and re-enable my account, then go back to logicity and enter the login the report will actually run.

I have a very similarly developed report that does not do this. That report opens in logicity, prompts for login, I login and everything works fine.

What would prompt the Databsae to lock my account when I have not tried to authenticate yet? Does logicity try to authenticate on its own when the report is opened? If so why does the other report work fine?

I am so confused.

Ok I have a reproducable behavior figured out. The reason the one reort was working is becasue it was developed under a different
IBM account. I confirmed it was locking that acocount when the report file is opened in logicity then when I changed the login to an enabled account that was not the default account it worked.

Here is a step by step breakdown
Connection type 32 bit ODBC IBM-Iseries Access ODBC v13.00.01.00

1.) Report is developed in Crystal XI using IBM user account "A" and saved
2.) Report file is opened using Logicity and a default login prompt for IBM account "A" is presented by logicity
3.) The Logicity prompt seems to lock IBM account "A"
4.) Change the logicity login prompt to an enabled IBM account "B" and the report runs fine

This also works
1.) Report is developed in Crystal XI using IBM user account "A" and saved
2.) Report file is opened using Logicity and a default login prompt for IBM account "A" is presented by logicity
3.) The Logicity prompt seems to lock IBM account "A"
4.) Login to IBM server and re-enable IBM account "A"
5.) complete login to logicity with IBM account "A" and report runs fine

Why is logicity locking the default IBM account that it prompts for login? There seems to be no way to prevent it, it locks as soon as the file is opened.

Well I understand this is a free tool, but ummmmmmmmm anyone?