Re: self-signing certificate

Hi, Josh.

It has not been set

Your description of "got the warning about being blocked" sounds like you're
describing the Sandbox mode, not the Macro Security level. If you want to
test which Macro Security level is being used for the current instance of
Access, place the following code in your startup form, save, and compile:

Private Sub Form_Open(Cancel As Integer)

On Error GoTo ErrHandler

MsgBox "AutomationSecurity is set to " & Application.AutomationSecurity

Exit Sub

ErrHandler:

MsgBox "Error in Form_Open( ) in" & vbCrLf & _
Me.Name & " form." & vbCrLf & vbCrLf & _
"Error #" & Err.Number & vbCrLf & vbCrLf & Err.Description
Err.Clear

End Sub

If the message box displays "AutomationSecurity is set to 2" when your
database opens, then select the Tools -> Macro -> Security... menu to open
the Security dialog window. Whichever level you see displayed there is the
Macro Security level that the current instance of Access is using. However,
if you're using the Automation VB Script on Jeff Conrad's Web site, then you
should see "AutomationSecurity is set to 1" displayed, meaning that despite
the value set in the Security dialog window (which reflects the Windows
Registry setting), the database was opened with Macro Security set to Low.

Ok, but , 'for this instance of Access', security should have been set to
low
via the script, and therefore I shouldn't have gotten a warning...?

So you see the question, "Do you want to open this file or cancel the
operation?" when you use the script and have three buttons to push,
"Cancel," "Open," and "More Info"? That question indicates Macro Security
level is Medium and the database file is not digitally signed. If you don't
see this question, but instead see "Microsoft Office Access cannot open <DB
file name> due to security restrictions," then this indicates that the Macro
Security level is High and the database file is not digitally signed. If
you see neither of these messages, then the Macro Security level is Low.

However, you'll get a warning about the Sandbox mode if your current Macro
Security level requires unsafe expressions to be blocked in order to work
correctly. Automation Security (to alter the Macro Security level) is a
separate issue from Jet 4.0 SP-8's Sandbox mode issue, which is why you get
so many different prompts when you're using the new security features of
Access 2003.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


"Josh" <traygo@xxxxxxxxxxx> wrote in message
news:uuf0a2d2ttar4jd6qnu744qjfu5heibi3b@xxxxxxxxxx

It will if you're using Access 2003, scripts are not blocked, and
User-level
Security have not been implemented on the database file.

It has not been set

and was trying to figure out where to put the line:
Application.RunCommand acCmdAppMaximize

It should be placed in the start up form's OnLoad( ) or OnOpen( ) event,
whichever is more convenient.

yes, I had placed it in the OnOpen event

but got the warning about being blocked

"Unsafe expressions" are checked by Jet's Expression Service, so if you
have
the Sandbox mode set to 1 or 3 when Jet 4.0 SP-8 is installed, it doesn't
matter which Macro Security level you have it set at, because your Macro
Security level is an entirely separate issue. Set the Sandbox mode back
to
2 and you won't be blocked, although you'll get a warning message that
"unsafe expressions" are not blocked if you have the Macro Security level
set at Medium or High.

thats when I went and
checked, and sure nuff, security was set to [Medium]

As it's designed to do. That script doesn't change the actual Windows
Registry setting, which is what you're reading when you open the Security
dialog window. That script only changes the Access.Application object's
AutomationSecurity Property to the indicated security level for that
specific instance of Access, as explained on Jeff's Web page: ". . . a
script file which sets the macro security level to low for that single
invocation of Access." The script is intended for users who don't have
Windows security permissions to make changes in the Windows Registry.

Ok, but , 'for this instance of Access', security should have been set to
low
via the script, and therefore I shouldn't have gotten a warning...?

Thanks, Josh




HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.


"Josh" <traygo@xxxxxxxxxxx> wrote in message
news:1a0u92lt1u3pm9qmvt4v2upp1vj5s2qo22@xxxxxxxxxx
hmmmmmmm, went to:
http://home.bendbroadband.com/conradsystems/accessjunkie/macrosecurity.html

and used his VBscript, but it does NOT set security to Low, for me
anyways. I
ran the script, and was trying to figure out where to put the line:
Application.RunCommand acCmdAppMaximize
I tried just putting it in a macro and running that, just to verify that
it did
maximize access, but got the warning about being blocked, thats when I
went and
checked, and sure nuff, security was set to low.

Josh




.

Loading