I have created the first half of a SqlServer database interaction project.
(I had already established the database structure and copied existing records into the tables.)
The "first half" was to allow the user to display an existing record and allow edit/save changes.
The "second half" is to allow the user to add a new record.
My thought is to use the same windows as in the "first half", hiding the buttons associated with editing existing records(if necessary) and showing buttons for creating a new record...but if I can simply use a button to allocate a new record(as empty), then use the same "edit/save existing record" buttons to fill in the field values for the new record, that could avoid duplication in my coding efforts.
Would it be considered "bad technique" to not have the two capabilities totally separate in my project?
(I have considerable experience with locally-hosted relational databases, but it was only recently that my employer began a relationship with a web-based host server provider for this database.)