Given the typical Dev/Test/Prod development staging methodologies, and the great ease by which changes to database objects (especially "supporting"-type changes like adding indexes to existing tables) can occur in a software development cycle, it would be very beneficial to allow the built-in Access Table, Query, Form, and Report designers to save the "state" of the overall object, and at "Save"-time offer an option to Generate VBA and/or SQL scripts that can help to facilitate the (re-)deployment of the new changes to partnering databases (migrate the changes from Test back to Dev or Prod copies of a database, for example).
Being able to (optionally) designate a database's SDLC Stage via pre-defined database properties and adding some supporting code appropriate to Dev/Test/Prod stages of a database file would be of great help as well.
Adding things like:
Having Access disallow dropping forms/queries/reports/code modules into DEV modes in a database marked as Production-level;
Adding additional prompts "This Database is designated as a TESTing database - Are You Sure?" before entering DEV modes for database objects in designated TEST DBs (and doing so even more emphatically when saving changes - offering the scripting options by default as part of the save operation);
Only designated DEV versions of the database files would have the same level of ease-of-use for editing operations we enjoy by default today.