Access 2010 and Sagekey
Bob Darlington
I've about given up with the Packaging and Deployment wizard that came with
the program.
I think MS support have given it up too.
--
Bob Darlington
Brisbane
Albert D. Kallal
news:4d464e37$0$22474$afc3...@news.optusnet.com.au...
>Has anyone used the Access 2010 Sagekey software?
>I've about given up with the Packaging and Deployment wizard that came with
>the program.
>I think MS support have given it up too.
Have you read my article here:
http://www.kallal.ca/RunTime/Index.html
In the above I suggest using a free installer. I been using Inno for about
7+ years now. It is free, and really, a update + install of your software
really amounts to a simple file copy of your front end and back end to the
users computer. In fact, before Inno, I was using a paid version of WinZip
that produced a .exe extractable file.
In fact, what is even better is the a2010 runtime is likely the first
runtime since access 97 in which you don't have to bother with trusted
locations or all of the macro security stuff. The new security model simply
prompts you the FIRST time if you want to run the content, and once you done
this, then no more nag prompts. Really VERY nice. What this means is you can
simply install the runtime on the target computer, and after that, any file
simple copied to the target computer can be clicked on, and it will run.
The major advantages of using Sagekey over that of something like Inno is
that SageKey installs do not interfere with existing (different) versions of
access on the target computer.
You can read my above article, but in in a nutshell, installing the runtime
or full edition is much the same, and even the issues of different versions
of access being installed is ALSO compatible in terms of the EXACT same
problems exist if you install full edition, or runtime edition on machines
that already have access installed. As noted, the only exception to this is
to use Sagekey.
However, in terms of macro security, trusted locations, the a2010 runtime is
a real breath of fresh air compared to the last 3 or 4 versions of the
runtime in which you had to setup reg keys and trusted locations etc. For
a2010, you don't have to do this anymore.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenos...@msn.com
buckskin
"Bob Darlington" <b...@notheredpcman.com.au> wrote in message
news:4d464e37$0$22474$afc3...@news.optusnet.com.au...
I'm using Sagekey Access 2000 runtime wizard and it works more or less
painlessly for me and makes deploying very easy.
Bob Darlington
"buckskin" <buck...@mailinator.com> wrote in message
news:8qnnfc...@mid.individual.net...
--
Did you mean Access 2010? That is my problem at the moment.
Bob Darlington
Brisbane
buckskin
No, Access 2000, I can only attest to that version. I've got no reason to
suppose the other versions aren't as robust.
Bob Darlington
There have been a few versions since 2000, in both Access and Sagekey, so
I'm reluctant to accept that there are no problems on the basis of 2000
experience.
But some might call me a cynic :-)
--
Bob Darlington
Brisbane
"buckskin" <buck...@mailinator.com> wrote in message
news:8qp1th...@mid.individual.net...