Thanks. Unless I misunderstood though, locking the controls prevents the
user from creating new records, doesn't it?
> Yes, that is how Access works.
>
[quoted text clipped - 23 lines]
> >
> > Thanks!!!
The article contains the code for locking and unlocking the form.
If you call the code in the form's Current event, you can use it to lock
existing records, and unlock new records:
Private Sub Form_Current()
Call LockBoundControls(Me, Not Me.NewRecord)
End Sub

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
> Thanks. Unless I misunderstood though, locking the controls prevents the
> user from creating new records, doesn't it?
[quoted text clipped - 28 lines]
>> > not on either subform. Am I stuck with this, or am I doing something
>> > wrong?
AccessMan - 13 Mar 2008 17:10 GMT
I think I see what you are saying now. Would a lot of modification be
required to automatically lock bound controls (or the entire form/subforms)
for existing records, and automatically unlock for new records?
> The article contains the code for locking and unlocking the form.
>
[quoted text clipped - 37 lines]
> >> > not on either subform. Am I stuck with this, or am I doing something
> >> > wrong?
Allen Browne - 13 Mar 2008 17:16 GMT
Probably no changes at all.
Copy'n'paste the code.
Use the form's Current event instead of the Load event /button click as
suggested in the article.

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
>I think I see what you are saying now. Would a lot of modification be
> required to automatically lock bound controls (or the entire
[quoted text clipped - 50 lines]
>> >> > something
>> >> > wrong?
AccessMan - 13 Mar 2008 17:36 GMT
I'm slowly building my comfort level with VBA. Would a more direct solution
be to set Allow Edits to No for the form and subforms by default, and reset
this property to Yes for all if the user clicks any of the New Record
buttons? I would also need to reset the properties back to No after the new
record is saved.
> Probably no changes at all.
>
[quoted text clipped - 57 lines]
> >> >> > something
> >> >> > wrong?
Allen Browne - 14 Mar 2008 03:03 GMT
You can try that.
My experience is that AllowEdits is way to restrictive in practice. For
example, if you use an unbound combo for navigating to a record, or unbound
controls so the user can filter the form, there are all useless if
AllowEdits is set to Yes.

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
> I'm slowly building my comfort level with VBA. Would a more direct
> solution
[quoted text clipped - 4 lines]
> new
> record is saved.