[AccessD] RE: [accessed] A2K What's the Opposite F11?

An alternative to disabling all Access Special Keys is to add an AutoKeys
macro group to the database. The macro named {F11} would have a condition
that checks the current user's LAN ID (a simple function call to an API) and
if it is that of the anointed one the ShowDbWindow code is run, otherwise
nothing happens. This macro effectively disables F11 for all but the chosen.

And here's the code to execute...

Function ShowDbWindow(Optional bMakeVisible As Boolean = True)
    DoCmd.SelectObject acForm, , True
    If Not bMakeVisible = True Then DoCmd.RunCommand acCmdWindowHide
End Function

Lambert

> -----Original Message-----
> From:	Susan Harkins [SMTP:ssharkins at bellsouth.net]
> Sent:	Thursday, December 18, 2003 10: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