C
Christopher Glaeser
I want to use assignments like
Forms!frmMyForm!txtData.DefaultValue = runtime_string_expression
to prefill some of the fields of a form so that Me.Dirty remains False and
AutoNum is not assigned until the user actually enters data. However, I
noticed that these DefaultValue assignments are persistent (e.g. the new
values can be viewed in the form design mode). This is not a problem, as I
will always prefill these fields with new values when using this particular
form.
However, what about a multiuser environment? If two users open a new form
record at the same time and the VBA code begins prefilling the fields with
assignments to DefaultValues, are these assignments to unique form objects
with unique DefaultValues, or is there a potential race condition as each
user begins assigning different values to the same form DefaultValue?
If it makes a difference, I am currently using Access 2003 and a single .mdb
file (i.e. has not yet been split into front-end/back-end).
Best,
Christopher
Forms!frmMyForm!txtData.DefaultValue = runtime_string_expression
to prefill some of the fields of a form so that Me.Dirty remains False and
AutoNum is not assigned until the user actually enters data. However, I
noticed that these DefaultValue assignments are persistent (e.g. the new
values can be viewed in the form design mode). This is not a problem, as I
will always prefill these fields with new values when using this particular
form.
However, what about a multiuser environment? If two users open a new form
record at the same time and the VBA code begins prefilling the fields with
assignments to DefaultValues, are these assignments to unique form objects
with unique DefaultValues, or is there a potential race condition as each
user begins assigning different values to the same form DefaultValue?
If it makes a difference, I am currently using Access 2003 and a single .mdb
file (i.e. has not yet been split into front-end/back-end).
Best,
Christopher