Date Syntax

Small progress.... I don't like this solution but it works.

Create "String" Parameter Fields (StartDate & EndDate) - prompt user to enter "yyyy,mm,dd" format in entering date.

Use formula:
{REVIEW.SCHED-DATE} in Date({?StartDate}) to Date({?EndDate})

Try this: In Crystal, go to File --> Options --> Fields --> Date and Time (button) --> Date and Time (tab)

Select a date only style, for example "03/01/1999"

Change your beg and end date parameters back to a type of "Date".

Now try your original selection criteria (ie {REVIEW.SCHED-DATE} in {?Beginning Date} to {?Ending Date}
)

Thanks, Chris.

I did as suggested. When I loaded the report to LBI and executed the report, it prompted me for the dates parameter using "01/31/2000" format. When I click "Run", another date parameter window appears - this time, it's asking a "yyyy-mm-dd" format, and right underneath the form shows a "Business Objects X" with a red x. If I then enter the dates in the format requested, then the query executes.

Any thoughts?

Wish I could post images.....

What version of LBI are you on?

good question.... let me find out really quick.

Version: 9.0.2.1.60

Do you have RAS installed on a server separate from LBI?

Jojo, are you having this problem in Crystal Reports itself, or when running the report after publishing to LBI?

after publishing it in LBI. I can only test the report in LBI because Crystal Report shuts down when I try to run the report. Error log says that there's something wrong with crqe.dll - but I've done everything I know of to repair it, yet haven't been able to fix the problem...

as far as RAS, if that stands for the Crystal server, then no. It is installed on the same server the LBI is on.

Do you have Crystal Reports installed on the LBI server? It's recommended that you do not. As far as your issues with Crystal Reports, what version are you working with? Have you tried reinstalling? Have you applied the latest Service Pack and Fix Pack?

Regarding the "red x" you are seeing at the parameter page in LBI, it sounds like the LBI jar files are not in synch with the RAS jar files. I would open an LIS ticket. Have you applied the RS update for 9.0.2.1?

I'm using CR XI - Pro

I didn't know about the CR not recommended to be installed within the LBI server. The reason being, I've installed the CR in my local PC, but when I tried to create an OLE DB connection, the Lawson OLE connector is not there - so I kept the CR in the LBI server.

As far as updates, I checked for updates via the CR help menu and returned no updates for CR.

I will try to open and LIS ticket, today to see if if gsc can help.

I have not had any problems with having Crystal Reports XI and RAS installed on the same box. One recent install did have a very subtle error which was in the install, where it didn't copy the crystalviewers* subdirectory to the LBI directory. In this case (and in Jojo's case, I think that GSC will reject this as an installation issue, and point you to needing some consulting help.

Jojo, The reason the Lawson OLEDB connector is not on your PC is because it needs to be installed as a separate component.

I would concentrate first on getting this report to run correctly within Crystal Reports before troubleshooting the LBI aspect of it.

Agreed on resolving any CR issues before spending too much time on the LBI issues.

I also have not had any problems having CR and RAS on the same box, but Lawson Support will advise against if it comes up during a ticket.

Previously I said the jar files are out of sync but meant crystalviewer files, which is the issue John is referring to (a symptom of which is the [i]"Business Objects X" with a red x"[/i] on the LBI parameter page with some types of date parameters). If you open a ticket with Lawson Support, they will likely advise you to 9.0.2.2, but if pressed can provide a manual workaround to resolve this issue (essentially syncing up the crystalviewer files).

Here's the manual workaround:

Stop RS.
Make a back up of the following folder: ...\LawsonBusinessIntelligence\ReportingServices\...\crystalreportviewers11
Replace it with the crystalreportviewers11 folder from ...\Program Files\Common Files\Business Objects\3.0\
From the backed up crystalreportviewers11 folder copy WEB-INF and META-INF, paste these into your new crystalreportviewers11 folder.
Delete the contents of ...\LawsonBusinessIntelligence\ReportingServices\...\WEB-INF\lib
and replace it with the contents of:
...\Program Files\Common Files\Business Objects\3.0\java\lib

Any files that existed in the ...\LawsonBusinessIntelligence\ReportingServices\...\WEB-INF\lib folder but not in the ...\Program Files\Common Files\Business Objects\3.0\java\lib folder
-OR-
...\LawsonBusinessIntelligence\ReportingServices\Reporting Services.ear\...\crystalreportviewers11 but not in ...\Program Files\Common Files\Business Objects\3.0\
will need to also be copied over from the back up folder you create.
Restart RS.

cool. I'll try this workaround to see if it'll fix the problem.

... made by head loopy reading it, but it makes sense

Thanks, gentlemen. I'll report back in a few.

nevermind... found it.

Chris, I performed that workaround and CR is still not working right. It's shutting down in the middle or a report being processed.


"Faulting application crw32.exe, version 11.0.0.895, faulting module unknown, version 0.0.0.0, fault address 0xf08c15ff."

Google results isn't much.

The workaround is to address the LBI issue you reported ("red x" on the parameter page). This will not address the issues you are having with Crystal Reports (CR)

I would try reinstalling CR, or install the OLE DB connector on your local pc where you also have CR installed and see if you still get this error. If you do, I would recommend 1) patching CR XI (search the Business Objects website for CR XI service packs), and if that doesn't resolve it 2) then reinstall CR XI and reapply the latest CR XI service pack

Jojo, going back to the first post..."The field "SCHED-DATE" in an Oracle table ..." What type of data source are you using for this report? Is it an Oracle ODBC, Oracle OLEDB, Lawson OLEDB? Etc. etc. The first thing you need to do is get the PC straightened out...so that you can create and run a simple Crystal report against the Oracle database, then add the Lawson OLEDB connector, and create a report using that. The problem is that you're trying to troubleshoot three separate issues without resolving the main one--that you can't get the baseline report to run on the PC.

Oh ok. I understand what you're saying, Chris. I'll look for the the lawson OLE DB connector and install on it on my PC - I'll test and will let you know.

John, I'm using Lawson OLEDB. Simple reports will run just fine. I can run a different report with a simple query to one specific table and collect all the information requested. I can also run a repot with a little bit more complex query, but only if I'm asking for ONE specific record. If I do range... (ie from this employee # to this employee # or from this date to that date), CR will then shutdown. I have not tried creating a report using a different connector - I will try the Oracle connector and see if that works.

Thanks again!!!

I created a new report using Oracle OLE DB and it works just fine - it's a lot faster too. It leads me to believe that there's something wrong with the Lawson OLE DB connection.....

Jojo, the Lawson OLEDB provider will always be slower than the native database (Oracle in your case) provider, since it's operating over the web server, and also adds additional layers for security, etc. See https://www.lawsonguru.co...Crystal-Reports.aspx for a more thorough discussion...

Make sense.

I've got another issue at hand, so I'll get back into this as soon as I finish the other... custom security.