So I have a bit of an interesting situation. I created a database to track test requests from engineers. They fill out a form and things work from there. Well to increase the speed of them inputting requests, because some are virtually the same, with the exception of one item, I use a a copy record query. This works fine because after I run that I run an update query that changes the information that needs to be changes. Even this works just as planned.
My issue is that sometimes the user creates one too many requests. So the last copy query isn't needed. What I would like to do is somehow when they leave the form or access is to delete the unnecassary record. It doesn't come up as a new record and since nothing has been changed the form ins't dirty either. That has left me wondering how to check if this record is meant to stay without asking the user.
I certainly have methods at my disposal that I can use along with interations from the user to get the results I want. I am just trying to avoid this if I can. I am just wondering besides checking if its a new record or if its dirty what other options do I have, if any?
My issue is that sometimes the user creates one too many requests. So the last copy query isn't needed. What I would like to do is somehow when they leave the form or access is to delete the unnecassary record. It doesn't come up as a new record and since nothing has been changed the form ins't dirty either. That has left me wondering how to check if this record is meant to stay without asking the user.
I certainly have methods at my disposal that I can use along with interations from the user to get the results I want. I am just trying to avoid this if I can. I am just wondering besides checking if its a new record or if its dirty what other options do I have, if any?