Peter's Software
Helping you create better Microsoft Access applications


Home

General info

Where to buy

Mailing List

Contact


Links


KeyedAccess FAQ (Frequently Asked Questions)

Table of Contents

    General

  1. Will KeyedAccess work with Access 2010 64-bit?


  2. Will KeyedAccess work with Access 2013/2016 32-bit?


  3. Will KeyedAccess work with Access 2013/2016 64-bit?


  4. Can I see an example of KeyedAccess implemented in an application?


  5. Can KeyedAccess shut down an application after a certain period of time and prompt for an Unlock Code?


  6. Does a help file come with KeyedAccess?


  7. With KeyedAccess implemented in my application, what additional file(s) do I need to distribute to the end-user?


  8. What additional registry keys need to be created by my installation procedure when I am using KeyedAccess?


  9. Does KeyedAccess have a setting to allow a program to be installed on multiple computers with the same key?


  10. Installation

  11. Can I install KeyedAccess on multiple computers?


  12. How can I delete the KeyedAccess-created registry keys when my application is un-installed?


  13. Usage

  14. Can I diasable only some features of the product during the trial period?


  15. Errors

  16. I'm getting an 'Error in ka_GetComputerSerialNumber (2), ...: 9 - Subscript out of range'.


  17. I'm getting an error 2950 when I open the KeyedAccess Generator application.


  18. I'm getting an 'Error occurred when attempting to add reference to C:\Documents and Settings\All Users\Application Data\Peter's Software\KeyedAccess\v4\ka.mde. 29060 - File not found.' and I'm using Access 2010.


Answers

  1. Will KeyedAccess work with Access 2010 64-bit?

    Upon initial installation, KeyedAccess will not work with Access 2010 64-bit, but we have a patch available for free by request that will enable Access 2010 64-bit support. Just send us an e-mail request for the patch after you purchase KeyedAccess and we'll send it to you.
    [Back to the top]
     
  2. Will KeyedAccess work with Access 2013/2016 32-bit?

    The KeyedAccess Generator data file "kagendatau.mdb" is an Access 97 database file which is not supported by Access 2013/2016. Once this file is converted to Access 2000 or 2002 format, then the KeyedAccess Generator will work just fine with Access 2013/2016 32-bit. Let us know via e-mail if you need assistance converting the "kagendatau.mdb" file to a more recent Access file format.

    The generated basKeyedAccess module that is inserted into your application front-end is compatible with all 32-bit Access versions 97 through 2016 (and after applying the 64-bit patch, with Access 2010 64-bit and Access 2013/2016 64-bit as well).
    [Back to the top]
     

  3. Will KeyedAccess work with Access 2013/2016 64-bit?

    Upon initial installation, KeyedAccess will not work with Access 2013/2016 64-bit, but we have a patch available for free by request that will enable Access 2013/2016 64-bit support. Just send us an e-mail request for the patch after you purchase KeyedAccess and we'll send it to you.

    Also, the KeyedAccess Generator data file "kagendatau.mdb" is an Access 97 database file which is not supported by Access 2013/2016. Once this file is converted to Access 2000 or 2002 format, and the patch described above is applied, then the KeyedAccess Generator and the generated basKeyedAccess module will work just fine with Access 2010 and 2013/2016 32 and 64-bit. Let us know via e-mail if you need assistance converting the "kagendatau.mdb" file to a more recent Access file format.
    [Back to the top]
     

  4. Can I see an example of KeyedAccess implemented in an application?

    Yes, the demo version of KeyedAccess comes with a sample application for Access 2000, 2002, and 2003 (and one for Access 97). To start it, click Start > Programs > KeyedAccess v3 demo > Sample Access 2000, 2002, 2003 Application
    [Back to the top]
     
  5. Can KeyedAccess shut down an application after a certain period of time and prompt for an Unlock Code?

    Yes. This functionality is available in version 3.0 and later KeyedAccess versions.
    [Back to the top]
     
  6. Does a help file come with KeyedAccess?

    Yes. You can open it by pressing F1 from any form in the KeyedAccess Generator, or by clicking Start > Programs > KeyedAccess . . . > KeyedAccess Help.
    [Back to the top]
     
  7. With KeyedAccess implemented in my application, what additional file(s) do I need to distribute to the end-user?

    None. Once you've implemented the basKeyedAccess module and KeyedAccess calling code in your application database .mde file, you distribute it just like you would any other Access application. No additional files need to be included in your application installation setup.
    [Back to the top]
     
  8. What additional registry keys need to be created by my installation procedure when I am using KeyedAccess?

    None. KeyedAccess creates its own set of registry keys when the application is first opened on the end-user's computer.
    [Back to the top]
     
  9. Does KeyedAccess have a setting to allow a program to be installed on multiple computers with the same key?

    Yes, KeyedAccess includes a "16-digit Reg ID/Product Key" mode where registration keys can be used on any number of computers. This is similar to the key that you get on a Microsoft Windows CD.

    KeyedAccess also functions in "Installation Serial Number and Unlock Code" mode where a key is specific to a computer. In this mode, the same key CANNOT be used on multiple computers.

    More information is included in the help file.
    [Back to the top]
     
  10. Can I install KeyedAccess on multiple computers?

    Yes, by the license you can do so within your own company. If you install KeyedAccess on different computers and wish to generate Unlock Codes for your application from each, you will need to make sure that the same KACP.txt file and KAGenDataU.mdb backend db are used at both locations. This will probably mean accessing the KAGenDataU.mdb file from a shared network folder, or copying the two files from the original computer to the other computers after installing, and after first generating a basKeyedAccess module on the original computer. The files should be copied to the KeyedAccess install folder, which is likely (Windows XP): "C:\Documents and Settings\All Users\Application Data\Peters Software\KeyedAccess\v4" or (Vista/7): "C:\ProgramData\Peters Software\KeyedAccess\v4".
    [Back to the top]
     
  11. How can I delete the KeyedAccess-created registry keys when my application is un-installed?

    Well, the registry keys that KeyedAccess creates are a record of your application's activity on that computer. Removing them would mean that the application could be installed again and perhaps a trial period or registration period could be re-started. That's one of the things that KeyedAccess guards against, and the registry keys are part of this protection.

    If you don't want that level of protection, you can un-check the "use bulletproofing" check box, and delete the key specified on the KeyedAccess generator Applications form next to "User Computer Registry Key for Unlock Code/Reg ID" on uninstall.

    For more information, please see the KeyedAccess help file under Getting Started > Uninstalling.
    [Back to the top]
     

  12. Can I diasable only some features of the product during the trial period?

    Yes. To disable some features of your product during the trial period, some special code needs to be added to the KeyedAccess calling code.

    Near the bottom of your KeyedAccess calling code block (when setup for a trial period) you should see some code that looks like this:
     ....
        Else
            ka_ValidateKeyWithPrompt True, 3  
            ka_ValidateKeyWithPrompt True, 4  
            If ka_ValidateKeyWithPrompt(True, 2) Then     
                'gblnRegistered = True
            Else
                If ka_IsGateActive(4) Then
                    MsgBox "This program is not registered. Click OK to exit."
                    Application.Quit
                Else
                    'gblnRegistered = True    <=====
                End If
            End If
        End If
    Else
        MsgBox "This program is not registered. Click OK to exit."
        Application.Quit
    End If
    The logic will flow to the place I ve marked above with an arrow when the trial period is active.

    So if you create a global variable, say

     Public gblnTrialPeriodActive as Boolean


    Then you can set the value in the code like so:
     gblnTrialPeriodActive = False     <=====
    
    ....
    
        Else
            ka_ValidateKeyWithPrompt True, 3  
            ka_ValidateKeyWithPrompt True, 4  
            If ka_ValidateKeyWithPrompt(True, 2) Then   
                'gblnRegistered = True
            Else
                If ka_IsGateActive(4) Then
                    MsgBox "This program is not registered. Click OK to exit."
                    Application.Quit
                Else
                    'gblnRegistered = True
                    gblnTrialPeriodActive = True     <=====
                End If
            End If
        End If
    Else
        MsgBox "This program is not registered. Click OK to exit."
        Application.Quit
    End If
    You can then test the value of gblnTrialPeriodActive elsewhere in your application and use it to inhibit functionality during the trial period.
    [Back to the top]
     
  13. I'm getting an 'Error in ka_GetComputerSerialNumber (2), ...: 9 - Subscript out of range'.

    It's possible that the error you received may occur when the basKeyedAccess module and your KeyedAccess calling code are out of sync.

    Did you re-generate the basKeyedAccess module and import it into your database? Did you re-import the code that calls KeyedAccess? If you left out one of these steps, then the error you describe may occur.

    The error may also occur if you did not specify a trial period expiration warning in the KeyedAccess setup wizard. This causes a line of calling code to be generated with a 0 as the final parm (Gate No). This is a bug that will be fixed in the next release. To resolve this issue, you can either specify a trial period expiration warning using the setup wizard, or comment out the following line of code in the generated KeyedAccess calling code:

    ka_ValidateKeyWithPrompt True, 0

    [Back to the top]
     
  14. I'm getting an error 2950 when I open the KeyedAccess Generator application.

    Please see http://support.microsoft.com/kb/931407
    [Back to the top]
     
  15. I'm getting an 'Error occurred when attempting to add reference to C:\Documents and Settings\All Users\Application Data\Peter's Software\KeyedAccess\v4\ka.mde. 29060 - File not found.' and I'm using Access 2010.

    For version 4.2 of the KeyedAccess Generator to be compatible with Access 2010, there is a change that needs to be made in the ng_AutoExec routine in the basAutoexec module. Please replace the lines of code below

    Select Case xg_WhichVersionOfAccess(False)
        Case 97
            strAccRefVer = "97"
        Case 2000 To 3000
            strAccRefVer = "2000"
        Case Else
        End Select

    ... With the following lines of code:

    Select Case xg_WhichVersionOfAccess(False)
        Case 97
            strAccRefVer = "97"
        Case Else
            strAccRefVer = "2000"
        End Select

    [Back to the top]
     

Ask a Question about KeyedAccess

Back to KeyedAccess Page

 

 

 

Copyright 1998-2003 Peter's Software