Vlad,

maybe I'm missing something here ... is it possible to open a remote view, disconnect the connection the view is using and later re-connect and make updates from the view's cursor that's still open over the new connection?

>As about this particular problem, its strange that sqldisconn(0) in anotehr app causes crash in first app.

I wouldn't think that this is really the cause for the problem. But one never knows. IMO it's more likely that there's something else wrong.

Regards,
Armin

>
>That's not true. You can get exact connection string from cursor properties, remember it, and then re-connect to server later (after disconecting) by using SQLStringConnect().
>
>As about this particular problem, its strange that sqldisconn(0) in anotehr app causes crash in first app.
>
>Fbilo, can you give more details about sequense of events happening? Like connect, disconnect, connect with what handle etc.
>
>>Hi,
>>
>>>Yeah, i do have an sqldisconn(0) state in another application. Mybe its because of i test that two app together. Thanks, but how can i get away from this state? I try to rebuild a connection, it did'nt work.:(
>>
>>unfortunately you can't reconnect to the database. You'll have to avoid disconnecting from the database before your cursors/views are closed.
>>
>>HTH,
>>Armin