Record lock, err 363

[James Milne]

On 11 Mar 2004, at 13:51, James Milne wrote:

> Hi all,
>
> I'm using Valentina 1.10 with REALbasic 5.2.4 and I'm having a strange 
> problem
> with record locking.
>
> In my application, I mainly use SQL select strings to perform queries, 
> and I'm using
> 'empty cursors' to insert data.
>
> After having inserted a few items into my table I'm getting a problem 
> with the
> table becoming locked such that I can no longer create a writeable 
> cursor on it.
> I'm just using Valentina within my application- no server stuff going 
> on here.
> Using DebugDumpObjects in REALbasic to show me what objects are alive
> shows that there are no VCursors alive when my call to SqlSelect fails.
>
> What other ways are there that a table might become locked? I am using 
> SQL
> update statements in some places. Is there anything I need to do after 
> an
> Update to ensure that the rows are unlocked?

Actually, I've figured it out.

Somehow, I'd omitted adding "where RecID = 0" onto the end of my select
statement to get an empty cursor. Adding that has fixed the problem.

Doh!

--
James Milne