H
HotRodSue
My table structure is completed. Now, I’m working on forms and queries. I
have 2 forms with sub forms, frmHarvestDates and frmFields. A dairy farm has
a variety of fields harvested, with varying acre size. The database is
structured such that a harvest is an event for the whole farm and in each
harvest event are multiple fields/plots/crops being harvested.
For the frmHarvestDates I identified which field/plot/crop is being
harvested with a query (qryFieldPlotCropList) to bring all of those pieces of
info together and then used that query as the row source to a combo box bound
to fkFieldPlotCropID.
The same field/plot/crop combination will be planted exactly the same in
more than 1 season. Access will uniquely identify the records, but they will
look the same to the user. So, I chose to filter the field/plot/crop listing
by placing a HarvestEndDate in tblFieldPlotCrop. l modified
qryFieldPlotCropList to limit the list to only those (field/plot/crop
combinations) that have not yet been harvested, HarvestEndDate Is Null.
When I go to frmHarvestDates to enter a new harvest event, my
Field/Plot/Crop Harvested combo box has any field/plot/crop combination with
no EndDate to choose from. However, when I look at the first harvest event
WITH an EndDate, the Field/Plot/Crop Harvested drop combo box is EMPTY as
this harvest event has an EndDate. When I look at the underlying table, the
data is stored as it should be. I was confused about the combo box being
empty, and think it will be confusing for the end user.
How can I better approach this to give the end user a clear data entry form?
have 2 forms with sub forms, frmHarvestDates and frmFields. A dairy farm has
a variety of fields harvested, with varying acre size. The database is
structured such that a harvest is an event for the whole farm and in each
harvest event are multiple fields/plots/crops being harvested.
For the frmHarvestDates I identified which field/plot/crop is being
harvested with a query (qryFieldPlotCropList) to bring all of those pieces of
info together and then used that query as the row source to a combo box bound
to fkFieldPlotCropID.
The same field/plot/crop combination will be planted exactly the same in
more than 1 season. Access will uniquely identify the records, but they will
look the same to the user. So, I chose to filter the field/plot/crop listing
by placing a HarvestEndDate in tblFieldPlotCrop. l modified
qryFieldPlotCropList to limit the list to only those (field/plot/crop
combinations) that have not yet been harvested, HarvestEndDate Is Null.
When I go to frmHarvestDates to enter a new harvest event, my
Field/Plot/Crop Harvested combo box has any field/plot/crop combination with
no EndDate to choose from. However, when I look at the first harvest event
WITH an EndDate, the Field/Plot/Crop Harvested drop combo box is EMPTY as
this harvest event has an EndDate. When I look at the underlying table, the
data is stored as it should be. I was confused about the combo box being
empty, and think it will be confusing for the end user.
How can I better approach this to give the end user a clear data entry form?