Known issues in ReservePro 5

The following items in ReservePro are open and under investigation:

 

  • In certain situations in ReservePro v5.0, File Math does not correctly add user defined tables together as expected in in layers other than Net.
  • Also, graphs of tables in layers other than Net may not print correctly in certain cases.

Solution:

An updated version of ReservePro (v 5.0.0.419) is available for download for all clients on our maintnance plan.

 

 

 

  • Microsoft recently released a new 64-bit version of their Microsoft Office solutions. Like most other 32-bit applications in the current marketplace, ReservePro's API has some challenges in certain cases when being used with this new 64-bit Office system.

Workaround:

Until a solution is available, we recommend continuing to use the 32-bit version of Excel for all work that involves the ReservePro API and Excel working together.

 

 

  • When using the API to retrieve data from ReservePro into Microsoft Excel, certain columns in my ReservePro report do not come through into Excel.

Background:
A few of ReservePro’s reports are dynamic, based on data in the file and/or on certain selections the user may have made within ReservePro.
Three reports have a fixed set of columns, as well as additional columns that are variable. These are:
   Losses: 1 - Summary of Losses and Reserves
   ALAE: 10 - Summary of ALAE and Reserves
   Claims: 20 - Summary of Claim Counts
For example, the Summary of Losses and Reserves can have up to seven columns; the first three (Paid Loss, Case Loss Reserve, Incurred Loss) are always present. If you have data in the selected Ultimate Loss vector, you get 5 columns, adding Indicated IBNR Loss Reserves and Ultimate Loss. If you have data in the IBNR Loss Reserves triangle, and in Ultimate Loss, the report will display 7 columns, adding Incurred Plus IBNR Loss and Indicated Change in Loss Reserves. ALAE Report# 10 and Claims Report# 20 behave similarly.
In all three of these reports, the API will only import the first three columns, the ones that are always available in the report.

Some other reports are also variable in their structure, and they may also present difficulties in extracting data with the API. These include
• Comparison of Ultimate Reports (#12, 21, 3, 56, 28) - dependent on the user’s selection of methods
• Cash Flow Reports (#29, 30, 31, 32) - dependent on the length of the payment pattern
• Berquist-Sherman Adjusted Exhibits (#217, 218, 224, 225, 226, 219-223) - dependent on selections made regarding the Selected Trends.
The columns present in these tables will vary depending on user selections within ReservePro.

 

Workaround:

In all cases, you can work around this by replicating the specific report or exhibit to a user-defined report (Tools | User Defined | Replicate). The new report will have all the columns, and you can then use the API to extract data from that report rather than from the dynamic system-provided one.

 

 

  • ReservePro does not install as expected under Windows Vista or Windows 7. When trying to install or run ReservePro in Microsoft Vista or Windows 7, I receive a message "Failed to update the system registry.  Please try using REGEDIT."

Solution:

Both Vista and Windows 7 use security protocols that require that you install the software as an "Administrator," and that you configure the system to use directories to which the system has specific rights.  

Complete details about installing and running ReservePro under these environments are available here:

 

 

 

  • When Page Layout is set to print multiple tables per page, and you insert a page break in the print list, the page break can sometimes be ignored.  For example, set Page Layout to print 2 tables per page, but then insert a page break after the third table. If your print list contains more than three tables, you expect only one table on your second page, but it may not always print that way.

Workaround:

If that happens, instead of inserting page breaks in the print list, insert a new page setup to modify how many tables per page to print.

 

 

  • The ASCII import may not automatically append a new diagonal to an asymmetrical file as part of the import process.

Workaround:

Append the new diagonal in the ReservePro file (Tools| File Structure | Append New Evaluation Period) before importing the ASCII data.

 

 

  • In certain circumstances, table math performed on a blank user-defined object results in numbers in the table, rather than resulting in a table of blank cells.

Workaround:

None known, other than not performing table math on a blank user-defined table.

 

 

A number of open issues were resolved in our most recent release of ReservePro. Please check there to see if we have released a fix to an issue you may be having.

As always, we welcome your feedback and suggestions.  Feel free to contact us.

 

 

P&C Insurance Software
Atlanta, Georgia, USA
Phone: 800 404.2276
  or      404 254.6752
Fax:     404 237.6984