AllowEdits and unbound fields

[James Martin]

I have a number of forms that are going to be used for historical purposes
only and, as such, I don't want users to be able to update any of the
information on the forms. I can think of a few ways around this (like
locking every control, etc.), but the simplest way for me (I thought) was to
set AllowEdits to false. This is because I have a routine common to every
form where I can make one change and AllowEdits will be set to false on all
the forms.

My only problem is that the forms all have an unbound combo box that is used
to find whichever record the user wants to view. As soon as I set AllowEdits
to false this combo box gets locked too, so the find function is no longer
useable.

I expect this is a vain hope, but is there some way to exempt an unbound
control from AllowEdits = False?

Barring that, what would be the preferred method of making a form view-only?
Should I just lock all the necessary controls?

Thanks in advance.

James

 

[Van T. Dinh]

You may like to try to set the Recordset Type of the Form to "Snapshot"
which won't allow the user to edit data in bound Controls but will allow you
to change the value in the unbound ComboBox.