** One thing you might look at would be putting the ODBC users on their RPC thread. I know this won't help with timeouts (maybe if it is Remedy timing out) but at least those users won't be tying up database threads that are being utilized by end users within the application.


On 10/13/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
**
Stephen:
 
The only method that I know of to fix this is indexing.  Sadly, the value used for database retrieval is fixed and is being exceeded.  You don't state which database you are using either....
 
James McKenzie
L-3 GSI
 


From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Stephen Lumini
Sent: Friday, October 13, 2006 9:46 AM
To: arslist@ARSLIST.ORG
Subject: Crystal Report timeout

**
Hey all,
 
We are having an issue with Crystal Reports that are timing out.  They use the Remedy ODBC driver to get to the DB.
 
The reporters want to be able to extend the timeout value.  There isn't time right now to look at making the reports more efficient.  After contacting Remedy, the best I got was to make changes to the AR.ini file which may or may not help.
 
Anyone else fix this problem?
 
Thanks
Stephen
ARS 7.0


Share your photos with the people who matter at Yahoo! Canada Photos __20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___



--
Frank Caruso
Specific Integration, Inc.
Senior Remedy Engineer
www.specificintegration.com
703-376-1249 __20060125_______________________This posting was submitted with HTML in it___

Reply via email to