The serevr crashes when I do setrange. The only different thing about
this table is that it has few computed fields, which use stor procs.
We have upgraded to the latest version of IBO and it still happens.

Regards

Sandeep

Jason Wharton wrote:

>That is the auto-generated name of the database cursor on the server. It
>must be unique for all clients.
>When you say kills the server what do you mean?
>
>Jason Wharton
>CPS - Mesa AZ
>http://www.ibobjects.com
>
>-- We may not have it all together --
>-- But together we have it all --
>
>
>----- Original Message -----
>From: "Sandeep Chandra" <sandeep@...>
>To: <ibobjects@yahoogroups.com>
>Sent: Sunday, September 08, 2002 4:53 PM
>Subject: [IBO] Setrange kills the server
>
>
>
>
>>I'm doing setrange on a table and it kills the server. Following is the
>>monitor log .
>>
>>[ 09/09/2002 11:47:38 ]
>>EXECUTE STATEMENT
>>TR_HANDLE = 36725600
>>STMT_HANDLE = 45212680
>>PARAMS = [ Version 1 SQLd 2 SQLn 2
>> [RBEG_REF_NUMBER] = 10000004920
>> [REND_REF_NUMBER] = 10000004920 ]
>>----*/
>>/*---
>>[ 09/09/2002 11:47:38 ]
>>EXECUTE ROW FETCH
>>TR_HANDLE = 36725600
>>STMT_HANDLE = 38061944
>>PARAMS = [ Version 1 SQLd 1 SQLn 1
>> CLIENT_MAIN.REF_NUMBER[BIND_0] = 10000004920 ]
>>----*/
>>/*---
>>[ 09/09/2002 11:47:38 ]
>>OPEN ROW CURSOR
>>STMT_HANDLE = 38061944
>>NAME = C497160166373347326 ===============> What is
>>
>>
>this?
>
>
>>SECONDS = 0.010
>>----*/
>>
>>Regards
>>
>>Sandeep
>>
>>
>
>
>