Creating a Digital Signature

I have created an Access 2013 database that I wish to send to a client.  They do not have Access on their test PC, meaning that I need to create a runtime licence, which is fine.  However, it now says that I need to "Sign" the package.  I've never done this before, so could someone tell me a low-cost way to do this (properly).

Thank you.
Andy BrownDeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joe Winograd, Fellow&MVEDeveloperCommented:
Hi Andy,

I use a Symantec (previously, VeriSign) code signing certificate for all of my programs that I distribute (it is reasonably priced — less that $100 per year). I've never used a certificate related to MS Office, but I noticed at their website that they offer one:

I don't know if this is what you need for your MS Access database, but it's worth a look. Btw, the Symantec/VeriSign support folks have been very helpful, and they are experts in digital signing certificates, so they'll probably know straightaway what's needed for your situation. Regards, Joe
You don't need to sign the app.  The user will get the security message the first time they open it and if they make it a trusted document, they won't be bothered again.

You might want to look into using SageKey to create the install package.  The product is not cheap and it requires a different license for each version of Access (which I object to on principle) but it does create smooth installs and it does handle the trusted folder issue.
Andy BrownDeveloperAuthor Commented:
Thank you Joe - I'll take a look at that.

Pat - Thanks also, but I can't see a way of saving it without Signing it.  The old versions let you, but on 2013, it definitely wants something.  Also, I've used SageKey before on a 2003 database and it worked really well, so I may look at that.  But it does seem a little overkill for this project.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

That option is used when you are using the Office packaging wizard which is not as good as the SageKey option.
Andy BrownDeveloperAuthor Commented:
Hi Pat - I agree, but I can't see anywhere of packaging it without a key.
The packaging wizard isn't doing anything particularly useful for you.  I don't use it - ever.  I either use the SageKey tool or nothing.  When I use "nothing", I:
1. compile the app as an .accde (make sure you keep the original .accdb in a safe place and back it up.  I always zip it)
2. rename the .accde to .accdr - this tells the database engine to pretend to be the runtime even if it isn't.
3. find a link to the Access runtime engine for the version you want your users to install.  I would send them the link rather than worrying about keeping my version of the download current.
4. zip the .accdr and send it to the user.
5. create instructions for the user to install the runtime engine (he only has to do this once) and then for unzipping the FE.  Don't forget to include how to relink.

You didn't say whether this distribution was for in-house use or for people who are not on your local network.  I occasionally create applications that are sold to the public.  Those I ALWAYS distribute with SageKey.  For apps I create for clients to distribute internally, I NEVER use a packaging tool.  I/the network adman handle the runtime install as a separate step.  Then I place the FE in a shared network folder and send the user a shortcut to place on their desktop.  The shortcut runs a batch file and the batch file creates a local directory (if necessary) and copies down a new version of the app and then opens it.  So, every time the user starts the app by clicking on the shortcut, he actually gets a fresh copy of the FE.  We don't have to worry about relinking since I use the UNC path to link to the BE so it doesn't matter how individual users have drives mapped.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andy BrownDeveloperAuthor Commented:
Thank you both for your help on this.  In the end, I simply purchased the latest version of Sagekey, which did the trick perfectly.

All the best.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.