Property Not Found error when trying to set AllowBypassKey in A97

[MLH]

I call the following Sub and Function in frmLaunch's OnOpen
event code. I keep getting Property Not Found error for the
AllowBypassKey setting. Failure point is line #30 in the Function
(not the Sub). Ideas?

Sub SetStartupPrope rties()
On Error GoTo SetStartupPrope rties_Err
10 ChangeProperty "StartupFor m", dbText, "frmLaunch" '
Form you want to open at startup
20 ChangeProperty "StartupShowDBW indow", dbBoolean, False '
True will show the dbase window
30 ChangeProperty "StartupShowSta tusBar", dbBoolean, True
40 ChangeProperty "AllowBuiltinTo olbars", dbBoolean, True
50 ChangeProperty "AllowFullMenus ", dbBoolean, True
60 ChangeProperty "AllowBreakInto Code", dbBoolean, True
70 ChangeProperty "AllowSpecialKe ys", dbBoolean, True
80 ChangeProperty "AllowBypassKey ", dbBoolean, True '
The SHIFT key thing

SetStartupPrope rties_Bye:
Exit Sub

SetStartupPrope rties_Err:
Dim r As String, k As String, Message3 As String
r = "The following unexpected error occurred in Sub
SetStartupPrope rties, CBF on frmLaunch."
k = vbNewLine & vbNewLine & Str$(Err) & ": " & """" & Error$ &
"""" & ", line #" & Erl
Message3 = r & k
MsgBox Message3, 48, "Unexpected Error - " & MyApp$ & ", rev. " &
MY_VERSION$
Resume SetStartupPrope rties_Bye
End Sub

Function ChangeProperty( strPropName As String, varPropType As Variant,
varPropValue As Variant) As Integer
Dim dbs As Database, prp As Property
Const conPropNotFound Error = 3270

10 Set dbs = CurrentDb
20 On Error GoTo Change_Err
30 dbs.Properties( strPropName) = varPropValue
40 ChangeProperty = True

Change_Bye:
Exit Function

Change_Err:
Dim r As String, k As String, Message3 As String
r = "The following unexpected error occurred setting " &
strPropName & " property in Sub ChangeProperty, CBF on frmLaunch."
k = vbNewLine & vbNewLine & Str$(Err) & ": " & """" & Error$ &
"""" & ", line #" & Erl
Message3 = r & k
MsgBox Message3, 48, "Unexpected Error - " & MyApp$ & ", rev. " &
MY_VERSION$
Resume Change_Bye

End Function

[Albert D. Kallal]

Try downloading my sample shift key by-pass setter.

You can find it here:

http://www.members.shaw.ca/AlbertKal.../msaccess.html

Note how in the above, the ChangePrpperity code is different then yours.
(you need to add the shiftkey property if it errors out...and it seems your
code sample does not do that).
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl************* ****@msn.com
http://www.members.shaw.ca/AlbertKallal

[MLH]

I'm trying, really, I am...

Functional lines in yours...
'Set dbs = CurrentDb
On Error GoTo Change_Err
dbs.Properties( strPropName) = varPropValue
ChangeProperty = True

Functional lines in mine...
10 Set dbs = CurrentDb
20 On Error GoTo Change_Err
30 dbs.Properties( strPropName) = varPropValue
40 ChangeProperty = True

They are too close for me. I noticed you have 4 argumentsto
the ChangeProperty function in your code...
Function ChangeProperty( strPropName As String, _
varPropType As Variant, _
varPropValue As Variant, _
dbs As Database) As Integer
' The current listing in Access help file which will
' let anyone who can open the db delete/reset any
' property created by using this function, since
' the call to CraeteProperty doesn't use the DDL
' argument

Do you think that has something to do with why my one
property is Not Found. The others are all found.

Try downloading my sample shift key by-pass setter.

You can find it here:

http://www.members.shaw.ca/AlbertKal.../msaccess.html

Note how in the above, the ChangePrpperity code is different then yours.
(you need to add the shiftkey property if it errors out...and it seems your
code sample does not do that).

[Douglas J. Steele]

It's not the functional lines that are the problem, it's the error handling.

Many of the properties to which you're referring do not exist by default:
you need to explicitly create them. That's the reason why

Const conPropNotFound Error = 3270

exists in your code: in your error handling section, you have to check
whether that's the error that's raised, and create the property if it is,
rather than treating it the way you do other errors.

Take a look at this version of ChangeProperty, from
http://www.mvps.org/access/general/gen0040.htm at "The Access Web"

Function ChangeProperty( strPropName As String, _
varPropType As Variant, varPropValue As Variant) As Integer
' The current listing in Access help file which will
' let anyone who can open the db delete/reset any
' property created by using this function, since
' the call to CreateProperty doesn't use the DDL
' argument
'
Dim dbs As Database, prp As Property
Const conPropNotFound Error = 3270

Set dbs = CurrentDb
On Error GoTo Change_Err
dbs.Properties( strPropName) = varPropValue
ChangeProperty = True

Change_Bye:
Exit Function

Change_Err:
If Err = conPropNotFound Error Then ' Property not found.
Set prp = dbs.CreatePrope rty(strPropName , _
varPropType, varPropValue)
dbs.Properties. Append prp
Resume Next
Else
' Unknown error.
ChangeProperty = False
Resume Change_Bye
End If
End Function

I haven't downloaded Albert's example, but I suspect it has similar logic in
it.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"MLH" <CR**@NorthStat e.net> wrote in message
news:h2******** *************** *********@4ax.c om...

I'm trying, really, I am...

Functional lines in yours...
'Set dbs = CurrentDb
On Error GoTo Change_Err
dbs.Properties( strPropName) = varPropValue
ChangeProperty = True

Functional lines in mine...
10 Set dbs = CurrentDb
20 On Error GoTo Change_Err
30 dbs.Properties( strPropName) = varPropValue
40 ChangeProperty = True

They are too close for me. I noticed you have 4 argumentsto
the ChangeProperty function in your code...
Function ChangeProperty( strPropName As String, _
varPropType As Variant, _
varPropValue As Variant, _
dbs As Database) As Integer
' The current listing in Access help file which will
' let anyone who can open the db delete/reset any
' property created by using this function, since
' the call to CraeteProperty doesn't use the DDL
' argument

Do you think that has something to do with why my one
property is Not Found. The others are all found.

Try downloading my sample shift key by-pass setter.

You can find it here:

http://www.members.shaw.ca/AlbertKal.../msaccess.html

Note how in the above, the ChangePrpperity code is different then yours.
(you need to add the shiftkey property if it errors out...and it seems
your
code sample does not do that).

[MLH]

Now I know why they call you guys MVP's.
That did the trick. 'preciate you setting me
straight on it. I would never have figured it
out.

xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxxx

It's not the functional lines that are the problem, it's the error handling.

<censored>

[MLH]

Say, if I remember correctly, there was not
a convenient way around the SHIFT bypass
in Access 2.0, was there?

[MLH]

So, now that I know about this cool new way of using
property settings to control whether database window
shows or not and whether shift bypass is allowed, should
I do away with this old way of restoring the database
window on demand?

....

DoCmd.DoMenuIte m A_FORMBAR, 4, 4, 0, A_MENU_VER20

What's an up-to-date replacement procedure? Tired of living
in the past.

[David W. Fenton]

MLH <CR**@NorthStat e.net> wrote in
news:e4******** *************** *********@4ax.c om:

Now I know why they call you guys MVP's.

Because they can read the Access help files?

Hello?

The code for setting this is found in the A97 help file under
"bypassing startup settings." The code that is there automatically
handles the property not already existing.

It would *have* to be, as that's the nature of much of Access --
Access objects are just Jet objects with a lot of "custom"
properties (from the Jet point of view). And many of the properties
are not created until the point at which a value is set for them.

You can easily see this demonstrated by cycling through the
properties of any Access object. You'll see that the number of
existing properties in the properties collection is fewer than the
number of properties listed on the object's corresponding properties
sheet. That's because, until you *set* many of those property in the
property sheet (or through code), the property does not yet exist.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

MLH <CR**@NorthStat e.net> wrote in
news:2e******** *************** *********@4ax.c om:

So, now that I know about this cool new way of using
property settings to control whether database window
shows or not and whether shift bypass is allowed, should
I do away with this old way of restoring the database
window on demand?

...

DoCmd.DoMenuIte m A_FORMBAR, 4, 4, 0, A_MENU_VER20

What's an up-to-date replacement procedure? Tired of living
in the past.

Look at the help for DoCmd.SelectObj ect.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

MLH <CR**@NorthStat e.net> wrote in
news:2e******** *************** *********@4ax.c om:

So, now that I know about this cool new way of using
property settings to control whether database window
shows or not and whether shift bypass is allowed, should
I do away with this old way of restoring the database
window on demand?

...

DoCmd.DoMenuIte m A_FORMBAR, 4, 4, 0, A_MENU_VER20

What's an up-to-date replacement procedure? Tired of living
in the past.

BTW, I'd highly recommend that you spend a lot of time navigating
the help files. I'm not sure which version you're developing in, but
if it's A97, you've got the best set of help files for Access that
Microsoft ever produced.

You will learn a lot by familiarizing yourself with their structure
and terminology.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc