N
Neil
Hello All,
Got a front end/back end database which is going to be used over a LAN. I
have tested the database on 2 machines and have a couple of questions on how
Access handles this situation.
1) When the recordset type is set to Dynaset, am I right in thinking that
changes made to existing records in the database are updated to each user
(this was happening, put it was acting strange with locked records but i'm
sure i'll figure that out)?
2) If new records are added, is it up to the programmer to requery the form
or are new records shown automatically (seems to be that a requery is
needed)?
3) Is there any aids that Access provides when coding - for e.g. when a
record is locked, the forms On Dirty event still fires. Is there a way to
check to see if the record is locked and then cancel the Dirty event.
4) When a record is locked, no error seems to be happening. Can you display
a message to the user somehow instead of just getting a beep. As many of our
users do not have sound, they will automatically assume that Access is
misbehaving rather than protecting a record?
Any thoughts, pointers etc is greatly appreciated!
TIA,
Neil.
Got a front end/back end database which is going to be used over a LAN. I
have tested the database on 2 machines and have a couple of questions on how
Access handles this situation.
1) When the recordset type is set to Dynaset, am I right in thinking that
changes made to existing records in the database are updated to each user
(this was happening, put it was acting strange with locked records but i'm
sure i'll figure that out)?
2) If new records are added, is it up to the programmer to requery the form
or are new records shown automatically (seems to be that a requery is
needed)?
3) Is there any aids that Access provides when coding - for e.g. when a
record is locked, the forms On Dirty event still fires. Is there a way to
check to see if the record is locked and then cancel the Dirty event.
4) When a record is locked, no error seems to be happening. Can you display
a message to the user somehow instead of just getting a beep. As many of our
users do not have sound, they will automatically assume that Access is
misbehaving rather than protecting a record?
Any thoughts, pointers etc is greatly appreciated!
TIA,
Neil.