Database Object.
You can use the AllowSpecialKeys property to specify whether or not special key sequences (ALT+F1 (F11), CTRL+F11, CTRL+BREAK, and CTRL+G) are disabled or enabled. For example, you can use the AllowSpecialKeys property to prevent a user from displaying the Database window using F11, entering break mode within a Visual Basic module using CTRL+BREAK, or displaying the Debug window using CTRL+G.
The AllowSpecialKeys property uses the following settings.
| Setting | Description |
| True (-1) | Enable the special key sequences. |
| False (0) | Disable the special key sequences. |
You can set this property by using a macro or Visual Basic. You can also set this property by selecting Use Access Special Keys in the Advanced section of the Startup dialog box, available by clicking Startup on the Tools menu. This is the easiest way to set this property.
You should enable the AllowSpecialKeys property when debugging your database.
The AllowSpecialKeys property affects the following key sequences.
| Key sequences | Effect |
| ALT+F1 (F11) | Bring the Database window to the front. |
| CTRL+G | Display the Debug window. |
| Key sequences | Effect |
| CTRL+F11 | Toggle between the custom menu bar and the built-in menu bar. |
| CTRL+BREAK | Enter break mode. |
This property’s setting does not take effect until the next time the application database opens
AllowBreakIntoCode Property, AllowBypassKey Property.
See the AllowBreakIntoCode property example.