Error 363

[Ruslan Zasukhin]

on 12/23/03 9:34 PM, Bill Mounce at bill at teknia.com wrote:

> Ruslan,
> 
> Yes, everything worked prior to 1.9.8, but I prefer to update my code
> to keep up with your advancements.
> 
> I can see how this new requirement has tripped up many people, even
> though you did specify clearly in the release notes. My problems have
> been more that searches that used to work just don't work any more. My
> question is, is it possible to access a database with a cursor that is
> read-only and also access the same database with a different cursor
> that is readwrite?

I believe answer is in the new docs.

NO, you cannot set WRITE lock on a record that already have READ lock.

But if first cursor READ lock one record.
But second cursor set WRITE lock on OTHER record, then no problems.


> With my current problem, even though I have added in the three newly
> required values for the SQLselect, I still can't find the record. I am
> receiving a nil error. It does, however, work with kv_NoLocks instead
> of kv_ReadWrite.

-- 
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
-------------------------------------------------------------