Re: Bypass Security Warnings in Access Runtime
From: Paul Overway (paul_at_I.hate.spam.logico-solutions.com)
Date: 01/28/05
- Next message: Pattyt: "Parameter Message in a split DB"
- Previous message: Colin Nash [MVP]: "Re: Perhaps the most OBVIOUS question you will ever see."
- In reply to: TC: "Re: Bypass Security Warnings in Access Runtime"
- Next in thread: TC: "Re: Bypass Security Warnings in Access Runtime"
- Reply: TC: "Re: Bypass Security Warnings in Access Runtime"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 Jan 2005 00:29:52 -0500
I've seen enough comments about the signed status being broken (like Scott's
post of yesterday), that I'll continue to shy away from macro security until
they fix it. Which is why my installer sets it to low. So, I've had no
complaints from 2003 users. For now, having macro security set to low is
the only way to be sure that the user doesn't get prompts and false alarms.
There is even more that they fail to tell you about getting a certificate
though....i.e., they "recommend" that you spend even more money to sign up
with Dunn & Bradstreet. And if you don't, odds are you won't get a
certificate or it will be for you as an individual only. Even if you do
sign up with D & B, you're not guaranteed to get a company cert. And then
guess who is liable? You, not your company. It really is a crock.
You might be right about the query issues, but I haven't verified it myself.
It should be easy enough to test the conditions you cited, even with a
selfcert certificate.
-- Paul Overway Logico Solutions http://www.logico-solutions.com "TC" <aatcbbtccctc@yahoo.com> wrote in message news:1106884592.973275.214680@f14g2000cwb.googlegroups.com... > True enough. But certificates can also stop working & the prompts > reappear. > > For example I *think* that modifying a query (programatically) will > break the signed status. (Can you confirm one way or the other?) > > I've also wondered whether *compiling* a query (ie. when it is run the > first time after creating or modifying it) would also do that. Yes? No? > > TC > > > Paul Overway wrote: >> Scripting may also cause prompts...from AV software. >> >> -- >> Paul Overway >> Logico Solutions >> http://www.logico-solutions.com >> >> >> "TC" <aatcbbtccctc@yahoo.com> wrote in message >> news:1106800249.620385.214820@z14g2000cwz.googlegroups.com... >> > Paul Overway wrote: >> > >> >> You need to sign your application with a digital certificate or > set >> > macro >> >> security to low. >> > >> > >> > Why does everyone keep saying this? >> > >> > By far the easiest way is to start the database via a script file > which >> > sets the macro security level to low for that single invocation of >> > Access. This does not require a certificate, or a registry change, > and >> > it does not affect any other database(s) - just the one being > started >> > by that script. >> > >> > Eg. in VBScript: >> > >> > dim o >> > set o=createobject ("Access.Application") >> > o.automationsecurity=1 ' set macro security LOW. >> > o.opencurrentdatabase "full path to your database" >> > o.usercontrol=true >> > set o=nothing >> > >> > I've never packaged a system with the Access Runtime, but surely it >> > should be possible to set it to start the system by running a > script? >> > HTH, >> > TC >> > >
- Next message: Pattyt: "Parameter Message in a split DB"
- Previous message: Colin Nash [MVP]: "Re: Perhaps the most OBVIOUS question you will ever see."
- In reply to: TC: "Re: Bypass Security Warnings in Access Runtime"
- Next in thread: TC: "Re: Bypass Security Warnings in Access Runtime"
- Reply: TC: "Re: Bypass Security Warnings in Access Runtime"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|