J
jovobas
The new security handling of access 2007 is really suffocating.
I had created a database to deploy among many users (+100). Because of
ongoing development of the front-end, I had built in an auto update
feature.
Basically, the user opens his front-end. The first form (automatically
opened) checks if version numbers match. If not the front-end imports
all queries, forms and reports from a root file on a local server.
Acces 2003: no problems with security: a pop-up warns the users that
macro's are coming, he clicks yes and the first form opens and an auto
update is triggered.
Acces 2007: big problems with security: the yellow security bar
appears. The users chooses to allow all content. Alas, the on open
event of the first form is skipped, so no auto update.
Access 2007 handles these events different, so in order to let the
same front-end work, every single user would need to lower the
security settings to the lowest (allowing all macro's). This is not a
good idea.
So in the mean while, we're exploring digital signatures. Being
successful in installing and trusting my signature for all users, the
problems seemed to solved.
The user can open his front end without warning (because the scripts
are signed), but this triggers the auto update. Thus importing new
forms and reports. So Access acts immediately on this security breach
by revoking the signature. And we're back at square one.
It doesn't matter whether the new forms and reports have macro's or
not, or whether they are signed with the same signature or not. Access
revokes the signature, rendering the application useless (again).
Is it really asking too much? Is Access really not capable of meeting
these development requirements?
Anyway, if no elegant solution can be found, i will be forced to
transform to a web interface.
I had created a database to deploy among many users (+100). Because of
ongoing development of the front-end, I had built in an auto update
feature.
Basically, the user opens his front-end. The first form (automatically
opened) checks if version numbers match. If not the front-end imports
all queries, forms and reports from a root file on a local server.
Acces 2003: no problems with security: a pop-up warns the users that
macro's are coming, he clicks yes and the first form opens and an auto
update is triggered.
Acces 2007: big problems with security: the yellow security bar
appears. The users chooses to allow all content. Alas, the on open
event of the first form is skipped, so no auto update.
Access 2007 handles these events different, so in order to let the
same front-end work, every single user would need to lower the
security settings to the lowest (allowing all macro's). This is not a
good idea.
So in the mean while, we're exploring digital signatures. Being
successful in installing and trusting my signature for all users, the
problems seemed to solved.
The user can open his front end without warning (because the scripts
are signed), but this triggers the auto update. Thus importing new
forms and reports. So Access acts immediately on this security breach
by revoking the signature. And we're back at square one.
It doesn't matter whether the new forms and reports have macro's or
not, or whether they are signed with the same signature or not. Access
revokes the signature, rendering the application useless (again).
Is it really asking too much? Is Access really not capable of meeting
these development requirements?
Anyway, if no elegant solution can be found, i will be forced to
transform to a web interface.