Submit button can be set to submit, new, revert as it relates to input form. IF you use NEW...even if say it is a second layer of a form input, where user has inputted some data and now editing the database with additional. Watch that word "new". New creates the issue below. YOU MUST keep it set to submit to avoid.
In creating user input forms and editors, when a user inputs data and clicks submit, it goes to a blank screen...does not refresh with data entered, unless you hit refresh. So this would allow for parties to then enter additional data, perhaps on accident or not. But what it then does is create a whole new row entry in a database, with perhaps just the one cell they entered on that blank screen showing.
This creates a chance of bad data building up, and without anyone knowing if a large database.
So am I missing a step to avoid this happening or is this a huge issue that needs to be fixed in ever using NEW as part of a submit button?