[AccessD] Unbound Again

Martin,

One problem with unbound is the whole locking issue, which the bound method
handles for you.  Unless you place a lock on the record you are editing,
then how do you know that the underlying record wasn't updated by another
user while this user was eating lunch?  Thus for simple unbound, probably
only updating fields changed is the safest.  If your form is going to lock
the record being edited, then you can safely update the entire record.  Or
you could refetch the original, compare the field values of the original to
the "old values" of the unbound form, and warn the user if there were
changes to the original.  Many different answers to that seemingly simple
question.


John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Martin Reid
Sent: Friday, December 22, 2006 8:10 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Unbound Again

Back to the unbound edit
 
So the idea I am using is to
 
1. Click The Edit Button
2. Unlock fields
2. Change edit caption to save
 
So the suer changes one field. Do you just simply update the whole record ot
do you test each field and only chane the one edited? Or is there any issue
with either?
 
Martin
 
Martin WP Reid
Training and Assessment Unit
Riddle Hall
Belfast
 
tel: 02890 974477