Quote Originally Posted by Christhemist View Post
I've decided to present them with one set of controls for them to page through all records, however they are going to want an autosave every time a change is made. Am I beating myself over the head with how many database writes this is going to end up with?
Show your approach and present the advantages - workflow with simplified data view and navigation. No one will read and modify 200+ fields, so it is better to keep single record info on single "page". If users need some info from previous/next page, then show only that info, e.g. previous and next item numbers and descriptions near by the buttons to move to prev/next record.

For the db saves techgnome wrote you how to do it.