Re: Access 2003 Macro Security Modification
From: Beth (BethMoffitt_at_iniinc.com)
Date: 02/27/04
- Next message: Brian Camire: "Re: SELECTing records"
- Previous message: Djoezz: "SELECTing records"
- In reply to: Mike Wachal: "Re: Access 2003 Macro Security Modification"
- Next in thread: Peter Russell: "Re: Access 2003 Macro Security Modification"
- Reply: Peter Russell: "Re: Access 2003 Macro Security Modification"
- Reply: Mike Wachal: "Re: Access 2003 Macro Security Modification"
- Messages sorted by: [ date ] [ thread ]
Date: 27 Feb 2004 07:19:21 -0800
Hello Mike and thanks for your reply. However, you either didn't read
or understand what I was saying in my post. I am a software developer
for a retail product. I'm not worried about security settings in
development as I don't think I am going to write anything that is
going to wipe out my own hard drive. :/
My issue is when we sell this app to clients and they have medium or
high security settings. No, we don't have digitally signed
applications, but since this latest 'feature' of M$'s, it looks like
we will have to go down this road since we won't be modifying the
clients' registry key.
Thanks again for your time.
Beth Moffitt
Mike Wachal <mikewa@online.microsoft.com> wrote in message news:<zsrjd0kdrqcj$.yizcqiovnnt$.dlg@40tude.net>...
> Hi Beth,
>
> I'm sorry to hear that you are strugling with the Automation Security
> property. It might help if you copy the code that is failing for you into
> the newsgroup so we can take a look at it. If you are trying to use this
> property from VBA inside an Office application, you will need to have a
> reference to the Office 11 TypeLib.
>
> I've written two pieces of sample code, both are working successfully in my
> test environment (WinXP Pro, Office 2003 Pro). Here is my code for
> reference.
>
> This is VBA code that I run from within Access to use automation to open a
> separate database.
>
<snipped code>
>
This doesn't make any
> kind of setting on the database or change a setting permanently in Access.
>
> The second sample code I actually pulled from the following help topic:
>
> http://office.microsoft.com/assistance/preview.aspx?AssetID=HP010397921033
> &CTT=98
>
> This code is in VBScript and is a great way to open your development
> database on a computer that has High or Medium security. The idea here is
> that while it makes sense that any production database on you computer
> would be signed, the database your are currently developing might not be.
> You can open them by making a shortcut to the script rather than to the
> database itself.
<snipped more code>
>
> Let me know if these samples don't work for you.
>
> --
> Regards,
> Mike Wachal
> Microsoft Corporation
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> On 19 Feb 2004 09:41:03 -0800, Beth wrote:
>
> > Thanks for the replies. I did have a reference to the correct
> > library, but it didn't work. I changed to the integer value and still
> > didn't work. So, I did what every good developer does... Rearched
> > until I need a new perscription in eyeglasses! This is what I have
> > found so far. Maybe it will keep someone else from reading till they
> > go blind while looking for a resolution!
> >
> > Access installs with Security Level default of Medium. Users are
> > prompted when opening an Access database and receive the message "This
> > file may not be safe if it contains code that was intended to harm
> > your computer. Do you want to open this file or cancel the
> > operation?" They are then prompted with Cancel, Open or More Info.
> > If they choose Cancel, the app will not open. To quote Microsoft,
> > "This message is a result of new security features that are part of
> > Access 2003. For more information on these features, see Migrating to
> > Access 2003, on Office Online." Microsoft also publishes the
> > following:
- Next message: Brian Camire: "Re: SELECTing records"
- Previous message: Djoezz: "SELECTing records"
- In reply to: Mike Wachal: "Re: Access 2003 Macro Security Modification"
- Next in thread: Peter Russell: "Re: Access 2003 Macro Security Modification"
- Reply: Peter Russell: "Re: Access 2003 Macro Security Modification"
- Reply: Mike Wachal: "Re: Access 2003 Macro Security Modification"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|