SageKey Update FE options

[ions]

Access Expert,

I am going to use SageKey along with Access Runtime to create a robust installation package. From my reading about SageKey I don't see an efficient solution for automatically updating the FE.

I use peterssoftware's free Application Starter for Updating my FEs.


http://www.peterssoftware.com/aps.htm

Can I incorporate something like this with SageKey? Basically what his free Application starter does is instead of opening the Application FE the user always runs his Update.mdb which checks the server for an Updated FE and if it exists copies it to the local machine and then launches the Application FE. Can I do something like this with SageKey? If not can I use peterssoftware solution with SageKey?

Thank you

 

[gemma-the-husky]

how does sage key work?

ideally you want something stored in the backend or in the registry - and your front end only needs to verify that whatever is already stored on the client machine is correct - then you can issue a new front end without having to relicense it.

i actually put a FAQ up the other day about a general technique for licensing.

http://www.access-programmers.co.uk/forums/showthread.php?t=245919

 

[ions]

Hi Husky,

Thanks for your response. I am not too concerned with licensing right now, perhaps down the road. Right now I am only concerned about developing the most effective update FE strategy with SageKey. From my reading most people either email the new FE update to their clients, or provide a download link. I can do that but my clients are accustomed to automatic FE updates which don't require any user intervention.

I did read at at the SageKey website that automatic updates are possible but not built into the product. I am trying to understand how to do this with SageKey.

http://www.sagekey.com/support_forum.aspx?g=posts&t=714

 

[gemma-the-husky]

personally, i think a database is not installable in quite the same way that a .exe application is.

it probably won't be distributed in large numbers, and it is not unreasonable to expect users to be able to contribute something towards the installation. i think it is not too unreasonable to send a new dbs to your users, and ask them to place it in the appropriate folder.

 

[ions]

i think it is not too unreasonable to send a new dbs to your users, and ask them to place it in the appropriate folder.

Interesting. Even for a commercial application?

Thanks Gemma.

 

[gemma-the-husky]

maybe i am wrong, but i just i feel a commercial app based on access is a little bit different to a standalone "exe" and needs more sensitive handling.

i think it is more likely to be "developer-installed" rather than supplied "shrink-wrapped" unless it is marketed as a single-user app.

 

[ions]

Hi Gemma,

My commercial app is a single user app. It's a reporting and analysis tool.

However, for customized ERP systems I use http://www.peterssoftware.com/aps.htm

Ideally I would like to implement the same kind of FE Update with Sagekey but I am not certain it's possible. As I think about it, an email with a download link can also work.

 

[NigelShaw]

Hi

I use sagekey and have done for quite some time. If you are updating a front end, why is there an issue? Sagekey will be in the front end thus be replaced with the new front end. I take use of this by changing option codes for major updates. The option codes are part of the licencing so if a user purchased V1 and the installed V2, the licence wouldnt work.

in your case, i would call Peters updater from my own front end making sure that the end user ran MY FE. you can call the functions, routines etc from another db from yours.

That si what i would do. If Sagekey refer to any specific updating, my guess is that they are referring to updating their module within your application. There isnt a way of updating sagekey modules automatically. you would have to update your source and then redistribute.

thanks


nigel

 

[JohnPapa]

I have been using Sagekey for the past 15 years (Access 97 & Access 2003) and has worked well over the years. A few hicups, which were overcome. Just to give you an example, Sagekey will not proceed with the .exe creation if Unicode language is not US English!!!

Regarding the FE mde replacement, I would agree with GTH. I simply replace the old mde.

Even though I am happy with Sagekey, I reccently installed Access 2013 and I have been looking to see if there are any other options for deployment of the 2013 Runtime when it comes out in a few months. I will look at Peterssoftware you mention and I also run into Inno software.

John