Re: Access 2003 and unsafe macros
From: nemo2 (nemo2_at_charter.net)
Date: 04/06/04
- Next message: TC: "Re: Security in Multi User env"
- Previous message: nemo2: "Re: Access 2003 and unsafe macros"
- In reply to: TC: "Re: Access 2003 and unsafe macros"
- Next in thread: TC: "Re: Access 2003 and unsafe macros"
- Reply: TC: "Re: Access 2003 and unsafe macros"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 5 Apr 2004 22:15:28 -0500
No such registry key (Office\11.0\Access\Security)
"TC" <a@b.c.d> wrote in message news:1081210111.138196@teuthos...
>
> "nemo2" <nemo2@charter.net> wrote in message
> news:1072qe5rc6g54d9@corp.supernews.com...
>
> > Re: Macro security to Low, no way I can find to do so in new Access,
> unlike
> > Excel and other parts of Office, which all have been set to Low.
>
> I don't have A2k+ myself, but I believe you can do it as follows.
>
> - Under Tools:security, or
>
> - if the relevant option doesn't appear, search around in the Customze
> menus, or
>
> - add registry key HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
> \Access\Security with a DWord value "Level" (without the quote marks)
equal
> to 1.
No such registry key (Office\11.0\Access\Security)
>
>
> > Re: Developer security, I have a cert and have signed the macros.
>
> Then that should stop the warnings, surely? (Unless maybe your code
modifies
> itself, eg. by changing the SQL of a stored query.) Maybe post a new
> question asking why signing your macros does not stop the warning. I'm no
> expert on that.
>
>
> > Re: Jet engine, I'm sure you are right. I don't remember the exacxt
> > suggestion MS made. I believe it may have been an update to v.4 of the
Jet
> > program, but I'm not sure.
>
>
> > Re: unable to use Start-up Form, the message I receive is Microsoft
Jet
> > database engine could not find the object ", Make sure the object exists
> and
> > that you spell it correctly. I don't understand the parenthesis in the
> > above sentence. Is it possible there is a parenthesis somewhere in the
> > properties of this form that is in error?
>
> That sounds more like a database corruption problem, to me. If the startup
> form's name is correct in the startup property, and the startup form does
> exist with that name, and that form does work when you run it manually,
but
> it gets that message when you start the database, I'd be importing all
your
> objects into a new db & trying again.
>
> HTH,
> TC
>
>
> > Thanks.
> >
> >
> > "TC" <no@email.here> wrote in message
> > news:4070b718$1_1@news.chariot.net.au...
> > >
> > > "nemo2" <nemo2@charter.net> wrote in message
> > > news:107189o5rptfof3@corp.supernews.com...
> > > > W2K, Office 2003
> > >
> > > > I just installed Office 2003 upgrade from Office XP and am having
> > > problems,
> > > > particularly with Access. I need to answer 3 separate dialog boxes
> > telling
> > > > me there are unsafe macros in order to get into my data.
> > >
> > > Office 2003 gives you these warnings unless:
> > > (a) you set Macro Security back to Low;
> > > (b) you get the developer of the database to "sign" it electronically,
> or
> > > (c) you use the selfcert.exe program to sign it yourself.
> > >
> > > IMO, most users will not be able to do (b) or (c), so they will go for
> > > option (a) - the exact reverse of what Microsoft probably wanted to
> > achieve,
> > > when they added these new warnings.
> > >
> > >
> > > > Initially, Msoft
> > > > suggested I download the MS Jet engine, and the problems may have
> begun
> > > > then.
> > >
> > > Er, Jet is the database part of Access. Without having Jet "behind the
> > > scenes", you would not have been able to use your Access data >at
all<.
> So
> > I
> > > doubt that this is what Microsoft suggested to solve the macro warning
> > > problem!
> > >
> > >
> > > > I have some code left over from previous versions, but nothing
> > > > malicious, since I created it.
> > >
> > > All users have applications that they trust, and that they >do not<
want
> > > these warnings from. Microsoft's implementation of the new warnings is
> > > half-baked, IMO, because they have not given the user any easy &
> > > straightforward way of saying, "I trust application X - do not give me
> any
> > > more warnings from it!"
> > >
> > >
> > > > I also have a start-up form in one Access file that can't be opened
in
> > the
> > > > new version, but always could in Access 2002.
> > >
> > > What do you mean, it can't be opened? What happens when you try to
open
> > it?
> > >
> > > HTH,
> > > TC
> > >
> > >
> > > > How can I get past these hassles?
> > > > Thanks
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: TC: "Re: Security in Multi User env"
- Previous message: nemo2: "Re: Access 2003 and unsafe macros"
- In reply to: TC: "Re: Access 2003 and unsafe macros"
- Next in thread: TC: "Re: Access 2003 and unsafe macros"
- Reply: TC: "Re: Access 2003 and unsafe macros"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
