Problem with cursor

[Michael Bierly]

Thanks Ruslan!  I added the options kV_Client, kV_NoLocks, kV_ReadOnly 
to the first cursor and everything worked exactly as expected.

On Sep 26, 2004, at 3:23 AM, Ruslan Zasukhin wrote:

> Hi Michael,
>
> I think all is simple
>
> Your first cursor is READ ONLY.
> Your second cursor want to be READ WRITE.
>     I assume it try lock THE SAME record.
>
> You do not have error check.
> You should have it after EACH query.
> Then you will know what is wrong.
> I think after second you get 363 error.
>
> You MUST kill the first cursor before you start second query.
> Or you must specify for the first cursor NO LOCK parameter
>
>
> -- 
> Best regards,
> Ruslan Zasukhin      [ I feel the need...the need for speed ]
> -------------------------------------------------------------
> e-mail: ruslan at paradigmasoft.com
> web: http://www.paradigmasoft.com
>
> To subscribe to the Valentina mail list go to:
> http://lists.macserve.net/mailman/listinfo/valentina
> -------------------------------------------------------------
>
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina
>