Results 1 to 3 of 3
  1. #1
    Join Date
    Oct 2004
    Location
    Melbourne, Australia
    Posts
    201

    Unanswered: StartUpSHowDBWIndow problem

    Another litttle problem to allow All of you Colleagues to show how much better at Access than I am.

    I have a client whose Access database contains an autoexec() function holding the following code snippet.

    'owner can bypass startup code
    If CurrentUser = "owner" Then
    If Not UserYesNo("Do you want to run startup code?") Then
    Set StartUpSHowDBWIndow = CurrentDb.CreateProperty(, , -1)
    Exit Function
    End If
    End If
    Set StartUpSHowDBWIndow = CurrentDb.CreateProperty(, , 0)
    . . . other settings

    The intention (apart from the usual one of preventing unprivleged users from mucking about with the database innards) is to create a nice background for a switchboard which is smaller than the screen size. This worked perfectly in Access 97, but after an upgrade to Office 2003, the window does not get hidden, but is merely disabled (i.e. greyed out). The effect is rather ugly and the client would like to see his system as he remembers it. Is there any other way I can code this process to give him what he wants.

  2. #2
    Join Date
    Mar 2009
    Posts
    5,442
    Provided Answers: 14
    This is a normal behaviour in Access 2003. To hide the Access Database window use:
    Code:
    RunCommand acCmdWindowHide
    You can also disable the F11 key to prevent someone calling it back.

    Have a nice day!

  3. #3
    Join Date
    Oct 2004
    Location
    Melbourne, Australia
    Posts
    201
    Thanks for your prompt advice, Sinndho. It worked perfectly. Curiously, though, if you invoke Access Help, the list of constants does not include this one.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •