Re: Avoid Security Warning
- From: Cron <cronoklee@xxxxxxxxxxx>
- Date: Tue, 7 Oct 2008 17:39:12 -0700 (PDT)
On Oct 8, 1:20 am, "Chris O'C via AccessMonster.com" <u29189@uwe>
wrote:
Several flaws in your logic. The vba won't run because the college students
at those hundreds of workstations don't have the smarts to enable the content
by pressing a bar that pretty much says "contents disabled unless you press
here". You don't want to go to those hundreds of workstations yourself to do
it while each user is logged in. (The trusted locations are per user, not
per workstation, so unless the network is set up with roaming profiles - kind
of doubtful - you have a lot more work than you thought if students are
allowed to use more than 1 pc when using your app during the semester.) The
user who's executing the vba code needs to have enough permissions to write
to the registry. Most college networks are locked down so student users
don't usually have those permissions.
True, but if it was just a once off, I could tell the students to
click the enable content button. It just can't appear every time the
database is opened. You might be right about the registry edits being
disabled altho the settings do allow the change through access so I've
a feeling the security won't be smart enough to distinguish VBA from
access.
What kind of digital signature are you using that needs to be packaged to be
installed on each pc? You can't sign the files on one pc with your digital
certificate and copy the front end to each user's desktop and copy the back
end to the network server?
I'm not sure if that was a question but I tried this quickly on my
home network and it didnt work but I might have missed something. Is
the following possible...
Create a digital signiture using office.
Sign and package the database with it in access.
Unpack the signed package to a new computer and run as digitally
signed without problems??
Cheers,
Ciarán
.
- Follow-Ups:
- Re: Avoid Security Warning
- From: Tony Toews [MVP]
- Re: Avoid Security Warning
- From: Chris O'C via AccessMonster.com
- Re: Avoid Security Warning
- From: Chris O'C via AccessMonster.com
- Re: Avoid Security Warning
- References:
- Avoid Security Warning
- From: Cron
- Re: Avoid Security Warning
- From: Rick Brandt
- Re: Avoid Security Warning
- From: Cron
- Re: Avoid Security Warning
- From: paii, Ron
- Re: Avoid Security Warning
- From: Cron
- Re: Avoid Security Warning
- From: paii, Ron
- Re: Avoid Security Warning
- From: Cron
- Re: Avoid Security Warning
- From: Chris O'C via AccessMonster.com
- Re: Avoid Security Warning
- From: Cron
- Re: Avoid Security Warning
- From: Chris O'C via AccessMonster.com
- Re: Avoid Security Warning
- From: Cron
- Re: Avoid Security Warning
- From: Chris O'C via AccessMonster.com
- Avoid Security Warning
- Prev by Date: Re: Avoid Security Warning
- Next by Date: Re: Avoid Security Warning
- Previous by thread: Re: Avoid Security Warning
- Next by thread: Re: Avoid Security Warning
- Index(es):
Loading