469,301 Members | 2,272 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,301 developers. It's quick & easy.

Is It possible to set Access Startup Options using VBA?

twinnyfo
3,653 Expert Mod 2GB
I am using MS Access 2007.

I have a database that I do all my editing and programming in and have certain Access options (under the Current Database tab) set one way during the editing. However, when I compile the database into the .accde file, I reopen the database and set certain options, such as the initial display form and navigation pane options. I keep these enabled during programming for ease of use, but disable them whem compiled to prevent others from possibly using them (or at least making it more difficult).

Is it possible to use VBA to set these options to automate this process after the compile? I already have code re-mapping all my linked tables and modifying/deleting unused Switchboard items.

Does anyone have any experience with this?Thanks!
Dec 7 '11 #1

✓ answered by ADezii

I think you are referring to the StartUp Properties of a Database and yes, they can be modified but it is a little tricky since they are User Defined Properties and cannot be Set/Retrieved in the conventional manner. If the Property exists, you can directly modify it, if not you must create it then Append it to the proper Collection. The Code below will set the Allow Full Menus Start Up DB Option to False:
  1. Function Definition:
    Expand|Select|Wrap|Line Numbers
    1. Private Function ChangeProperty(strPropertyName As String, varPropertyType As Variant, varPropertyValue As Variant) As Integer
    2. On Error GoTo Err_ChangeProperty
    3. Dim MyDB As DAO.Database
    4. Dim MyProperty As DAO.Property
    5.  
    6. Set MyDB = CurrentDb()
    7.  
    8. 'Property exists, so set its Value
    9. MyDB.Properties(strPropertyName) = varPropertyValue
    10. ChangeProperty = True
    11.  
    12. Exit_ChangeProperty:
    13.   Exit Function
    14.  
    15. Err_ChangeProperty:
    16.   If Err.Number = 3270 Then       'Property not found
    17.     'Since the Property isn't found, create it!
    18.     Set MyProperty = MyDB.CreateProperty(strPropertyName, varPropertyType, varPropertyValue)
    19.     MyDB.Properties.Append MyProperty
    20.       Resume Next
    21.   Else
    22.    'Unknown Error
    23.    ChangeProperty = False
    24.      Resume Exit_ChangeProperty
    25.   End If
    26. End Function
  2. Function Call:
    Expand|Select|Wrap|Line Numbers
    1. ChangeProperty "AllowFullMenus", dbBoolean, False

13 14000
ADezii
8,800 Expert 8TB
I think you are referring to the StartUp Properties of a Database and yes, they can be modified but it is a little tricky since they are User Defined Properties and cannot be Set/Retrieved in the conventional manner. If the Property exists, you can directly modify it, if not you must create it then Append it to the proper Collection. The Code below will set the Allow Full Menus Start Up DB Option to False:
  1. Function Definition:
    Expand|Select|Wrap|Line Numbers
    1. Private Function ChangeProperty(strPropertyName As String, varPropertyType As Variant, varPropertyValue As Variant) As Integer
    2. On Error GoTo Err_ChangeProperty
    3. Dim MyDB As DAO.Database
    4. Dim MyProperty As DAO.Property
    5.  
    6. Set MyDB = CurrentDb()
    7.  
    8. 'Property exists, so set its Value
    9. MyDB.Properties(strPropertyName) = varPropertyValue
    10. ChangeProperty = True
    11.  
    12. Exit_ChangeProperty:
    13.   Exit Function
    14.  
    15. Err_ChangeProperty:
    16.   If Err.Number = 3270 Then       'Property not found
    17.     'Since the Property isn't found, create it!
    18.     Set MyProperty = MyDB.CreateProperty(strPropertyName, varPropertyType, varPropertyValue)
    19.     MyDB.Properties.Append MyProperty
    20.       Resume Next
    21.   Else
    22.    'Unknown Error
    23.    ChangeProperty = False
    24.      Resume Exit_ChangeProperty
    25.   End If
    26. End Function
  2. Function Call:
    Expand|Select|Wrap|Line Numbers
    1. ChangeProperty "AllowFullMenus", dbBoolean, False
Dec 8 '11 #2
twinnyfo
3,653 Expert Mod 2GB
Thanks ADezii,

BRILLIANT! That worked perfectly for turning off full menus. However, where does one find the names of these other properties, such as Allow Default Shortcut Menus and the like? I've tried some variations and nothing seems to work.

Also, how does one use VBA to tell the Database to open a specific form when it opens? Doing it manually is easy, but I have no clue where to start doing this in VBA....

Thanks for your help so far!
Dec 8 '11 #3
ADezii
8,800 Expert 8TB
All the answers to your questions are listed below:
Expand|Select|Wrap|Line Numbers
  1. Text in Startup Dialog Box         Property name
  2. -------------------------------------------------------------
  3. Application Title                  AppTitle
  4. Application Icon                   AppIcon
  5. Display Form/Page                  StartupForm
  6. Display Database Window            StartupShowDBWindow
  7. Display Status Bar                 StartupShowStatusBar
  8. Menu Bar                           StartupMenuBar
  9. Shortcut Menu Bar                  StartupShortcutMenuBar
  10. Allow Full Menus                   AllowFullMenus
  11. Allow Default Shortcut Menus       AllowShortcutMenus
  12. Allow Built-In Toolbars            AllowBuiltInToolbars
  13. Allow Toolbar/Menu Changes         AllowToolbarChanges
  14. Allow Viewing Code After Error     AllowBreakIntoCode
  15. Use Access Special Keys            AllowSpecialKeys
Dec 8 '11 #4
twinnyfo
3,653 Expert Mod 2GB
ADezii,

Thank ou again! I wish MS made this stuff more readily available. I was certain I had already tried some of those properties but they didn't work. This time, works like a charm!

Warmest regards!
Dec 8 '11 #5
ADezii
8,800 Expert 8TB
@twinnyfo:
It is not at all intuitive on how you can Set/Retrieve these Properties.
Dec 8 '11 #6
Mihail
759 512MB
Thank you too, ADezii.
This post is just to subscribe.

By the way: Can I subscribe to a thread without posting something in that thread (and disturb the others) ?
Dec 8 '11 #7
ADezii
8,800 Expert 8TB
@Mihail:
Can I subscribe to a thread without posting something in that thread (and disturb the others)?
I actually not 100% sure, but the person to direct this Question to would be NeoPa. Send him a Private Message with this same Question, and I'm sure he will reply to you.
Dec 8 '11 #8
NeoPa
32,173 Expert Mod 16PB
Not currently, but there used to be such a facility and we expect there to be such again in a future version of the site :-)
Dec 8 '11 #9
NeoPa
32,173 Expert Mod 16PB
That was so useful that I decided to create a module specifically to support working with Properties in Access. Reading, writing, adding and deleting are all supported, and even though the VarType() function returns values in a similar but incompatible set from the dbXXX type values required by CreateProperty(), I thought it was worthwhile to handle that with a little conversion function that handles the most common and those likely to be used with property values.

The code all seems to work :

Expand|Select|Wrap|Line Numbers
  1. Option Compare Database
  2. Option Explicit
  3.  
  4. Private Const conNoProp As Integer = 3270
  5. Private Const conVBToDB As String = "\2|3\3|4\4|6\5|7\6|5" & _
  6.                                     "\7|8\8|10\11|1\14|20\17|2"
  7.  
  8. 'SetProperty() requires that either intPType is set explicitly OR that
  9. '              varPVal has a valid value if a new property is to be created.
  10. Public Sub SetProperty(strPName As String, varPVal As Variant, _
  11.                        Optional ByVal db As DAO.Database, _
  12.                        Optional intPType As Integer = -1)
  13.     Dim prp As DAO.Property
  14.  
  15.     If db Is Nothing Then Set db = CurrentDb
  16.     If PropertyExists(strPName, db) Then
  17.         db.Properties(strPName) = varPVal
  18.     Else
  19.         If intPType = -1 Then intPType = DBVal(VarType(varPVal))
  20.         Set prp = db.CreateProperty(strPName, intPType, varPVal)
  21.         Call db.Properties.Append(prp)
  22.     End If
  23. End Sub
  24.  
  25. Public Function GetProperty(ByRef strPName As String, _
  26.                             Optional ByVal db As DAO.Database) As Variant
  27.     If db Is Nothing Then Set db = CurrentDb
  28.     If PropertyExists(strPName, db) Then GetProperty = db.Properties(strPName)
  29. End Function
  30.  
  31. Public Function PropertyExists(ByRef strPName As String, _
  32.                                Optional ByVal db As DAO.Database) As Boolean
  33.     Dim varTest As Variant
  34.  
  35.     On Error GoTo Err_PropertyExists
  36.     If db Is Nothing Then Set db = CurrentDb
  37.     PropertyExists = True
  38.     varTest = db.Properties(strPName)
  39.     Exit Function
  40.  
  41. Err_PropertyExists:
  42.     If Err <> conNoProp Then
  43.         On Error GoTo 0
  44.         Resume
  45.     End If
  46.     PropertyExists = False
  47. End Function
  48.  
  49. Public Sub DelProperty(ByRef strPName As String, _
  50.                        Optional ByVal db As DAO.Database)
  51.     If db Is Nothing Then Set db = CurrentDb
  52.     If Not PropertyExists(strPName, db) Then Exit Sub
  53.     Call db.Properties.Delete(strPName)
  54. End Sub
  55.  
  56. Private Function DBVal(intVBVal) As Integer
  57.     Dim intX As Integer
  58.  
  59.     intX = InStr(1, conVBToDB, "\" & intVBVal & "|")
  60.     DBVal = Val(Mid(conVBToDB, intX + Len(intVBVal) + 2))
  61. End Function
PS. Congrats to ADezii for helping to make such a complicated process into one that's now quite straightforward. With all this information such work should be a doddle in future.
Dec 8 '11 #10
ADezii
8,800 Expert 8TB
Nice adaptation, NeoPa.
Dec 8 '11 #11
NeoPa
32,173 Expert Mod 16PB
Thank you ADezii. My aim was not as limited as simply answering this thread (although that was certainly the starting point). I saw this was something that could be more generally helpful (to me as well as others) with just a little more meat on the bones. I expect this module to be available for my use in all future projects.
Dec 8 '11 #12
NeoPa
32,173 Expert Mod 16PB
I'm so glad I found this again. It made creating just such a module again so much easier :-D
Nov 3 '13 #13
NeoPa
32,173 Expert Mod 16PB
A hijack question has now been moved to a new thread called Set Application Title using VBA.

Please do not post new questions in existing threads.
Apr 13 '19 #14

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

13 posts views Thread by Sateesh | last post: by
2 posts views Thread by TechBoy | last post: by
4 posts views Thread by silverburgh.meryl | last post: by
3 posts views Thread by Gerrit Snel | last post: by
8 posts views Thread by Bhuwan Bhaskar | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by harlem98 | last post: by
1 post views Thread by Geralt96 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.