 |
 |
 |
 |
|||
 |
||||||
| Updates of version 7.10, 7.09, 7.08, 7.07, 7.06, 7.05, 7.04, 7.03, 7.02, 7.01, 7.00 | ||
| Updates of all versions are available through the above links. Crystal Clear is committed to making Loan Performer the best software for Microfinance institutions around the globe. | ||
| 7.03 | to top  |
|
| 1. Corrected: Patch702 could not update SQL database. 2. Correction: Russian characters were distorted on some platforms. 3. Corrected: the installation procedure did not always register the Help file(s) correctly with the operating system, so that F1 did not invoke the Loan Performer Help (SMCP, Eritrea). 4. Corrected: in the English version an error occurred after restoring backup then clicking the Login/Logout menu. 5. Corrected: if user made a backup using the Loan Performer facility at menu System/Quit, sometimes s(he) could not start Loan Performer again. A message was given "File error, table ... does not exist" or just "File ... does not exist".. The same error occurred if user was running LPF on a SQL Server database but with difficulty accessing the server and later choose to go back to a Foxpro database. to top 6. Corrected: if a new license with a different branch code was copied into the database and ran to install, afterwards, at startup, Loan Performer was not able to update the database with the new branch code. 7. Correction: if MSDE was not installed and user selected to login into an SQL Server database, (s)he would get all kinds of error messages. Now in the new version, they are trapped and the user is informed that he first has to install MSDE. 8. Correction: if Loan Performer was running and you started Loan Performer again with the same or a different database, you would get a message 9. Corrected: error at login /logout: if user logged in then logged out, on logging in afresh as the same user LPF gave a message ("there are currently 1 users logged in"). 10. Corrected: at Configuration/General, when saving and clicking on the Next button, an error was generated in an SQL Server database. to top 11. Correction: all data entry screens should follow the setting of the number of decimals at menu Configuration/General, but they did not. It was still possible that although the local currency had no decimals, to enter decimal amounts (Socodevi, DR Congo). 12. Correction: at Configuration/Register part 1, user could enter zero's in the format fields. If zero's were entered, then at entry of clients, the user could not access those fields. 13. Correction: at menu System/Configuration/Funds, user was able to enter a transaction date (at Contribution window) that was earlier than the starting date of the fund. 14. Correction: at menu System/Configuration/Funds, if user opened "Funding, Donors" window via New Donor command button, clicking on labels Donor ID or Donor Name generated an error (Error Number 26, Error message Table has no Index order set, KWFT,Kenya). to top 15. Corrected: when at System/Configurations/Users, when supervisor cleared users as not logged in, then went to View all users, the error - Cannot access the selected table - was generated. 16. Correction: if the number of backdated transactions is changed for the current user at Configuration/Users, the public variables are not immediately refreshed when saving and user has to logout/login before the new settings become active. The same for the access rights. 17. Corrected: the menu item Configuration/Define GL Export file was replaced with "Configure Value Added Tax". 18. Correction: menu System/Configuration/Configure Value Added Tax, saving and closing generated an error (Error no:10, KWFT, Kenya). to top 20. Corrected: in the Spanish version, the translation of amounts were incorrect. For instance 140 was translated as 'uno cien cuarenta mil solo, Fundacion Dignidad, Mexico). 21. Corrected: at menu Clients/Group Clients, during entry of a new client under group member information, on entering end of membership date for the new client LPF gave a wrong validation message ("Specified group member has a loan"). 22. Correction: user was able to enter an end-of-registration date for individuals if the person had outstanding shares. 23. Correction: user was able to enter an end-of-registration date for individuals, groups, group members if the client had outstanding loans. to top 24. Correction: if registration had ended, the user could still deposit to the client's savings accounts. This was because the end of registration did not close the savings accounts (at Clients/Savings Details). Now, if the user enters an end-of-registration date, automatically the savings accounts are closed as well and no deposits are possible anymore. 25. Correction: user was not able to enter an end-of-membership date for a group member even if this member or this group had no savings balance and no loan balance (SMCP, Eritrea). 26. Correction: at menu Clients Individual and Business clients, user was able to change Registration date to a date later than opening date of a savings product. 27. Corrected: at menu Clients, page "Other details", if user clicked in the field registration ended, (s)he was not able to leave it without entering a date. LPF gave a validation message: Please enter valid end-of-registration date." 28. Corrected: if during the process of adding individual clients at window Other Details, user entered data in the text areas, then saved, the next entry screen for an individual client retained the entered data of the last client at the Other Details window. to top 30. Corrected: if user entered an individual client, group or business client, saved but then closed the payment of registration fees window by clicking the "X" in the right top corner, LPF generated an error. 31. Corrected: if user closed a savings account, it was possible to put a closure date in the future (after the login date). However if a commission was charged and if the accounting part was activated (start of fin. year entered and savings product should be booked to the general ledger), the commission was booked on this date in the future. This should not have been possible. Now if user enters a date in the future and an account closure commission is charged and this should be booked into the GL, a warning message pops up, giving the user the choice to 1) cancel the charge for the commission, or 2) to have the commission booked on the login date of the user. In the last case, it will cause a difference between the total savings balance in the savings ledger and the general ledger savings balance before the closing date. 32. Correction: if user had created a folder for signature files or photos and indicated this at Configuration / General, the button for signature files and photos did not open this folder and default the images at menu Clients /Loan guarantors after adding the folders during creation of loan guarantors. to top 33. Correction: it was possible to import group members with the same member number in the same import file. For instance 2 members shared the same member number. This is no longer possible. 34. Correction: if an individual client's name already existed in the database, it was impossible to import another client with the same name, using Excel templates, and LPF gave a wrong validation message that the client code already exists and the record was rejected. 35. Correction: LPF allowed client to buy shares by cheque and transfer the shares to another client before the cheque was cleared. 36. Corrected: an error occurred during calculation of dividend in an SQL Server database when the user confirmed to update the savings accounts after printing out the dividends calculation report. A message - "Couldn't save data. Inform supervisor!" - appeared although the report was printed. 37. Corrected: it was not possible to re-print the report on the last dividend calculation. 38. Corrected: at menu Saving/Modify time deposit, attempting to modify a Time deposit opened by a group client with Interest capitalized and deposit paid by cheque, an error was generated. to top 39. Corrected: if at menu Savings/Interest/Calculate Interest on time deposits, interest was calculated on time-deposits that had not expired, LPF prompts the user to print after which a message is given (If correctly printed you can update the time deposit interest. Do you want to update the account with calculated interest ). If user selects YES, LPF generated an error. 40. Correction: after calculation of interest paid on time deposit, if user clicked yes on prompt to "Update accounts with calculated interest" LPF generates an error (Error Number: 1938, "Object is not contained in FORMSET"). 41. Correction: if interest was calculated at maturity for a time deposit, user was unable to calculate interest. LPF gave a message " No accounts found that match your criteria. Press a key to continue". 42. Corrected: if several time-deposits were entered and for some interest was capitalised and for some it was not, the interest could be calculated wrongly at withdrawal of the time-deposit. to top 43. Corrected: contrary to settings at Configurations/Savings, Interest rates with decimal places are rounded of to the next figure if greater than 0.5 and to lower figure if less than 0.5 i.e. if at Configuration/Savings Interest rate is 2.5%, the Savers Statement shows current interest rate as 3%). 44. Correction: at Savings/Deposit with member tracking enabled, after entering a savings deposit for a group client, on saving LPF generated an error ("Pages is not an object"). 45. Corrected: if user made a savings deposit with member tracking enabled, saved all and chose to withdrawal another amount with transfer to/from bank activated, LPF gave a message that last transaction was less than 0 days, do you want to charge a fee? If user chose No, an error was created (Error number 1734). 46. Correction: in an SQL server database, if user entered a savings deposit by cheque and cleared the cheque, entering a savings deposit for another client by cheque from the same bank and with same cheque number generated an error ("Error Number: 26"," Error message: Table has no index order set", KWFT, Kenya). to top 47. Correction: a savings withdrawal as a transfer from a bank account generated an error (Error 1734, "Property 48. Corrected: if user double clicked on the product type under menu Savings/Charges and rewards, an error was generated (Error number 230, "Array dimensions invalid"). 49. Corrected: transferring of savings from one group account to another with member tracking enabled created an error that something went wrong, press a key to continue. 50. Corrected: if savings deposits were to be transferred from one client's savings product to another product of the same client and this client had only one savings product, an error was created (Error number 1, "aprogd.prg does not exist). 51. Correction: it was possible to transfer an amount from a savings account even if user indicated that no withdrawals were allowed or that the account was put on hold. to top 52. Correction: while transferring savings from one client's account to another, the savings balances of the second account with more recent transaction dates, were not correctly updated (Unophone, Uganda). 53. Corrected: if a client deposited a cheque and the cheque was not cleared, the user was able to transfer the un-cleared part of the savings balance to another client. Now during the process of transferring the un-cleared part of the cheque, LPF warns the user that the cheque is not cleared. 54. Correction: if user modified a savings transaction from deposit to withdrawal or vice versa, the savings balance was not corrected (CRS/Horizonti, Macedonia). 55. Corrected: when user modified or deleted a group savings transaction at group member level, it did not update the member details (SMCP, Eritrea). to top 56. Corrected: the interest calculation on monthly minimum balances had many errors:
59. Correction: the reprint Last Interest report showed dates that are not consistent with the interest period for which interest was last calculated. It instead it showed dates in a reverse order. The interest per batch showed the right period (Gamstar, Gambia). 60. Correction: in case of group member tracking for savings, the reprint Last Interest report did not show the names of the members who received interest. 61. Correction: unlike other reports, the Compulsory Savings report had no Heading. Once printed, it was difficult for user to know what is being reported. to top 62. Correction: at menu Savings / Savings report / Personal Ledger, if a client had transactions for one saving product and user changed product to another in which the client had no transactions, LPF gave a wrong validation message ("Specified client code does not exist"). 63. Corrected: when at loan application, if user clicked on 'check savings' the previous window and the windows in the background were still active. Clicking on the window in the background generated an error. 64. Correction: if at loan application, the user entered a grace period that is equal to or longer than the installment period and no interest installments are to be calculated, Loan Performer did not consider the grace period at all. 65. Corrected: if at loan application, user activates checkboxes Lump-sum upfront interest and Interest deducted at disbursement (though not practically sensible), LPF created ledger cards with negative interest balances for loans on declining balance amortisation. As this combination makes no sense, it has been disabled. to top 66. Correction: during loan application, if Upfront interest payment is ticked and type of interest calculation is flat-rate, LPF calculated wrong interest balances and sometimes gave a negative last installment in the interest column at loan ledger card or repayment schedule. 67. Corrected: during loan application for an individual client, at loans part 3, if user double clicked at value text box for collateral 3 or 4, LPF gave a validation message ''collateral can not be zero ..''. On clicking "OK" and saving LPF generated an error (error No:9). 68. Corrected: if repayments priorities were set as modifiable and loans were tracked at group member level, it was not possible to modify group member amounts using the normal repayment screen (Fundacion Dignidad, Mexico). 69. Correction: the name of the group chairperson was not included on the Loan Repayment Schedule when printed at application. At disbursement and if reprinted, the name was included. to top 70. Corrected: if a member was transferred from one group to another and the group from which the member was transferred, applied for a loan (and member tracking was enabled ) the Loan Repayment Schedule was ok, but the Loans Received by Group Members report was wrong. The transferred member still appearer with a loan hence giving a wrong total loan balance. 71. Correction: if user entered a group loan with Flat Rate interest with group loan tracking at group-member level enabled and interest deducted at disbursement and entered loan commission (as a % of the loan amount at configuration), the loan commission was reflected in the loan repayment schedule at group level, but not at member level. 72. Corrected: during application of a loan by a group (with member tracking enabled), the Group Member Repayment Schedule sometimes showed duplicate entries for each transaction. to top 73. Correction: if in version 7.01 or 7.02 the user entered a loan application for a group with interest on declining balance and this loan had a couple of interest installments only and a single balloon installment of principal only at the end of the loan period, the first group member had the correct number of interest installments, but each following group member had one interest installment less than the last group member. 74. Correction: if a loan was entered with a grace period that was longer than the installment period and client was to pay interest with each installment, the grace period was saved as the installment period in days, causing the modification of a loan application to give the wrong number of days as grace period. 75. Corrected: the payment of commissions by savings transfer (menu: Loans/Payment of commissions) created an error (Error number 1734, "Property LCVATCOMM is not found"). 76. Correction: if loan commission is paid by savings transfer from a savings product tracked at member level, LPF correctly debited the group savings balances but not the group member balances causing differences between the member and group totals as it's not known whose member savings are used to pay the commission. to top 77. Corrected: in certain cases a loan disbursed to the first savings account ended up being disbursed to the second. This happened when data was posted using dates earlier than the current date and the screen for re-calculating disbursement dates options came up. 78. Corrected: it was possible to disburse a loan to the client savings account while the account was closed. 79. Corrected: it was possible to disburse a group loan tracked at group level to a savings product tracked at member level which later lead to no savings balances reflected on the group savings statement. 80. Correction: if a loan was disbursed on the same day as the loan application, the loan status was not updated nor the loan cycle number (for an individual or group loan). 81. Correction: the disbursement of loan to a client's savings account resulted in an error "Function requires row or table buffering mode." to top 82. Corrected: if a loan was disbursed less stationery and commission and the user had set VAT on stationery and commission, the VAT was not deducted from the loan amount (Fundacion Dignidad, Mexico). 83. Corrected: if user entered an individual loan application with declining balance amortization with interest deducted at disbursement, and disbursed the loan 1 or 2 days later than the loan application date while the recalculation was set to "Recalculate date and amounts based on disbursement date", the interest balance in the due table was incorrect for all the installments and gave negative interest balances. The option "Interest deducted at disbursement" has been disabled for loans on declining balance. 84. Corrected: if a loan was entered with flat rate interest and at disbursement the user printed the Loan Repayment Schedule, the interest calculation method was erroneously shown to be on declining balance. The error did not occur if the Loan Repayment Schedule was reprinted nor was it shown on the Loan Ledger Card. to top 85. Correction: at loan disbursement, user intends to disburse a loan to a group client but LPF points to an individual client. This occurred under the following conditions: 1. Both the group client and individual client have two or more loan applications each. 2. Group loan tracking at group member level. 3. Client may apply for 2nd loan when 1st loan is still outstanding and client may receive 2nd loan when 1st loan still outstanding are not activated (loans part 1). 86. Correction: if at Loan application, user manually adjusted the first due date to coincide with the application/disbursement date, LPF rejected prepayments for the follow up installments and gave a validation message that the total amount paid is more than outstanding principal and interest. 87. Corrected: The repayment of loans on declining balance had an error. If the loan was in arrears and user entered two repayments, one of them not equal to the interest and the other covering the rest of the interest and some principle, LPF generated negative balances. 88. Corrected: if a minimum balance is set on a savings account and a loan is repaid through savings transfer, LPF did not obey the setting of this minimum balance. to top 89. Corrected: pre-payments for group loans with member tracking for loans with zero interest and commission with every installment, created entries for penalties paid. This then caused problems later on for closing the loan (Forde, Uganda). 90. Correction: menu option Group Member Repayments generated an error (Error No:1597, "View required either DB_BUFOPTRON or DB_BUFOPTTABLE"). 91. Corrected: if user wanted to enter loan repayments using the Group Member Repayment screen, LPF did not allow to post repayments for groups without savings products defined. It happened even when the transactions have nothing to do with savings. 92. Corrected: repaying arrears from savings created errors if no savings were available to repay the arrears. 93. Correction: the module "Repay Arrears from Savings" did not recalculate the interest for loans on declining balance. Now - if in configuration - this is set as being compulsory, this module recalculates the interest first before proceeding to repay from savings. to top 94. Corrected: the menu option Repay Arrears from Savings and with Grameen methodology, an error message "Variable 'TOTARR' is not found" appeared when adjusting the free savings column. 95. Corrected: sometimes an error occurred when repaying arrears from savings. LPF informed the user that these transactions are not possible, do you want to preview them? On answering Yes, a list of loans with mismatched figures showed up. Later LPF said that no exchange rate had been set for the period even when none of the loans was linked to a second currency (Forde Uganda). to top 96. Correction: the deletion of a paid loan commission (menu Loans/Deletions/Payment of Commission) gave an error (Error no 12, "Variable Commdate not found"). 97. Correction: when a prepayment was made on a Flat Rate loan with group member tracking enabled, the group members dues were not properly updated. This caused problems for later repayments (Socodevi, DR Congo). 98. Correction: at menu Loans/Penalty for a single loan, on selecting a group loan in an SQL Server database (group member tracking enabled and member gets individual loan), LPF gave a window labeled Open Table, on clicking OK, LPF generated an error (Error number 1, "File:'C\Lpf 702\memdue.dbf' does not exist", KWFT, Kenya). 99. Correction: if at menu Loans/Automatic calculation of penalties on arrears, user changed the loan product type, an error was generated regardless of the method of penalty calculation. 100. Corrected: if a loan was closed with no interest and user deleted the last repayment, LPF did not reset the repayment schedule to what it was originally. to top 101. Corrected: at the screen of deleting a loan, the transaction number did not increase with every deletion of a loan. 102. Correction: if the user disbursed the loan in two different installments, on deleting one of the installments, LPF gave a warning message "The Key defined by the key field property for table (P_datapath +"xDue") is not unique. 103. Correction: if client applied for a loan and user disbursed it by transferring it to a clients saving A/C, on deleting the loan, the amount still appeared in the clients savers statement. 104. Correction: if in version 7.02 the user entered a loan application with interest on declining balance amortised and this loan had a couple of interest installments only and a single balloon installment of principal only at the end of the loan period, then at disbursement the option to recalculate due dates and amounts messed up this repayment schedule so that the total principal due was twice the loan amount and due dates were incorrect. 105. Corrected: if on an SQL Server database, loan applications were imported and then user entered a new loan, the new loan could get a loan number that already existed, causing confusion for Loan Performer later on at disbursement.. 106. Correction: the importation of loan disbursements for group loans (Grameen methodolgy) created errors (Error number 12, "Variable int is not found"). The Ledger Card for the same loan against original dues created an error "NBALVAT is not found". to top 107. Corrected: with importation of loan repayments, LPF is making a wrong comparison when checking for repayment dates that are later than written off dates (SPBD, Samoa). 108. Correction: importation of loan repayments returned incorrect error: "Wrong number of parameters passed to function 'InsRepay'. This should be ten."v Corrected: when printing out a report at the time of writing off several loans, the following error occured: "Wrong parameter type passed to function 109. Corrected: at menu Loans/Write off loans, after previewing the automatic written-off loans report, LPF gave a validation message (Data is not saved, loans can only be written off if printed). LPF did not automatically prompt the user to print after preview. 110. Correction: the label for credit officer is a user defined label at Configuration/Define Labels/Users. However most loan reports had still hard coded labels if ordered by 'Credit Officer'. to top 111. Correction: the Loan Ledger Card did not update the VAT and Total columns if a penalty was added on which VAT was due (Fundacion Dignidad, Mexico). 112. Correction: The Amounts Due report only printed loans due if user selected by monthly period. If other options were selected, no loans were found (CRS/Horizonti, Macedonia). 113. Correction: the selection items "Only due in period" and "Principal only" of the Amounts Due report were not reflected in the report header (CRS/Horizonti, Macedonia). Corrected: the Amounts Due report has a checkbox saying "Show principle only", however if checked, user would get a message saying "No loans found that match these criteria". 114. Corrected: at menu Loans/Portfolio reports/Reports on repayments/Repayment of dues reports, choosing a business sector resulted to an error ( "Property SECTORNAME is not found"). 115. Corrected: the report "Repayments by voucher number" has been renamed "Listing of repayments". The savings products have been removed from the 4 report formats. They were not part of the reports anyway. An additional checkbox is added saying "Past-due payments only". If selected, the report only shows repayments where either the principal or the interest part was a payment of arrears (Oxfam GB, Azerbaijan). This report also got 2 additional report formats, one with date, loan number, client name, receipt number, officer, total paid, principal, interest, penalty and commission and the 2nd the same but with reference number instead of officer (Caritas, Haiti). to top 116. Corrected: the indicators Portfolio at Risk according to age classes on the Performance Monitoring report were calculated on number of loans in arrears versus total loans outstanding and not on amounts in arrears (ID, Haiti). 117. Corrected: the Guarantors report in a corporate database was incorrect. Guarantors were entered with a simple ID number. When creating a corporate database, loans were linked to the guarantor of a different branch. Now guarantors have gotten a branchcode (Socodevi, DR Congo). 118. Correction: automatic transactions could be linked to header accounts. 119. Correction: the item 'Active' in the window Chart of Accounts was not always correctly reflecting the underlying value (DWA-SLP, Angola). 120. Correction: if an item was not properly linked to a GL account, the user was given an error message saying "One of the general ledger account numbers does not have a value. Please check the linking to the GL accounts of this product in System/Configuration." It was not always clear for the user where to look for this missing link. Now LPF informs the user more specifically. 121. Corrected: running a year closure created errors in Foxpro as well as SQL Server databases. In both cases it was not possible to close the year correctly. After closing LPF and logging in again, the user could get a message like "Error, file ... does not exist, please restore backup". to top 122. Corrected: the APPEND FROM command was not working properly in an SQL Database when it was appending from a view. This occurred in the Year Closure and the procedure for De-Archiving (SMCP, Eritrea). 123. Correction: if the Trial Balance, Income & Expense Statement or Balance Sheet were run with a starting date not equal to the start of the financial year, the balances carried forward were incorrect (Foccas, Uganda). 124. Corrected: if user made a budget for an item in one financial year and later asked for a budget report in another financial year, an error was created (Error number 1806, "Sql Column DEC is not found"). 125. Correction: The option to recalculate savings balances under menu Tools/Check Database was not working (Unophone, Uganda). 126. Modified: with a demo version (without a license), the number of individual clients and businesses is limited to 500 each, the number of groups is limited to 100, the number of group members to 500, the number of savings transactions to 2,000, the number of loans to 1,000 and the number of general ledger transactions to 2,500. 127. Modified: the Amyuni PDF Driver for printing to PDF format has been updated (with improved support for Office XP/2003). to top 128. Modified: the backup procedure has been replaced by a new procedure using CAB files. The old procedure sometimes had problems restoring files. 129. Modified: when starting LPF, the log-on screen shows the last opened database, also in the SQL version. In previous version loading LPF took time because LPF always checked for available servers and databases. 130. Modified: under Tools/Check Database, a feature is added to post transactions from header accounts to non-header accounts (to correct balances on Header accounts). This is in the form of a debit-credit transaction and the transferred transactions have to be printed out. 131. Modified: at menu Tools/Check Database an option has been added to create a file that displays the structure of the database. Users can email this file to the developers to check the consistency of the database. 132. Modified: at Configuration/Define Labels, a "Replace All" button has been added to replace all occurrences of a word in all screens and reports. This is only available if source and destination language are the same. 133. Modified: at Configuration/Funds, the time-deposits (product code T..) are added as a source for the loan fund. 134. Modified: the user - even if (s)he does not have access to the configuration - can now change his/her background picture (at System/Change password). to top 134. Modified: if user closes a savings account, a message-box shows up asking whether the user wants to calculate interest on the account. If positive, a voucher is printed and if the printout is confirmed, the account is updated with the interest. 135.Modified: savings deposits/withdrawals don't have to be entered in chronological order anymore. Before this had to be the case, now it is more flexible and this parameter can be set per product (Socodevi, DR Congo). 136.Modified: a four-weekly loan type has been added. 137.Modified: almost all loan reports have additional filter criteria where the user can filter on any field of the underlying cursor (Eclof, Kenya). 138.Modified: the Loan Provision report (under menu Accounts) has an option to print the report with client names (Group Agir, Haiti). 139. Modified: the option "Repay loans in arrears from savings" has got a checkbox to select all loans. Now it is no longer necessary to click each and every single loan that is involved (Socodevi, DR Congo). 140. Modified: the report that can be run from the 2nd page of menu item Savings Balances - a report for group members' balances - has a filter option to select a range of account numbers only (Group Agir, Haiti). to top 141. Modified: the Outstanding loan balances report has a checkbox where user can select to include written-off loans (World Vision Kosovo). 142.Modified: the validation on the "Repayments of Dues Report" where the end of period date cannot be after the login date has been removed (Oxfam GB, Azerbaijan). 143.Modified: the Guarantors report can also be grouped by loan number. 144.Modified: the Breakdown report has an additional filter criteria where the user can select on the type of transaction, making it possible to filter for instance only disbursements from the loans account (SMCP Eritrea). 145. Addition: a Month Closure under menu Accounts, before Year Closure. The first month should be set to the first month of the current financial year. Loan Performer does not allow to book in closed months anymore. 146. Addition: With version 7.03 the user may expect 'Service Packs' that can be downloaded from our website and installed on the local machine to correct bugs. |
||
| 7.02 | to top |
|
|
1. Corrected: at entry of a new client under group member information, on entering end of membership date for the new client Loan Performer gave a wrong validation message (Specified group member has a loan). 2. Corrected: at menu Clients/Business or Group, if a client is retrieved and user clicked on the button for the selection of a geographical area, and then on the column header "Area name" to order the list according to area name, an error was generated. 3. Corrected: if user entered an individual client, group or business client, saved but then closed the window for entry of payment of registration fees by clicking the "X" in the right top, an error was generated. 4. Corrected: an error occur during the calculation of dividend, when the user confirmed to update the savings accounts after printing the dividends calculation report. 5. Corrected: on attempting to make a savings deposit for an account that has a closing date, even if it is not due, Loan Performer gave a wrong validation message, (Account is closed! No deposits possible, if you want to reactivate the account choose menu client and delete the end of membership date or account closing date.) to top 6. Corrected: making a group savings deposit while tracking of group savings was activated, created an error (Error number 1924). 7. Corrected: at savings deposit during depositing of member amount at group member information window for some group clients (group member tracking enabled), a savings balance appears but on checking at the savers statement no transaction has ever been recorded for the client. During the process of closing an error was generated. 8. Corrected: under menu Savings/Transfer savings deposit, if the transfer was from a group, on double clicking the Membership No. textbox an error was generated. to top 9. Corrected: if at interest calculation, user choose to print a report while the printer was off, an error was generated (Error number 125). 10. Corrected: the monthly minimum balance method of interest calculation on savings for groups with member tracking enabled showed incorrect minimum balance for group but correct interest amount for entire group at the report generated during interest calculation. 11. Corrected: after opening a time deposit, if user goes to Savings/Interest/Calculate interest on time deposit, on calculating interest earned and setting the pay status to yes, Loan Performer prompts the user to print. If confirmed, a message follows "If correctly printed you can update the time deposit interest. Do you want to update the account with the calculated interest?". If confirmed, an error is generated. 12. Corrected: Loan Performer generated an error if working with the SQL Server database, when the user clicked the preview button to generate the loan repayment schedule on page 3 of the loan application form. 13. Corrected: it was possible to disburse a loan to the client savings account while the account was closed. to top 14. Corrected: under menu Loans/Group member repayments, Loan Performer generated an abnormal screen for a client who had no loans. 15. Corrected: many reports generated errors when selecting Business Sector (Error number 1734, "Property SectorName not found"). 16. Corrected: at menu Loans/Portfolio reports/Reports on repayments/Payments made during a period, on selecting an item at the business sector drop down box an error was generated. 17. Corrected: with an SQL database, it was not possible to modify a financial transaction in the GL. 18. Corrected: in version 7.01 it was possible on a network for the same user to login several times with the same username from different machines. to top 19. Corrected: at menu Systems/Configurations/Users, on selecting "View all users", an error was generated. 20. Modified: the Savings Balances report has a format with telephone numbers (Unophone, Uganda). 21. Modified: with an SQL database, the speed for reporting was very slow. 22. Modified: a checkbox is added to the Amounts Due report, saying "Principal only". If checked it gives only principal and no interest (Oxfam GB, Azerbaijan). 23. Modified: the validation on the Repayments of Dues Report - where the end of period date cannot be after the login date - has been removed (Oxfam GB, Azerbaijan). to top
|
||