If the user needs to step through each of the records then I'd recommend treating this like a wizard wherein you have a next button at the bottom of the page in place of the save button. I would make that button larger or a different color than the other buttons to make it clear that that is the main action. With this change, you are asking the user to enter a code, enter a description and click next. In your example, where there are six records, the user can repeat this progression six times. When she reaches the final record, change the button label to Finish. If the records are optional, then include an extra button to finish and close out. A workflow that starts at the top right and moves down the page and ends bottom right is the usual flow for a page, at least in Western countries. The flow of the original screen is awkward because the user is expected to enter a code, move down to the description and then move back up to the next / prev buttons and then after entering all six, go all the way to the bottom to click the save button. This down, up, down, up, down all the way cycle is hard to figure out. The second screen shares this maze of a flow so whether regardless if a slider is a better control than arrow buttons, the workflow remains unnatural.
A source of problem here is in trying to stick six records into a form that would work much easier if there were one record. I assume the user is coming from a table etc. and you could greatly simply the form by only handling one record at a time.
Another issue is the Delete button who's purpose is unclear and seems kind of scary - like I'm deleting everything. If this button is meant to delete one of the records, then consider relabeling it.
The term records is database jargon. If you could come up with a more humanistic label then I think the users might have an easier time understanding the purpose of the form.