Project Post-Mortem

Every project that was worth doing should have a post-project debrief. What went wrong? What could have been done better? While the ideas are still fresh, you have to ask yourself what things should go into the next version.

The application probably could have made all changes be automatically saved (to the customer record, frm_main) and the cmd_save_edits button could have been removed altogether. The times when edits won’t be saved will be very rare. So such a change probably wouldn’t impact usefulness and would save more keystrokes than it created. Instead, simply run the update database procedure every time frm_main is moved off the current record.

Regarding the changes made to frm_items_ordered, simple is best. If a ...

Get MySQL Building User Interfaces now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.