[AccessD] VBA Unbound data entry / update form

Max,

 > Won't work John.

 >>Make the changes.  When done, look up the original record 
in the real table, compare data fields from temp to real. 
If there are any changes THEN make the appropriate decisions 
etc.  This still requires a fair amount of logic to 
determine "old values" and the like...

Lock fields, lock notices, timeouts etc are a "fair amount 
of logic" as well.

 > 2. Lock it as soon as record is accessed/edited.

I can't do this.  The lock affects other entirely unrelated 
records due to memo and index "page locks".  THAT IS WHAT I 
AM TRYING TO WORK AROUND!

John W. Colby
www.ColbyConsulting.com


Max Wanadoo wrote:
> Won't work John.
> If you have User 1 making changes, you need to ensure that User 2 is not
> making simultaneous changes to the same data albeit via a temp table.
> Until you do that, nothing else makes any sense.
> I would:
> 1. Put a field on the table "I am locked By UserName".
> 2. Lock it as soon as record is accessed/edited.
> 3. Warn other users that records is being edited by UserName if they try to
> access it.  Ask them do they want to be notified when record becomes
> available.  If so, record PK and User in a temp table or in variable array
> and check it via an OnTimer event.
> 4. You can also put a Time-Out default if UserName left a record Locked when
> he/she went off to luch.  Time-out and lock/leave the record thus unlockign
> it for others.
> 5. KIS works for me.
> Max
> Ps. Also be aware of what you need to do if the record is locked by being
> reported on via a Report/update batch run, etc.  Remember record will be
> incomplete.