- Activation
- Expiration
- Badge layout and print date
- Lost and stolen flags
Note: the data remains in the card record in the C-Cure database, but seems to be ignored when C-Cure displays person data. In a pinch, it can be accessed using ODBC.
Showing posts with label Tip. Show all posts
Showing posts with label Tip. Show all posts
Wednesday, October 31, 2007
Watch out when you delete Persons
Prior to version 9.0 of C-Cure, you could view and export pretty much all of the person/card data for deleted persons. With the database changes made in 9.0 (person and card data split to support multiple cards per person), fields associated with the card can no longer be viewed. This includes:
Note: the data remains in the card record in the C-Cure database, but seems to be ignored when C-Cure displays person data. In a pinch, it can be accessed using ODBC.
Note: the data remains in the card record in the C-Cure database, but seems to be ignored when C-Cure displays person data. In a pinch, it can be accessed using ODBC.
Friday, February 2, 2007
Panel Comm errors -> C-Cure crash
One goal for this blog is to help people learn from the experience of others. This tip is based on a recent painful incident at a high profile. The site was down for several hours event thought they have redundant servers that are functioning properly.
When C-Cure person records are edited, imported, or purged, the changes are downloaded to online panels. If a panel is online, but not communicating due to a hardware or line failure, C-Cure stores the changes for that panel in a download table so they can be sent when comm is restored.
Over time, these records can take up a lot of space in the database, and ultimately kill the driver. If you have a redundant system, the same database will exist on the backup system, so the failure will occur there as well. As far as I know, there is no clear indication of why the system won't work, and to recover, you need restore a backup of a good database or have SH TSG do some database magic.
Moral of story - communication failures should be dealt with immediately, and panels (or comm ports) should be set offline if the fault cannot be repaired promptly.
When C-Cure person records are edited, imported, or purged, the changes are downloaded to online panels. If a panel is online, but not communicating due to a hardware or line failure, C-Cure stores the changes for that panel in a download table so they can be sent when comm is restored.
Over time, these records can take up a lot of space in the database, and ultimately kill the driver. If you have a redundant system, the same database will exist on the backup system, so the failure will occur there as well. As far as I know, there is no clear indication of why the system won't work, and to recover, you need restore a backup of a good database or have SH TSG do some database magic.
Moral of story - communication failures should be dealt with immediately, and panels (or comm ports) should be set offline if the fault cannot be repaired promptly.
Wednesday, January 31, 2007
Problems with Copy/Paste from Excel into C-Cure
When you copy a cell in Excel, end of line characters (CRLF) are included at the end of the data. Beware if you paste into C-Cure or other applications.
A customer had about 100 entries to add to an enumerated list. The entries were in a spreadsheet so he did a copy from Excel and paste into the Personnel\Configuration screen for the enumerated field. Then he created a template and attempted to import data into the field.
All records were rejected saying the enumerated values were unknown. When we manually selected a value from the pull-down, then exported the records, we say a line break. Unfortunately, it took a few hours of investigation before this was tried.
By editing the value on the configuration screen, we saw that you could hit delete then re-add the last character and the invisible characters at the end were removed and the import worked.
I have seem similar things happen when copying and pasting in Sql Server grids. Beware.
A customer had about 100 entries to add to an enumerated list. The entries were in a spreadsheet so he did a copy from Excel and paste into the Personnel\Configuration screen for the enumerated field. Then he created a template and attempted to import data into the field.
All records were rejected saying the enumerated values were unknown. When we manually selected a value from the pull-down, then exported the records, we say a line break. Unfortunately, it took a few hours of investigation before this was tried.
By editing the value on the configuration screen, we saw that you could hit delete then re-add the last character and the invisible characters at the end were removed and the import worked.
I have seem similar things happen when copying and pasting in Sql Server grids. Beware.
Subscribe to:
Posts (Atom)
