I created a form which has locks so that I can't edit any textbox. The lock property is "No" and the allow edit property is "No". A second form has similar properties, yet I'm able to edit the textboxes. What property do I need to change to prevent any changes to the textboxes or the record ?
Form Locks
- Thread starter DBFIN
- Start date
missinglinq
AWF VIP
- Local time
- Yesterday, 22:06
- Joined
- Jun 20, 2003
- Messages
- 6,417
The Form's Locked Property has to do with whether a Record is Locked to UserB if UserA is working with the Record. You would need to Lock each Control to prevent anyone from editing the Record. Or setting AllowEdits to No should do, as well.
Exactly how are you opening the errant Form, when it allows you to edit Records? Opening a Form from another Form, through code, can sometimes override the secondary Form's Properties.
Linq ;0)>
Exactly how are you opening the errant Form, when it allows you to edit Records? Opening a Form from another Form, through code, can sometimes override the secondary Form's Properties.
Linq ;0)>
Last edited:
After further testing, I think I discovered the problem, but still would like to hear your thoughts. The form with the problem was a copy of another form. Even though the allow edit property was "No", this property seemed to be de-activated, possibly when I created the form from another form. I simply went to the allow edit property and selected "No" again even though the property was already "No". This activated the property and it works now.
What concerns me is how could allow edit property of "No" allow edits ? Is it because of the copying from another form or another reason ?
What concerns me is how could allow edit property of "No" allow edits ? Is it because of the copying from another form or another reason ?
missinglinq
AWF VIP
- Local time
- Yesterday, 22:06
- Joined
- Jun 20, 2003
- Messages
- 6,417
No idea, really. I cannot reproduce the problem. Probably just the Access Gnomes having some fun!
Glad you got it working.
Linq ;0)>
Glad you got it working.
Linq ;0)>
missinglinq
AWF VIP
- Local time
- Yesterday, 22:06
- Joined
- Jun 20, 2003
- Messages
- 6,417
Only thing I can suggest is that you remove sensitive data, if any, ZIP the file up and attach it so someone here can look at it. If you can save the file in 2003 or 2007 format (2003 would be best) more of us will be able to look at it.
Also give the name of the errant Form.
Linq ;0)>
Also give the name of the errant Form.
Linq ;0)>
