forms and tables

[jeffobullo]

As I enter information into a form, shouldn't this information appear in the
related table? I have instances where this is not happening. Can someone
please explain.

When I enter information directly in the table, the info does show up in the
form.

 

[Jerry Whittle]

Do you get any error messages when entering the data through the form?

Is the record source for the form a table or a query? If a query, are more
than one table involved.

Are there any messages in the lower left of the window when typing in data
into the form?

 

[jeffobullo]

Thanks Jerry.
Not getting any error messages when entering data through the form. The
record source for the form is a table.

I want to use the form as the the main data entry point. The report I've
written is pulling from the table, but since some of the data entered in the
form doesn't make it back to the table, the report has missing data in it.

 

[John W. Vinson]

Thanks Jerry.
Not getting any error messages when entering data through the form. The
record source for the form is a table.

I want to use the form as the the main data entry point. The report I've
written is pulling from the table, but since some of the data entered in the
form doesn't make it back to the table, the report has missing data in it.

One common way this can happen is having the data on the form, but not yet
committed to the table before the Report is opened. Are you opening the report
from the form, or while the form is still open? If you close the form, or
intentionally save the record using shift-Enter, does the problem go away? If
you're opening the report using a command button or other form event, you can
put a line

DoCmd.RunCommand acCmdSaveRecord

before the line opening the report to save the record.

 

[Armen Stein]

One common way this can happen is having the data on the form, but not yet
committed to the table before the Report is opened. Are you opening the report
from the form, or while the form is still open? If you close the form, or
intentionally save the record using shift-Enter, does the problem go away? If
you're opening the report using a command button or other form event, you can
put a line

DoCmd.RunCommand acCmdSaveRecord

before the line opening the report to save the record.

When you enter data into the form, then close it and reopen it again,
are those fields blank again? If so, it's possible that those fields
are not actually bound to your underlying table.

Check the property sheet on those fields, and make sure the Control
Source property is a name of a field in your table. If the Control
Source is blank, that means your field is "unbound" and that would
cause your problem.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[jeffobullo]

Thanks but that didn't do the trick. One thing I have noticed with the data
entered in the form that doesn't pull to the table is that these fields are
automatically populated. For instance, when I enter the employee number in
the form, the first and last name automatically populate in the form, but
does not make it the corresponding table.

Could this be part of the issue?

 

[John W. Vinson]

Thanks but that didn't do the trick. One thing I have noticed with the data
entered in the form that doesn't pull to the table is that these fields are
automatically populated. For instance, when I enter the employee number in
the form, the first and last name automatically populate in the form, but
does not make it the corresponding table.

What are the Control Source properties of the textboxes containing the names?
What is the Recordsource property of the form? I suspect that the form's
recordsource table does not (and should not!!) contain fields for the
employee's name; those fields should exist only in the employee table, NOT in
any other table.