Make Access db trialware

[tuxalot]

Two phase question. I am looking for some guidance and not necessarily code. I want to learn how to create these functionalities in my db and the pros and cons of different approaches.

FIRST: I would like to distribute my db to a group of beta testers for feedback. The db should run for 30 days then expire with the option of entering a second key to continue the trial. Exeshield looks like a good solution for this but only works on executables.

SECOND: As requested functions are added or bugs squashed, I would like to have the DB check it's version on startup against a web version and prompt the user if/when a newer version exists and then allow it to be downloaded and the older version overwritten.

Thanks in advance for any assistance.

[jimatqsi]

For the versioning, I include a front-end (local to the user) data item with the version ID of the front-end. In the back-end (remote for your case) table I store the current version ID and the minimum version ID. I compare the versions at start-up. That allows me to force updates when needed.

In either case, but especially the first, what if web access is not available? I think you'll have to require web access for the demo to work or one could turn your demo into a permanent copy by blocking your site via a firewall.

Jim

[tuxalot]

Hi Jim. Thanks for the post. My back-end is local. The call to the website will be required to check versioning only. If the user has no web access, then the check would not occur.

For the trialware, something like keyedaccess would be great but the costs are high at $299 for the module. I would like to find a lesser expensive solution if it exists.

[neelsfer]

I use a very basic method and do not have version checking. If they then buy it, i will send an unlocked version with a 12 month date limit on.
I add a date text field to the startup form, and use something like this.

If Me.Datefield >= #2/2/2012# Then DoCmd.Quit

[Narender Sagar]

This is a very interested question, and I would like to see some more expert responses on this subject.
Jim: Can you please elaborate or put some more light on maintaining version in FE and BE.
Neelsfer: I would just like add a word to readers that, before putting above code in your database, a backup copy must be taken separately.

[jimatqsi]

Narender,
I have a local parameter table (tbl_Runtimeparameters) in the front end. In the backend there is a similar parameter table (tbl_GlobalRuntimeparameters).

In the local table I have a parameter for the version of the front end. I update this version before putting a new copy on the distribution volume. I also update the current version in the global parameter table and if there is a reason to force users to a minimum version I plug the minimum version into the global parameters also.

Here is some of the code that runs at startup. Note that the parameter tables are used for many purposes so the columns are generic, to indicate whether they hold date, text or numerics.

    Dim strVersion As String
 
    Dim rstRunTimeParameters As DAO.Recordset
    Dim rstGlobalRunTimeParameters As DAO.Recordset
    Dim strVersion As String
 
    Set rstRunTimeParameters = dbs.OpenRecordset("tbl_Runtimeparameters", dbOpenSnapshot)
    rstRunTimeParameters.FindFirst ("pt_Parameter='Version'")
 
    Set rstGlobalRunTimeParameters = dbs.OpenRecordset("tbl_GlobalRuntimeparameters", dbOpenSnapshot)
    rstRunTimeParameters.FindFirst ("pt_Parameter='Version'")
         ' require minimum version
    If rstGlobalRunTimeParameters!pt_ValueA2 > rstRunTimeParameters!pt_ValueA Then
        MsgBox "The minimum allowed version is " & rstGlobalRunTimeParameters!pt_ValueA2 & ". Please update"
        rstRunTimeParameters.Close
        rstGlobalRunTimeParameters.Close
        Application.Quit
    End If
      ' let them know they're not running current version
    If rstGlobalRunTimeParameters!pt_ValueA <> rstRunTimeParameters!pt_ValueA Then
        MsgBox "The current version is " & rstGlobalRunTimeParameters!pt_ValueA
    End If
 

Here's the code where I display the version in the title bar

    ' Displays the current company and user in the caption bar.
    If reg_strUserName <> "" Then
        cswSetStartupProperty "AppTitle", dbText, "Image Accounting Premier: " & rstComp!strCompanyName & " - User: " & reg_strUserName & "  Version " & strVersion
    Else
        cswSetStartupProperty "AppTitle", dbText, "Image Accounting Premier" & " " & strVersion
    End If
    Application.RefreshTitleBar
 

Jim

[Narender Sagar]

Thank you so much Jim,
I'll try it in my database, & will get back for further help.
kind regards,
Narender

[NeoPa]

Two questions in the original post and a hijack from Narender as well. What a mess. This should probably have been deleted as soon as started but as it wasn't, and some helpful answers have been posted, that is no longer appropriate I believe. As such I will simply lock it to further posting and suggest that if anyone has any further questions related to this, they do it properly with a new thread.