D
Don
The database I am working on has an employee information form on which there
is a subform which lists education. The subform is linked using the
employee ID and used tblEducation as its source. In this configuration, the
subform would always show a blank record in which the user could enter new
education data.
Now, I added a Me.RecordSource which uses and SQL string. When I tested the
form, I noticed the blank record was gone. It then dawned on me that the
subform was no longer directly linked to the underlying table
(tblEducation). Before I go off to solve this issue, I would like to get
confirmation of a couple things:
1) Is it safe to assume that the blank/new record will not be in a subform
if the subform is not directly linked to it's underlying table?
2) Edits made in the subform will not be reflected in the underlying table
as the record source for the subform is actaully an SQL query?
Now for the design question ........
If I want to continue to use the SQL string (there are some sorting and
table linking going on), is the best design path for adding and editing
records to have pop-up forms with fields to fill in or edit respectively?
It seems like the only option to me, but I figured some of you advanced
Access users might have some comments and ideas.
Thanks!
Don
is a subform which lists education. The subform is linked using the
employee ID and used tblEducation as its source. In this configuration, the
subform would always show a blank record in which the user could enter new
education data.
Now, I added a Me.RecordSource which uses and SQL string. When I tested the
form, I noticed the blank record was gone. It then dawned on me that the
subform was no longer directly linked to the underlying table
(tblEducation). Before I go off to solve this issue, I would like to get
confirmation of a couple things:
1) Is it safe to assume that the blank/new record will not be in a subform
if the subform is not directly linked to it's underlying table?
2) Edits made in the subform will not be reflected in the underlying table
as the record source for the subform is actaully an SQL query?
Now for the design question ........
If I want to continue to use the SQL string (there are some sorting and
table linking going on), is the best design path for adding and editing
records to have pop-up forms with fields to fill in or edit respectively?
It seems like the only option to me, but I figured some of you advanced
Access users might have some comments and ideas.
Thanks!
Don