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

  1. Does a help file come with KeyedAccess?


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


  3. Can I install KeyedAccess on multiple computers?


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


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


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


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


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


Answers

  1. 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]
     
  2. 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]
     
  3. 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 c:\Program Files\Peters Software\KeyedAccess.
    [Back to the top]
     
  4. Can KeyedAccess shut down an application after a certain period of time and prompt for an Unlock Code?

    Yes. This functionality has been implemented in version 3.0 of KeyedAccess.
    [Back to the top]
     
  5. 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]
     
  6. 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]
     
  7. 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]
     

  8. 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]
     

Ask a Question about KeyedAccess

Back to KeyedAccess Page

 

 

 

Copyright © 1998-2003 Peter's Software