Need help with entering data into subforms on a main form

[Dave 14867]

ridders,

I looked at what you did and it looks OK. It will take me a while to digest everything you mentioned but I will get through it all, and I trust you opinion and will try to get those things addressed.

The query isn't quite what I was looking for yet and maybe I am asking something that can't be done. I will keep working on this and hopefully making more headway. It seems to be actually working now for the most part and I will be inputting more data to see if anything unexpected happens.

Can you assist with the code to high light cells if an unexpected number is entered. I am still haing trouble with the code to pull a number from a field in 1 table to use in another.

Again, thanks so much for your guidance with this.

Dave

 

[isladogs]

The query isn't quite what I was looking for yet and maybe I am asking something that can't be done.

Dave

Which query?
1. qryMembraneID was designed for the form frmMembrane & its subform
2. I had left the query for the frmSearch subform to you ....

However I've now spent another hour on this & done this subform (fsubSearch) for you.
It is based on a query qryEquipmentMaterials which is then filtered according to the 2 combo boxes

NOTE: The field 63LotNum should be number datatype - you made it Date/Time. I've corrected it

Can you assist with the code to high light cells if an unexpected number is entered.

Use conditional formatting to do this.
In the absence of suitable data to show this, here an example setting PaddleNum field to red text with a bright yellow background if the value is >10
I know that's example is not what you want but the principle is identical

However the best way of preventing users making data errors is not to allow the possibility.
Suggest you remove the field QtyMembranes from the PuckPreparation table and just use the Qty field from the Membrane table - you said I think these should be identical so don't duplicate them

I am still having trouble with the code to pull a number from a field in 1 table to use in another.

With well designed tables containing one type of data only and ensuring no duplication of data in different tables, it will become much easier to construct suitable queries

I've uploaded the updated version for you.
Hopefully this has helped you move forward a lot

However, I really can't afford to spend this amount of time on this database again.

I'm also going to send you a private message if you've enabled that feature