Startup Properties Help

Startup Properties Help

am 13.10.2007 16:57:09 von pdtay84

Having some trouble with an unfinished database. I'm a moderate user,
not a beginner, but I'm training myself more advanced options. I have
an unfinished database that I set the startup properties to disable
all the menus (oops.) How can I get back in to edit the database. I
read somewhere pressing F11 will bring up the menu but it does nothing.

Re: Startup Properties Help

am 13.10.2007 16:58:12 von Rick Brandt

pdtay84 wrote:
> Having some trouble with an unfinished database. I'm a moderate user,
> not a beginner, but I'm training myself more advanced options. I have
> an unfinished database that I set the startup properties to disable
> all the menus (oops.) How can I get back in to edit the database. I
> read somewhere pressing F11 will bring up the menu but it does
> nothing.

Hold shift while opening the file.

(F11 is one of the things you disabled)

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Re: Startup Properties Help

am 13.10.2007 22:06:02 von Larry Linson

To add to Rick's comments: You can disable the Shift option, too, and then
you could be "up the proverbial creek." It is always a good idea to save a
development copy without the "finishing touches" added, and set the Startup
properties on a copy just before you distribute it.

Of course, you'll have separated that "front end" copy from the "back end"
containing tables, relationships, and data and linked the back end tables to
the front end, so if you update, test, finish, and distribute a new copy of
the front end, you will not lose your data.

Larry Linson
Microsoft Access MVP

"Rick Brandt" wrote in message
news:825Qi.43937$RX.42334@newssvr11.news.prodigy.net...
> pdtay84 wrote:
>> Having some trouble with an unfinished database. I'm a moderate user,
>> not a beginner, but I'm training myself more advanced options. I have
>> an unfinished database that I set the startup properties to disable
>> all the menus (oops.) How can I get back in to edit the database. I
>> read somewhere pressing F11 will bring up the menu but it does
>> nothing.
>
> Hold shift while opening the file.
>
> (F11 is one of the things you disabled)
>
> --
> Rick Brandt, Microsoft Access MVP
> Email (as appropriate) to...
> RBrandt at Hunter dot com
>

Re: Startup Properties Help

am 13.10.2007 23:50:09 von Lye Fairfield

"Larry Linson" wrote in
news:Ky9Qi.1379$2o1.974@trnddc03:

> To add to Rick's comments: You can disable the Shift option, too, and
> then you could be "up the proverbial creek."

Larry

I think this can be used as a paddle by running it from another Access
application:

Public Sub ResetStartProperties(ByVal FullPathToApplication$)
' I found this to be difficult
' and not well-documented.
' if you can make it simpler,
' please, tell me and the world
Dim a As Access.Application
Dim aProperties(0 To 9, 0 To 1)
Dim pa As AccessObjectProperty
Dim z&
aProperties(0, 0) = "AllowBuiltInToolbars"
aProperties(1, 0) = "AllowByPassKey"
aProperties(2, 0) = "AllowFullMenus"
aProperties(3, 0) = "AllowShortCutMenus"
aProperties(4, 0) = "AllowSpecialKeys"
aProperties(5, 0) = "AllowToolbarChanges"
aProperties(6, 0) = "StartUpShowDBWindow"
aProperties(7, 0) = "StartUpShowStatusBar"
aProperties(8, 0) = "StartUpMenuBar"
aProperties(9, 0) = "StartUpShortcutMenuBar"
For z = 0 To 7
aProperties(z, 1) = True
Next z
For z = 8 To 9
aProperties(z, 1) = vbNullString
Next z
Set a = New Access.Application
With a
.OpenCurrentDatabase FullPathToApplication, True
On Error Resume Next
For z = 0 To 9
With .CurrentDb.Properties
.Delete aProperties(z, 0)
.Refresh
End With
With .CurrentProject.Properties
Set pa = .Item(aProperties(z, 0))
.Remove pa
pa.Value = aProperties(z, 1)
End With
Next z
On Error GoTo 0
.CloseCurrentDatabase
.Quit
End With
End Sub

Private Sub testMDB()
ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
Documents\Access\northwind.mdb"
End Sub

Private Sub testADP()
ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
Documents\Access\terraware.adp"
End Sub

--
lyle fairfield

Re: Startup Properties Help

am 14.10.2007 00:30:09 von Stuart McCall

"lyle fairfield" wrote in message
news:l4bQi.8540$9F1.1259@read1.cgocable.net...
> "Larry Linson" wrote in
> news:Ky9Qi.1379$2o1.974@trnddc03:
>
>> To add to Rick's comments: You can disable the Shift option, too, and
>> then you could be "up the proverbial creek."
>
> Larry
>
> I think this can be used as a paddle by running it from another Access
> application:
>
> Public Sub ResetStartProperties(ByVal FullPathToApplication$)
> ' I found this to be difficult
> ' and not well-documented.
> ' if you can make it simpler,
> ' please, tell me and the world
> Dim a As Access.Application
> Dim aProperties(0 To 9, 0 To 1)
> Dim pa As AccessObjectProperty
> Dim z&
> aProperties(0, 0) = "AllowBuiltInToolbars"
> aProperties(1, 0) = "AllowByPassKey"
> aProperties(2, 0) = "AllowFullMenus"
> aProperties(3, 0) = "AllowShortCutMenus"
> aProperties(4, 0) = "AllowSpecialKeys"
> aProperties(5, 0) = "AllowToolbarChanges"
> aProperties(6, 0) = "StartUpShowDBWindow"
> aProperties(7, 0) = "StartUpShowStatusBar"
> aProperties(8, 0) = "StartUpMenuBar"
> aProperties(9, 0) = "StartUpShortcutMenuBar"
> For z = 0 To 7
> aProperties(z, 1) = True
> Next z
> For z = 8 To 9
> aProperties(z, 1) = vbNullString
> Next z
> Set a = New Access.Application
> With a
> .OpenCurrentDatabase FullPathToApplication, True
> On Error Resume Next
> For z = 0 To 9
> With .CurrentDb.Properties
> .Delete aProperties(z, 0)
> .Refresh
> End With
> With .CurrentProject.Properties
> Set pa = .Item(aProperties(z, 0))
> .Remove pa
> pa.Value = aProperties(z, 1)
> End With
> Next z
> On Error GoTo 0
> .CloseCurrentDatabase
> .Quit
> End With
> End Sub
>
> Private Sub testMDB()
> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
> Documents\Access\northwind.mdb"
> End Sub
>
> Private Sub testADP()
> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
> Documents\Access\terraware.adp"
> End Sub
>
> --
> lyle fairfield

Nice routine. Just to satisfy my curiosity, why do you do this bit:

> With .CurrentDb.Properties
> .Delete aProperties(z, 0)
> .Refresh
> End With

and this:

> .Remove pa

when you're overwriting them all anyway?

Re: Startup Properties Help

am 14.10.2007 00:37:58 von Larry Linson

Thanks, Lyle. Is "paddle" the correct word, not "shovel"? Larry

I keep a separate development copy of each application as a matter of course
(even for my own single-user databases), so putting the "finishing touches"
on a copy of them when it's time to distribute is no great burden.

Larry

"lyle fairfield" wrote in message
news:l4bQi.8540$9F1.1259@read1.cgocable.net...
> "Larry Linson" wrote in
> news:Ky9Qi.1379$2o1.974@trnddc03:
>
>> To add to Rick's comments: You can disable the Shift option, too, and
>> then you could be "up the proverbial creek."
>
> Larry
>
> I think this can be used as a paddle by running it from another Access
> application:
>
> Public Sub ResetStartProperties(ByVal FullPathToApplication$)
> ' I found this to be difficult
> ' and not well-documented.
> ' if you can make it simpler,
> ' please, tell me and the world
> Dim a As Access.Application
> Dim aProperties(0 To 9, 0 To 1)
> Dim pa As AccessObjectProperty
> Dim z&
> aProperties(0, 0) = "AllowBuiltInToolbars"
> aProperties(1, 0) = "AllowByPassKey"
> aProperties(2, 0) = "AllowFullMenus"
> aProperties(3, 0) = "AllowShortCutMenus"
> aProperties(4, 0) = "AllowSpecialKeys"
> aProperties(5, 0) = "AllowToolbarChanges"
> aProperties(6, 0) = "StartUpShowDBWindow"
> aProperties(7, 0) = "StartUpShowStatusBar"
> aProperties(8, 0) = "StartUpMenuBar"
> aProperties(9, 0) = "StartUpShortcutMenuBar"
> For z = 0 To 7
> aProperties(z, 1) = True
> Next z
> For z = 8 To 9
> aProperties(z, 1) = vbNullString
> Next z
> Set a = New Access.Application
> With a
> .OpenCurrentDatabase FullPathToApplication, True
> On Error Resume Next
> For z = 0 To 9
> With .CurrentDb.Properties
> .Delete aProperties(z, 0)
> .Refresh
> End With
> With .CurrentProject.Properties
> Set pa = .Item(aProperties(z, 0))
> .Remove pa
> pa.Value = aProperties(z, 1)
> End With
> Next z
> On Error GoTo 0
> .CloseCurrentDatabase
> .Quit
> End With
> End Sub
>
> Private Sub testMDB()
> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
> Documents\Access\northwind.mdb"
> End Sub
>
> Private Sub testADP()
> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
> Documents\Access\terraware.adp"
> End Sub
>
> --
> lyle fairfield

Re: Startup Properties Help

am 14.10.2007 07:17:43 von Lye Fairfield

"Stuart McCall" wrote in
news:fergva$lup$1$8300dec7@news.demon.co.uk:

> "lyle fairfield" wrote in message
> news:l4bQi.8540$9F1.1259@read1.cgocable.net...
>> "Larry Linson" wrote in
>> news:Ky9Qi.1379$2o1.974@trnddc03:
>>
>>> To add to Rick's comments: You can disable the Shift option, too,
>>> and then you could be "up the proverbial creek."
>>
>> Larry
>>
>> I think this can be used as a paddle by running it from another
>> Access application:
>>
>> Public Sub ResetStartProperties(ByVal FullPathToApplication$)
>> ' I found this to be difficult
>> ' and not well-documented.
>> ' if you can make it simpler,
>> ' please, tell me and the world
>> Dim a As Access.Application
>> Dim aProperties(0 To 9, 0 To 1)
>> Dim pa As AccessObjectProperty
>> Dim z&
>> aProperties(0, 0) = "AllowBuiltInToolbars"
>> aProperties(1, 0) = "AllowByPassKey"
>> aProperties(2, 0) = "AllowFullMenus"
>> aProperties(3, 0) = "AllowShortCutMenus"
>> aProperties(4, 0) = "AllowSpecialKeys"
>> aProperties(5, 0) = "AllowToolbarChanges"
>> aProperties(6, 0) = "StartUpShowDBWindow"
>> aProperties(7, 0) = "StartUpShowStatusBar"
>> aProperties(8, 0) = "StartUpMenuBar"
>> aProperties(9, 0) = "StartUpShortcutMenuBar"
>> For z = 0 To 7
>> aProperties(z, 1) = True
>> Next z
>> For z = 8 To 9
>> aProperties(z, 1) = vbNullString
>> Next z
>> Set a = New Access.Application
>> With a
>> .OpenCurrentDatabase FullPathToApplication, True
>> On Error Resume Next
>> For z = 0 To 9
>> With .CurrentDb.Properties
>> .Delete aProperties(z, 0)
>> .Refresh
>> End With
>> With .CurrentProject.Properties
>> Set pa = .Item(aProperties(z, 0))
>> .Remove pa
>> pa.Value = aProperties(z, 1)
>> End With
>> Next z
>> On Error GoTo 0
>> .CloseCurrentDatabase
>> .Quit
>> End With
>> End Sub
>>
>> Private Sub testMDB()
>> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
>> Documents\Access\northwind.mdb"
>> End Sub
>>
>> Private Sub testADP()
>> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
>> Documents\Access\terraware.adp"
>> End Sub
>>
>> --
>> lyle fairfield
>
> Nice routine. Just to satisfy my curiosity, why do you do this bit:
>
>> With .CurrentDb.Properties
>> .Delete aProperties(z, 0)
>> .Refresh
>> End With
>
> and this:
>
>> .Remove pa
>
> when you're overwriting them all anyway?

There's not much documentation about these, and testing the existence
and value of these properties is tedious.So I'm doing everything I can
to be sure they are the way I want them, even though some it is likely
to be redundant.

--
lyle fairfield

Re: Startup Properties Help

am 14.10.2007 11:41:00 von Stuart McCall

"lyle fairfield" wrote in message
news:XDhQi.7810$xa2.6520@read2.cgocable.net...


> There's not much documentation about these, and testing the existence
> and value of these properties is tedious.So I'm doing everything I can
> to be sure they are the way I want them, even though some it is likely
> to be redundant.
>
> --
> lyle fairfield

Understood. Thanks.

Re: Startup Properties Help

am 14.10.2007 11:50:34 von Stuart McCall

"lyle fairfield" wrote in message
news:XDhQi.7810$xa2.6520@read2.cgocable.net...
> "Stuart McCall" wrote in
> news:fergva$lup$1$8300dec7@news.demon.co.uk:
>
>> "lyle fairfield" wrote in message
>> news:l4bQi.8540$9F1.1259@read1.cgocable.net...
>>> "Larry Linson" wrote in
>>> news:Ky9Qi.1379$2o1.974@trnddc03:
>>>
>>>> To add to Rick's comments: You can disable the Shift option, too,
>>>> and then you could be "up the proverbial creek."
>>>
>>> Larry
>>>
>>> I think this can be used as a paddle by running it from another
>>> Access application:
>>>
>>> Public Sub ResetStartProperties(ByVal FullPathToApplication$)
>>> ' I found this to be difficult
>>> ' and not well-documented.
>>> ' if you can make it simpler,
>>> ' please, tell me and the world
>>> Dim a As Access.Application
>>> Dim aProperties(0 To 9, 0 To 1)
>>> Dim pa As AccessObjectProperty
>>> Dim z&
>>> aProperties(0, 0) = "AllowBuiltInToolbars"
>>> aProperties(1, 0) = "AllowByPassKey"
>>> aProperties(2, 0) = "AllowFullMenus"
>>> aProperties(3, 0) = "AllowShortCutMenus"
>>> aProperties(4, 0) = "AllowSpecialKeys"
>>> aProperties(5, 0) = "AllowToolbarChanges"
>>> aProperties(6, 0) = "StartUpShowDBWindow"
>>> aProperties(7, 0) = "StartUpShowStatusBar"
>>> aProperties(8, 0) = "StartUpMenuBar"
>>> aProperties(9, 0) = "StartUpShortcutMenuBar"
>>> For z = 0 To 7
>>> aProperties(z, 1) = True
>>> Next z
>>> For z = 8 To 9
>>> aProperties(z, 1) = vbNullString
>>> Next z
>>> Set a = New Access.Application
>>> With a
>>> .OpenCurrentDatabase FullPathToApplication, True
>>> On Error Resume Next
>>> For z = 0 To 9
>>> With .CurrentDb.Properties
>>> .Delete aProperties(z, 0)
>>> .Refresh
>>> End With
>>> With .CurrentProject.Properties
>>> Set pa = .Item(aProperties(z, 0))
>>> .Remove pa
>>> pa.Value = aProperties(z, 1)
>>> End With
>>> Next z
>>> On Error GoTo 0
>>> .CloseCurrentDatabase
>>> .Quit
>>> End With
>>> End Sub
>>>
>>> Private Sub testMDB()
>>> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
>>> Documents\Access\northwind.mdb"
>>> End Sub
>>>
>>> Private Sub testADP()
>>> ResetStartProperties "C:\Documents and Settings\Lyle Fairfield\My
>>> Documents\Access\terraware.adp"
>>> End Sub
>>>
>>> --
>>> lyle fairfield
>>
>> Nice routine. Just to satisfy my curiosity, why do you do this bit:
>>
>>> With .CurrentDb.Properties
>>> .Delete aProperties(z, 0)
>>> .Refresh
>>> End With
>>
>> and this:
>>
>>> .Remove pa
>>
>> when you're overwriting them all anyway?
>
> There's not much documentation about these, and testing the existence
> and value of these properties is tedious.So I'm doing everything I can
> to be sure they are the way I want them, even though some it is likely
> to be redundant.
>
> --
> lyle fairfield

I see. Just wondered. Thanks.

Re: Startup Properties Help

am 14.10.2007 23:01:27 von Larry Linson

"lyle fairfield" wrote

> Larry
>
> I think this can be used as a paddle by running it from another Access
> application:

But, even though re-adding finishing touches at distribution time is no
burden for me, I appreciate your advice and your code, which I have copied
for future use, if/when needed... and I sometimes do, if I inherit a
"tightly secured" database that a previous contractor secured for (from?) a
client.

Larry