[AccessD] Project is unviewable

It is not worth the hassle of self-signing certificates as there are 
authority and permission problems
installing them properly into the digital signature cache under Win XP 
with any another user.
Network Admins will hunt you down with pitchforks and burning torches.
You should use the internet authority verifiable certificates from 
Veritas or Thwaite etc.
Of course then you have to pay, get a DUNS number etc.
I don't even know if SageKey handles their installation.

I got self certs to work a couple of years ago with makecert  with a lot 
of fiddling
but I think there have been OS security changes since then.



John Colby wrote:

>Never mind.  There is something about pressing the send key that magically
>makes workarounds work.  Actually it appears that I had to hold down the
>shift key as I was opening the aforementioned database to do this stuff.  It
>MAY have something to do with the fact that when I do that I am not looking
>at my framework code when I perform this "unlocking" rigamerole hooey. 
>
>At any rate, I have my code back and will NOT attempt to sign my databases
>anymore, as it appears to hose them if signed in 2003 and opened in XP?  Or
>not.  Who can really say what causes anything anymore?
>
>John W. Colby
>www.ColbyConsulting.com 
>
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
>Sent: Friday, April 21, 2006 3:37 PM
>To: 'Access Developers discussion and problem solving'
>Subject: [AccessD] Project is unviewable
>
>Has anyone ever gotten this?
>
>I was trying to get rid of the 2003 crap that forces you to answer THREE
>questions correctly before it allows you to open an Access database.  In the
>process I created a digital signature and applied it to the database.  Not
>sure exactly what went wrong but now "the project is unviewable" which means
>NO CODE CAN BE SEEN!!!
>
>I googled the error message and is appears (though not directly stated) that
>this is a known bug with a workaround... which doesn't work around it.
>
>Has anyone ever successfully recovered your code from this specific piece of
>hell that MS is subjecting me to?
>
>John W. Colby
>www.ColbyConsulting.com 
>
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada