V4RB 1.1 RB 5.5 errors handle in multi-user apps

[olivier vidal]

Hi Ruslan and list,

In local network and application multi-users.
For cursors:
Except to test the error KcannotSetLock ( 363 ), there are the other 
types of errors which would require a test in a loop to be certain that 
the cursor is created?
( E.g. if the network is not idle, which error returned?)

Would not you should make it for all returned errors? (Re-try to create 
cursor during e.g. 3/4 seconds)

Except for for the creation of cursors, in what cases does it better 
need to re-try the operation several times in a loop?
cursor navigation methods ? cursor records methods ? all ?

thank you

olivier

Le 14 juin 04, à 12:52, Ruslan Zasukhin a écrit :

>> In Valentina 1.x,
>> in multi-user application, To be certain that the cursor is create, it
>> is always necessary to test it in a loop and to try to create it as
>> long as the error " KCannotSetLock " returned ?
>> It is the solution?
>
> Yes.
>
> You can add in loop sleep,
> Also you can add timeout to be parameter of your app,
> And after say 5 seconds inform user -- cannot do operation.