Do you see how ProdID is always the FK in all the tables directly descended from your production activity?
This is corrected now.
------------------------------------------------------------------
If you look at your SQL string in Design view, you will notice that tblAsphalt2 has a relationship to AsphaltFK1. I don't think this is what you want.
This is corrected now and tblAsphalt2 is updating automatically.
-------------------------------------------------------------------
1. Don't use the actual SQL string as the Record Source for Form. There are no problems with doing this, but it is much easier to create a Query, save it and use the query itself as a Record Source.
I have not switched the record source yet, before doing so I'm curious if my data will still be saved in the tables as well.
--------------------------------------------------------------------
As I mentioned to you earlier, a Tab Control is a good design for this: You've done that. BUT, each Page on that tabl control should have sub-form specific to each particular aspect of the production. One subform will be about Lime, one about Aggregate, etc.
I will do work on this tomorrow, very simple layout I use so should not take long. But this brings me back to you saying use query as a record source, so every subform will use a individual qry or can I use my qry that has every table/every field for each subform?
--------------------------------------------------------------------
Just curious here, not requesting details for now. I never could recreate your aggregate subform. Did you use a query for its source to filter it to the forms date?
Thanks, This is a big learning curve. I'm semi getting it I do believe but without tech knowledge/terminology its sometimes difficult to get what I'm asking across in a way it makes sense.
This is corrected now.
------------------------------------------------------------------
If you look at your SQL string in Design view, you will notice that tblAsphalt2 has a relationship to AsphaltFK1. I don't think this is what you want.
This is corrected now and tblAsphalt2 is updating automatically.
-------------------------------------------------------------------
1. Don't use the actual SQL string as the Record Source for Form. There are no problems with doing this, but it is much easier to create a Query, save it and use the query itself as a Record Source.
I have not switched the record source yet, before doing so I'm curious if my data will still be saved in the tables as well.
--------------------------------------------------------------------
As I mentioned to you earlier, a Tab Control is a good design for this: You've done that. BUT, each Page on that tabl control should have sub-form specific to each particular aspect of the production. One subform will be about Lime, one about Aggregate, etc.
I will do work on this tomorrow, very simple layout I use so should not take long. But this brings me back to you saying use query as a record source, so every subform will use a individual qry or can I use my qry that has every table/every field for each subform?
--------------------------------------------------------------------
Just curious here, not requesting details for now. I never could recreate your aggregate subform. Did you use a query for its source to filter it to the forms date?
Thanks, This is a big learning curve. I'm semi getting it I do believe but without tech knowledge/terminology its sometimes difficult to get what I'm asking across in a way it makes sense.
Comment