AllowSpecialKeys Property

Applies To

Database object.

Description

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 by pressing F11, entering break mode within a Visual Basic module by pressing CTRL+BREAK, or displaying the Debug window by pressing CTRL+G.

Setting

The AllowSpecialKeys property uses the following settings.

Setting	Description

True (–1)	Enable the special key sequences.
False (0)	Disable the special key sequences.

The easiest way to set this property is by using the Use Access Special Keys option in the Advanced section of the Startup dialog box, available by clicking Startup on the Tools menu. You can also set this property by using a macro or Visual Basic.

To set the AllowSpecialKeys property by using a macro or Visual Basic, you must first either set the property in the Startup dialog box once or create the property by using the CreateProperty method and append it to the Properties collection of the Database object.

Remarks

You should make sure the AllowSpecialKeys property is set to True when debugging an application.

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.
CTRL+F11	Toggle between the custom menu bar and the built-in menu bar.
CTRL+BREAK	Enter break mode and display the current module in the Module window.

If you set the UseSpecialKeys property to False, and specify a global menu bar by using the StartupMenuBar property or the MenuBar property of the Application object, the built-in menu bar isn't accessible.

This property's setting doesn't take effect until the next time the application database opens.