Re: Access 2000 to Access 2003 conversion
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Wed, 14 Sep 2005 14:28:02 +0800
Yes, you can purchase a certificate and pay annual fees if you have a
company (not as an individual).
It's not a great solution though. The user still gets the message every time
they open the database. And you have to resign the application any time you
make a change to any code, action query, etc. And there is also the issues
with Sandbox mode.
Setting it to low yields exactly the same results as all previous versions
of Access. Unless you are accepting databases from unknown people who could
have malicious intentions, this whole macro security thing is a non-issue
that MS is trying to pretend to be doing somehthing useful about. It's about
as useful as forcing people who wear seatbelts on bicycles.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"bignerd" <eric@xxxxxxxxxxxxxxx> wrote in message
news:1126664314.533976.41460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> In regards to the security option, currently it is set to Medium and I
> am prompted when I start the application. However, I'm hesitent to set
> it at low. Can I "sign" my app or do something so that I don't have to
> change the security settings? Does this apply for ALL MDBs that I'd
> open? I just don't want to have any problems with this.
.
- References:
- Access 2000 to Access 2003 conversion
- From: bignerd
- Re: Access 2000 to Access 2003 conversion
- From: Allen Browne
- Re: Access 2000 to Access 2003 conversion
- From: bignerd
- Access 2000 to Access 2003 conversion
- Prev by Date: Re: Access 2000 to Access 2003 conversion
- Next by Date: dsdf
- Previous by thread: Re: Access 2000 to Access 2003 conversion
- Next by thread: Access 97 under Win 2k to Access 2003 under XP
- Index(es):
Relevant Pages
|