L
Lubek
I've got quite complicated Access 2000 dbase. Somethimes, especially for
continuous forms I try to control the way the user enters the data. Special
concern to avoid accidental changes. Therefore I start all the forms in
read-only by using:
Me.AllowAdditions = False
Me.AllowDeletions = False
Me.AllowEdits = False
and special button to enable changes. It works perfect. However, to save the
data before switching back to read-only I need to use:
DoCmd.RunCommand acCmdSaveRecord
which soethimes ends up with 2501 error. In case I've got at hands now it is
a separate table linked to server. The field are mostly combo-boxes geting
meaning of the data from other tables. But the table itself is simple,
straightforward:
Autonumber, few longs and memo.
ANy idea why does it happen?
continuous forms I try to control the way the user enters the data. Special
concern to avoid accidental changes. Therefore I start all the forms in
read-only by using:
Me.AllowAdditions = False
Me.AllowDeletions = False
Me.AllowEdits = False
and special button to enable changes. It works perfect. However, to save the
data before switching back to read-only I need to use:
DoCmd.RunCommand acCmdSaveRecord
which soethimes ends up with 2501 error. In case I've got at hands now it is
a separate table linked to server. The field are mostly combo-boxes geting
meaning of the data from other tables. But the table itself is simple,
straightforward:
Autonumber, few longs and memo.
ANy idea why does it happen?