After upgrading to 400a from 200, the search lookup in the prompts screen for the ICRs are no longer working. They just hang.. We are in a Progression SQL environment. The Reports themselves work fine as long as you don't have to do any lookups when entering in the data. Any thoughts?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ICR - 400a 1
- Thread starter gc6294
- Start date
If you run the same report only using the cobol report instead of the ICR, does the search work? They use the same search AFAIK.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
- Thread starter
- #3
- Thread starter
- #4
You went from 76200 to 76300 first correct?
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
- Thread starter
- #6
Did you test ICRa at that point? There was a known issue when updating to 76300 at one time.
I try reinstalling the Macola client, if that doesn't work you need to call Exact.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
I try reinstalling the Macola client, if that doesn't work you need to call Exact.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
-
1
- #8
I have the same issue and one of my friends called me about it as well. I checked the sqlsrch_sql table and all looks fine. I also checked the .epj file for the report I was running and it seems to be calling the correct search function, which should be the case since the top search works, just the alternate ones.
I ran profiler against it and found that at least in my case, when it searched on the IM-ITEM one by Item Description it was trying to use the following command which as you can see is wrong:
exec sp_cursoropen @P1 output, N'Select ITMIDX_SQL.search_desc, IMITMIDX_SQL.item_no From ITMIDX_SQL
As you can see, it's dropping the leading IM from the table and description field. I can't say I know why but my friend is sending it to support.
Kevin Scheeler
I ran profiler against it and found that at least in my case, when it searched on the IM-ITEM one by Item Description it was trying to use the following command which as you can see is wrong:
exec sp_cursoropen @P1 output, N'Select ITMIDX_SQL.search_desc, IMITMIDX_SQL.item_no From ITMIDX_SQL
As you can see, it's dropping the leading IM from the table and description field. I can't say I know why but my friend is sending it to support.
Kevin Scheeler
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question