To locate source of data in a form

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I have a form where there are few blank fileds (shown in design view). However, this form is being used as a data entry screen. I have no way to know which table the data is going to by checking the form properties. The form does not show any event procedure is active.

I am looking for idea how to resolve this problem.
One thing to note is the fact that the form has a combo box which represent a list of cases and one can choose one of the cases and then correspondingly fill in the blank fields in the form to make the data entry.
Thanks in advance
 
John said:
Hi,
I have a form where there are few blank fileds (shown in design
view). However, this form is being used as a data entry screen. I
have no way to know which table the data is going to by checking the
form properties. The form does not show any event procedure is
active.

I am looking for idea how to resolve this problem.
One thing to note is the fact that the form has a combo box which
represent a list of cases and one can choose one of the cases and
then correspondingly fill in the blank fields in the form to make the
data entry.
Thanks in advance

I'm not sure I follow you, John. The form's RecordSource property will
always tell you what table or query its data is being stored in, unless
data is being written by code behind the form, rather than by the
built-in Access data-binding. If the form's RecordSource property is
blank when you open the form in design view, and yet the form actually
does update tables, there are only two possibilities: (1) code or a
macro that executes at run time sets the form's RecordSource property so
that normal data-binding can occur, or (2) code or a macro that executes
at run time updates tables directly with values taken from unbound
controls on the form.

If the RecordSource is blank, cCheck the form's HasModule property to to
see if the form has a code module. If so, then click the "Code" toolbar
button to view that module and see what procedures are in it. If the
form has no code module, then check for macros in various event
properties for the form and its controls. If there are none, then maybe
the form is opened by some external procedure or macro that also sets
its RecordSource property.

What you say about the combo box makes it sound like there may be code
for one of that combo box's events, and that code may be relevant.
 
Back
Top