CLARIFICATION OF 5.7 ANNUAL SUBSCRIPTIONS

[Chris Rendall]

If I'm understanding this correctly, if someone doesn't upgrade until version 5.7.08 is out and they don't want to use the annual subscription model they will get out-dated code in version 5.7?  I think when someone decides to purchase filePro and they don't choose the subscription model they should still get the latest version with all the bug fixes.  

I've seen it mentioned many times on the filePro mailing list if someone is having a problem and is using an older version of filePro 5.6 to install the latest version of 5.6 to fix it.  With this new subscription model you are saying either sign up for the subscription model or wait for the next major release to get the bug fixes.

On Jul 28, 2011, at 4:27 PM, FpTech Sales wrote:

> Some of you have had questions as to how the 5.7.00 annual subscription works, so I will try to explain and clarify any issues you might have.  This email will also let you see what will be in 5.7.01 and as we develop more request, you will be advised what is being worked on and available for release.
> 
> ANNUAL SUBSCRIPTION CLARIFICATION
> 
> When you upgrade or purchase the NEW 5.7.00 product you will have the option to purchase an annual subscription. This will entitle you to ALL of the NEW features and fixes as they are completed and released and not required to wait for the next major release (5.8.00).
> 
> Example: Customer A purchases 5.7.00 and is given the option to purchasse the annual subscription for 20% of the total list price of the invoice.  He decides to purchase the annual subscription and will be entitled to download ALL the releases during the term of the subscription; therefore, as release become available for download, he simply downloads the product ( example 5.7.08) and starts using the feature(s) available in 
> ALL the releases from 5.7.00 to 5.7.08.  
> 
> Customer B decides that he would like to upgrade to 5.7 from 5.0.09.  He has to pay 65% of the total list price to upgrade to 5.7.00.  He is also given the option to purchase the annual subscription.  He declines.  He is entitled to download ONLY 5.7.00 (WHICH IS THE STARTING POINT OF ALL NEW OR UPDATED PURCHASES).  He does not start at 5.7.08 since he would get all the features from 5.7.00 to 5.7.08 which is not fair to those who have purchased the annual subscription starting at 5.7.00; therefore, ALL upgrades or new purchases will start at 5.7.00.  If he see a feature he desires, he can purchase the annual subscription at that time and is entitled to all features from 5.7.00 to the current release.  If he wishes NOT to purchase an annual subscription he will have to wait until 5.8.00 is release at which time he will need to pay the upgrade cost at that time.
> 
> =========================================================
> New 5.7.01 Feature
> =========================================================
> This contains the encrypting ddefine and dclerk. (If you attempt to use an encrypted file with an older filePro 
> program, you will get a "no or invalid map" error.)
> 
> Note: these binaries are "5.7.01", and as such will need a 5.7.01 or later license in order to run.
> 
> In ddefine, there is a new "O-Options" available when not in update mode. This will allow you to change the creation password as well as an encryption 
> key.  If you put a "Y" into the field next to the "change creation password" or "change encryption key" prompt, you will be taken to the entry field next 
> to it:
> 
> ┌───────────────── File Options ────────────────────┐
> │                                                   │
> │    Change creation password:  ◄  **************◄  │
> │       Change encryption key:  ◄  **************◄  │
> │                                                   │
> └──────────Press  ESC  To Record,  Ctrl-C  To Cancel┘
> 
> Note that, if the file already has an encryption key, you will be asked for it before being allowed to change it.  Currently, it doesn't actually verify that you gave the correct key.
> 
> When you exit, the file will be encrypted with the key specified, or be decrypted entirely if left blank.
> 
> The accompanying dclerk appears to transparently read and update the encrypted records without any issue.
>