We're using ODBCExpress v5.07 to talk to a SQL Server 2000 database. Up until recently this all worked just fine.
However we now get an application hang. (luckily this is against the Testing database and Production is running fine) We are running a sequence of SQL statements (some SELECTS, some Stored procedure calls) though the same THstmt in a single transaction. Most run fine, but there is one particular Stored procedure call that runs but doesn't appear to pass it's results back through ODBC correctly causeing the aforementioned application hang. Using SQL profiler I can see that the SQL server has finished processing the SQL statement, it's just waiting for the front end application (service actually) to retrieve the data rows. By judicious placing of logging statements (cause this problem also doesn't ocurr in the development environment) I've determined that the SQL execute method call is returning and the hang is when the application calls "FetchNext" of the ODBC statement handle. I've tried using the ODBC trace functionality in the testing environment, but this doesn't seem to want to capture the ODBC calls made by Services. I've also traced back and reviewed the changes made to the Testing database around the time the problem surfaced but they are all unrelated. Any other Ideas? Unfortunately I can't easily reboot/reinstall the Testing server as it is a shared environment box. Help? Struan Judd Mailto:[EMAIL PROTECTED] Developer Phone: +64 (9) 368 9368 eCargo Fax: +64 (9) 368 9369 Visibility - Communication - Measurement Mobile: +64 (21) 685 335 Private & Confidential http://www.ecargo.co.nz _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
