V4RB - Version 1.10 vs 1.11 and Encryption

[Ruslan Zasukhin]

On 10/27/05 1:54 AM, "Russ Tyndall" <fitzbew at nc.rr.com> wrote:

>> I can assume that 1.11 is more strict on record locks, than 1.10
>> 
> 
> Parameters were never changed before or during switching out of plugin.
> 
> Here is line that makes vCursor:
> 
>    rstDB = dbAvx.SqlSelect("Select common_name, sort_id, species_no from
> species where active = 'Y' order by sort_id", kV_Client, kV_ReadOnly,
> kV_Random)

You only read this cursor?
 
> I don't know why fourth parameter is Random, could just be ForwardOnly.
>   Random access is not necessary.

If you do not use PrevRecord, FirstRecord, then you can use ForwardOnly.

But this is just optimization. ForwardOnly cursor unlock record as only you
move to next. Because you have promise never return back.


> Still, that *should* not cause Nil
> vCursor, should it? Even with more strict cursors in 1.11?

It can return nil only in case of some error.
You have check error ?
 
> The app runs at least one other query automatically with the same
> parameters, from a different table.  The first query runs fine.
> 
> Same vCursor property is used in both first and second (Nil) cursor,
> and I am sure it is Nil before second cursor.  So, I do not *think*
> locks are a problem, if I understand you correctly.

Please check error code. If cursor fail to create, then was some error.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]