Troubleshooting - Miscellaneous

Commas In Currency

Q - All of my currency fields are showing commas instead of the decimal point. This means that a value like 200.00 is displayed as 200,00.

A - The latest Microsoft patches list that this error is caused when using the multithreaded libraries and the setlocale call. Until Microsoft corrects this, you can inhibit calling the setlocale function using the command line startup switch /dl.

To do this:

1. Right-click the CV11 icon on your Desktop. A popup will appear. Select Properties and then select the Shortcut Tab.


2. Add /d1 as the last command argument in the Target line of the shortcut path and pre-existing command arguments.


3. Click the Apply button to initialize your setting changes and then select OK to save and close the window.

You can now sign into Collect! as you normally do and your currency fields should display properly.

Branch Offices

Q - If we were to open another office in a different city, would multiple branches be able to access a single database?

A - Yes. You would want a fast communication link to optimize the access speed as well as maintain your local users performance levels.

On local area networks, transmission rates are on the order of between tens and thousands of megabytes per second. Contact your local phone company for details and pricing for data lines and routers. See Remote Access Topics in the Help pages.

Data Importing

Q - We want to know if there is any way to determine beforehand whether or not we are going to encounter any problems importing data from our current program to yours, and to what extent. Can you advise how we might make this determination?

A - Yes, there are 3 ways.

1. If you are extremely familiar with the data and what it should contain, go ahead and visually review the raw data file you are about to import and see if anomalies make themselves apparent; i.e. inconsistent formatting or garbage characters that need to be filtered.


2. Run the import into your demodb or into a Test Client in your masterdb to keep the files contained to a controlled area of your system that will allow easy deletion if the tagged list of accounts were to accidentally become untagged in the process of reviewing.


3. The Import process allows you to "preview" records on a one by one basis to see how the data looks. You can Cancel out of the import if you notice that a mapping error has occurred, then delete out the debtor records it inserted during the preview. If your map follows the Collect! file hierarchy, you will see Debtor main screen first, followed by the sub-records ( Cosigner, Attachment Transaction etc.) that can all be previewed record by record to assess accuracy of your map.

Interoffice Messaging

Q - What sort of capabilities are there in Collect! for sending and receiving messages inhouse.

A - If the nature of the communication is relative to a specific debtor or client, an Operator can use a Review Contact Events as the vehicle to send a message or request to another employee. After creating the Review contact with the Due Date being current or future dated, with or without a Time, they may free-form write their brief request or message into the Description line. The intended recipient will see it when they are in their WIP List.

If you have a lot to say you can select the folder icon in the attachment field of the Contact to create a new attachment for this contact event. If your office allows a blank "Scratch.txt" file to be stored somewhere as a blank, this can be incorporated into the file as a scratch pad for staff to converse back/forth about an account without having to meet face-to=face or take up time on an interoffice call.

The communication of this type retains audit trail on the debtor or client it pertains to in the Contact Tab, as the Review event will remain In Progress in the recipient's WIP List until they have Completed the Review event, removing it from their WIP. If your internal procedures require that all users input notes on a debtor or client file when they perform a task, the sender of the email will see the actioning of their request by the footprint of the sender in the Notes tab.

Also possible but advised with extreme caution, is if the intended recipient doesn't work a WIP List, but your site DOES utilize email through Collect!, the sender need only click the Email icon on the Debtor or Client of interest and REPLACE the recipient email address from the prefilled address (debtor or client) to the internal email address of the coworker. As you can imagine, the extreme caution is that the sender must exercise absolute attention to detail, remembering to clear and re-enter the recipient email address from what is on the screen (debtor or client) with the internal address of intent, OR the actual debtor or client will be who receives the message.

Lists Easily Navigated

Q - Is there an easy way to look at the detail/full screen contents of each item in a list?

A - Yes. Open the first item in the list and then use the double arrow keys pointing left and right under the OK button to advance to the next account in the list OR back up to the previous account viewed. As well, PageUp and PageDown on your keyboard will page you up and down the list while displaying the full screen. Ctrl+End will advance you to the last record in the list while Ctrl+Home will take you back to the first record in the list.

Hipaa Compliance

Q - Is Collect! HIPAA compliant?

A - Yes.

The HIPAA regulations are in place to keep the security of personal data related to the medical industry. Collect! has many features that can help the agency protect this information. You are completely in control of any information that you may wish to extract from the Collect! database. Therefore, you can absolutely meet any guidelines set out by HIPAA for electronic data exchange.

Collect! can restrict fields, notes, transactions and/or any data field from operators using access levels. This enables you to display a medical account only to operators with authority granted to view the data. Also, your IT staff has full control over what to export or import into the database.

The excerpts below are taken from http://www.integratedmodular.com/hipaasuggestionsandfacts.html

"No Specific Hardware or Software is Required for HIPAA Compliance. HIPAA compliance cannot be 'quick fixed' by a piece of software. Policies on patient privacy must be implemented institution wide. Software can only help an institution to become HIPAA compliant."

"To date, there is No Official HIPAA Conformance Statement. The best thing for an institution right now, is to enforce all JCAHO rules and regulations, review the HIPAA rules and regulations, then create your own policies to cover compliance and conformance."

"The term "HIPPA Compliant" can only refer to a company, institution, or hospital - NOT SOFTWARE. Software only helps in making those institutions compliant. Policies and enforcement must accompany the software."

In summary, HIPAA compliance must be understood in its entirety, beyond Collect!. You do have full control over what data goes in and out. And you have many tools to restrict user access to limit data from those who should not see it. Using these features, you can be HIPAA compliant with Collect!