[AccessD] A2K What's the Opposite F11?

Susan,

I do inhibit the db window - but not for administrators.

The way I do this is to change the "AllowSpecialKeys" property in code to
False prior to the db being in production use.  The administrator (not
users) can get to a screen and push a button to reset those db properties to
True.  Then the administrator needs to exit out of the db and reopen - and
then the administrator is unrestricted.

The button to open this administrators screen is not visible to users, but
is visible to administrators.  

Hmm . . .  Do you need an article on this?

Dan Waters
Quality Process Solutions, Inc.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Thursday, December 18, 2003 9:17 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A2K What's the Opposite F11?



> Hello all
> When the dB window is hidden - pressing F11 will make it visible What 
> do I do to make it IN-visible once it is visible?

============If you need to permanently inhibit the F11 key too, you must
deselect both of the following startup options: Display Database Window and
Use Access Special Keys. Word of caution -- you don't want to do this until
you're really done with the project. I'd be interested to know how many
applications permanently inhibit the db window -- just curious.

Otherwise, I don't understand what you mean by making it invisible.

Susan H.



_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com