If you're saying that while running the database in the runtime environment that you can't make design changes, that's because you're not allowed to make changes in the runtime version! You're only allowed to
run the database! Here's the explanation from Microsoft:
Differences Between the Standard and Runtime Versions of Access
It's important to understand the differences between the standard and runtime versions of Access. The following differences have definite implications for the way you develop any applications you expect to run from the runtime version:
- The Database, Macro, and Module windows aren't available in the runtime environment.
- No Design views are available in the runtime environment.
- No built-in toolbars are available in the runtime environment.
- Many windows, menus, and commands are invisible in the runtime environment. For example, the Window | Hide and Window| Unhide commands are invisible. Although these and other commands aren't visible, their functions are generally accessible by using code.
- You must build error handling into your runtime applications. If you don't, when an error occurs the application displays a standard Access dialog box indicating an irrecoverable error and then exits to the desktop.
- You must build your own custom help files for each runtime application.
- Some keystrokes aren't available in the runtime application.
If you want to make design changes it has to be done under the regular version of Access, not runtime.
Linq
;0)> 
38
