A clunky workaround could be to add a meaningless extra read-only field and separately have code plop a "1" or "True" or "Place_Holder" in the field (because gINT Rules can write to a read-only field). It would have to be separate from the reading list because doesn't count toward empty vs used.
If data is only going in from that Access db, you could add a field with "1" in it whether or not there's a reading for that sieve.
I hope there's a better way I haven't heard of.
YUP - A placeholder for any of the readings that do not have a Soil Tare created by my source originating application is what I impress into my source data file. For grins, the value placeholder is "8675309", as shown below. The gINT tech, then adds the supplemental data on other sieves not in the source to overwrite those placeholder values as needed and deletes the remainder. placeholder rows.Clunky a bit but a start at least. More code can be made to remove the 8657309's.
...Don't lose that number
I just KNEW that someone would get it!
Ha ha, but I muffed the lyric, it should have been "Don't change your number", I had it mixed up with Rikki Don't Lose That Number