[AccessD] database is not digitally signed

Just remember on a network, the digital signature cache can be
locked down for general users.

Gustav Brock wrote:

>Hi Francisco
>
>I haven't followed the thread but if you wish to digitally sign your A2003 code, here is how:
>
>http://msdn2.microsoft.com/en-us/library/aa167281(office.11).aspx
>
>If selfcertification is not enough, you can obtain a free certificate here at CAcert:
>
>http://www.cacert.org/
>
>/gustav
>
>  
>
>>>>fhtapia at gmail.com 01-02-2007 21:10:04 >>>
>>>>        
>>>>
>Hi John,
>   Thanks for replying... In fact I created an ADE from the ADP, and
>packaged that via sagekey+wise (there is only one version on their
>site, I just checked today).  What I had not anticipated was that my
>install changed the default behavior for the full version of
>access2003, not only the runtime version.
>
>I started searching for the keywords in google for the problem but I
>wasn't getting a solution, just simply that Access required a
>digitally signed certificate for the app, since I didn't know what had
>happend, I kinda went into a panic and started trying to query google
>w/ every keyword combination I could think of, :).  I gave up and
>decided to search my gmail to find out if anyone had posted something
>in the last 2 years, and i was amazed that it didn't show up in my
>results :).  So I posted it :)
>
>
>
>On 1/31/07, John Bartow <john at winhaven.net> wrote:
>  
>
>>Hi Francisco!
>>Long time no hear. I haven't had that issue. Are you using the icons the
>>install places or opening Access and then the application? As far as I
>>understand SageKey's scripts will eliminate that problem but you do have to
>>let it do its thing.
>>
>>SageKey does post updates every now and again and they have a FAQ section on
>>their website.
>>
>>In order to test this I just turned macro security to high with my Access
>>2003 full version. I installed an application which uses Wise/SageKey to
>>install Access 2003 runtime and shortcuts. I started the application and it
>>did not give me the error message. I then opened the same access app's file
>>but by opening (Access full version) and then selecting the file. this gave
>>me the error concerning the security setting.
>>
>>So I'm guessing that your opening it via full Access or your shortcut icon
>>is not referencing the runtime version of access that SageKey installs.
>>
>>If you want, I can help troubleshoot you through the install script. Contact
>>me off list.
>>
>>HTH
>>John B.
>>
>>-----Original Message-----
>>From: accessd-bounces at databaseadvisors.com 
>>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia
>>Sent: Wednesday, January 31, 2007 6:49 PM
>>To: Access Developers discussion and problem solving
>>Subject: [AccessD] database is not digitally signed
>>
>>I used sagekey to install a demo copy of my own db for my end users, version
>>Access2003, I had been using the 2000 for years now w/o any problems.
>>
>>Now the error that I am seeing is described here
>>http://office.microsoft.com/en-us/access/HA011225981033.aspx#080 
>>
>>"Access cannot open the file due to security restrictions. Security settings
>>restrict access to the file because it is not digitally signed"
>>
>>but what it does NOT tell you is how to set the macro security level to low
>>so that I CAN open the projects I was opening before I did the wise install
>>(sagekey) install.  I called Sagekey and the guy there was stunned and asked
>>me to re-install Access 2003... but that of course has not fixed anything...
>>:(
>>    
>>
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada