Hi,

I want to write lock a group of records in a table whilst I perform some
processing on those records.  How can I do this?  As I understand a
transaction will lock the whole table from writing, so that doesnt suit the
requirement.

V3.30

Thanks

Alex

Al

I think the only way to do that is creating a special field and control it
inside the application. If the content of field is '*' then it is locked
otherwise not.

Eduardo

Alex,

<< I want to write lock a group of records in a table whilst I perform some
processing on those records.  How can I do this?  As I understand a
transaction will lock the whole table from writing, so that doesnt suit the
requirement. >>

DBISAM doesn't allow this.  However, ElevateDB will most likely allow for
multiple row locks per table cursor.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hmm, seems rather limiting then.  I have taken in Jose suggestion of
creating a lockedflag field, however, I am a little wary of this type of
solution in a multi-user environment, especially if a PC were to crash
without the chance of clearing those flags.

What about opening up an instance of a table for every record i want to lock
and locking a record by editing?  The number of records this should affect
at any one time should not be more than 100.  What sort of memory or
resource implications would this potentially have.

Or any other potential solutions to consider?

Thanks

Alex

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:324ACFCD-4752-4FCF-8BCE-6806871B2044@news.elevatesoft.com...
> Alex,
>
> << I want to write lock a group of records in a table whilst I perform
> some processing on those records.  How can I do this?  As I understand a
> transaction will lock the whole table from writing, so that doesnt suit
> the requirement. >>
>
> DBISAM doesn't allow this.  However, ElevateDB will most likely allow for
> multiple row locks per table cursor.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Alex,

<< What about opening up an instance of a table for every record i want to
lock and locking a record by editing?  The number of records this should
affect at any one time should not be more than 100.  What sort of memory or
resource implications would this potentially have. >>

You'd be consuming a bit of memory, but nothing outrageous.  Table cursors,
which is what the TDBISAMTable represents, are fairly lightweight in the
memory department.

--
Tim Young
Elevate Software
www.elevatesoft.com