• What is HRS Pro ?
• + Downloads
• + HRS Pro Support
• — HRS Pro FAQs
•   About HRS Pro
•   Installation
•   Importing
•   Using HRS Pro
•    Output
•   State Information
•   download settings
• + Mailing List
• Enterprise Version
• Version Notes
• Disclaimer

Frequently Asked Questions
Output

Why are there different file extensions of .HDE and .HRS for different States?

How can I securely send my .HRS file to a Non-Wagers State ?

Why can't I open my NAUPA file ?

How can I be sure tha NAUPA file is correct ?

Encryption Failed Error Message, This is a standard ASCII file.

Why are there different file extensions of .HDE and .HRS for different States ?

HRS Pro creates two different types of the NAUPA II files, the .HDE and the .HRS.
 The .HDE file is an enrypted secure file produced for Wagers Supported  States that have the ability to accept the encrypted files.
 The .HRS file is a standard text file for Non-Wagers States that do not have the ability to decrypt the files.
 HRS Pro knows which file extension should be assigned to each particular state.

How can I securely send my .HRS file to a Non-Wagers State ?

You may choose to utilize a program like WINZIP in which you can password protect the .HRS file.
 If you do this, do not send the password in the package with the CD or floppy.
 Contact the Non-Wagers state you are reporting to for a safe and effective password communication.

Why can't I open my NAUPA file ?

The purpose of an .HDE file is to securely lock the NAUPA file which could have Personal Identifying information in it.
The state you are reporting to has the ability to decrypt and load the file as necessary.

How can I be sure that NAUPA file is correct ?

Any report of property (detailed or summary) output is an exact representation of the data being submitted to the state.

Encryption Failed Error Message, This is a standard ASCII file.

If you see the message "This is a standard ASCII file", a .HRS file is created, but it is non-encrypted.
It is NOT adviseable to send a non-unencrypted file to the state.
If the installation was done without full Administrative rights, the files needed for encryption may need to be un-registered, then registered again manually into the workstations registry.
Please see the information in the Installation FAQ on how to check for ADMIN rights.
Please check this page ---> Encryption ReRegistration for more information on how to un-register and re-register the files.