Hi,

        I developed a multiuser database application (front end VB5 with a Access
backend <jet engine>, oh! - the database is of a dynaset type) At this
point all my users can access all records an edit them simultaneously.  The
problem that i am trying to solve is that i want to lock a page (or row if
you will) so that while one user is edititing record "x" another user can
only read and not write into record "x" concurrently.  Access 97 seems to
have such features options/advance/records locking)  however the
functionality does not work when calling the database thru VB5, further
more the Access functionality works on locking the whole record (or table
if you will) or a chunck of records(2004k buffer).  The functionality that
I am seeking is for a whole row only of a selected field.

Can you shed some light on the subject

gracias,
Rafael

VB Tech Journal, October Edition has an article on third party database
engines.  Some offer you record locking (Oterro, http://www.oterro.com) and
some don't.  I hope this article helps.

Access 97 seems to

JET doesn't utilize record locking.  You are stuck with 2k page locks,
which could affect records that other users are trying to edit, view, etc.
I would suggest creating a dynaset type recordset with the dbSeeChanges
option.  The VB5 help has more explanation on this option under the
OpenRecordSet method.  Make sure you read the information at the bottom of
the help page for suggestions on how to use this option effectively.

Later,
Tony Fountain

The Oterro database engine has what you are asking for $299.  Their website
is http://www.oterro.com

Rafael,

  Getting Access to work like this is difficult because it locks records
on
a page level not record level. If you change to another database engine
there
may be some reprogramming necessary to use the other engine, and, does
it
have the functionality to flag the user when a record is locked ? How
about
this :

  1. The user identifies what record he wants to edit so you change the
     value of an 'EditUser' field from null to the log on name of the
     user.

  2. If another user goes to the same record the EditUser field has a
value
     so the second user gets a message stating the record is read only
because
     user 'xxxx' has the record. You should let the user that wants the
record
     know who has the record just in case the first guy goes away from
his desk
     and they have to find him.

  3. When the first user commits his transaction you set the field back
to null.

  4. When users log in you would have to update the EditUser field to
null
     where the EditUser field equals the person's log on name. (Just in
case
     there was a power failure or the person's machine crashed before he
was
     done).

The only downfall is if a user's machine crashed and he never logs back
in, the
front end will not let anyone edit that particular record until the
first guy
logs back in; other than that it should be fairly easy to implement.

Hope this helps,
Anthony