Thank you so much for your reply. Your explanation is how I had my table setup prior to moving to the reverse relationship solution. Some issues that I had at the time were that the Added Read (Record) would become the new maximum when saved...resulting in run time = 0. I had to use snapshot fields to preserve the read. It got confusing because the calculation would work prior to saving. The operator could see the run time. When the record was saved the calculation would change (because of the new Max). I had to create conditions to alter the view depending on if it was a new record, edit, view. This is when I changed to the reserve relationship solution. I also had issues with how the mobile app would process the New Record routine compared to the Desktop Version. This was many years ago.
The operators are using the mobile app and many of our locations are in areas with poor/no connectivity. I am going to collect the reads with an app that can be used to collect the data. I will need to import the reads into the reads table. The problem is that I won't know the reverse relationship Record ID of the previous read.
I can export a list from the equipment table. It will have the [Equipment ID] and Summary Fields [Last Read][Date of Last Read]. The operator can input the current read. I can then Import the data into the Read Table. I will have the equipment ID#, Read Date, Read Value. I won't have the Record ID# to populate the [Related Read Field] (Reverse Relationship)
If I could use logic to know what the Record ID# would be maybe there is a solution?
Thank you again.
