INSTALLATION INSTRUCTIONS: Most of the programs here are in LZH format, the data compression used for Rent Roll backups. Save the program to your Rent Roll folder, then get to a DOS command prompt and change to the folder with your Rent Roll files using the CD \RENTROLL command. Then type LHA X whatever.lzh and press {enter} to extract the program. Contact Peter for more detailed instructions. Most programs can be run simply by typing the program name followed by your four-letter (digit) property ID, such as RR_INTEG ABCD and then press {enter} to run the data integrity test on property ABCD. Anywhere you see pppp, put in your actual property ID in the typed command.

• FIXCASH: This program will recalculate cash payment history and reapply cash payments to a given tenant's ledger to fix incorrect balances. Contact Peter Steiger for instructions.
  
• FIXCV: Updated 11/05/2008 New for 2008! Automatically repair all your charge variances in SECONDS. Just type FIXCV pppp {enter} and it will eliminate all charge variances by writing LTOL/LTOR adjusting entries to all units with variances. More documentation here.
  
• FULLFIX: All of the following utilities in one handy, humongous download updated 07/24/08
  
• RR_INTEG: Analyzes your property data and reports any discrepancies. Save it to your Rent Roll folder as described above, then from the C:\RENTROLL prompt type RR_INTEG pppp {enter}. The results are displayed to screen with an option to print them (I strongly advise against printing the results, as it may be a report 100 pages long). It saves the report to a file pppp_BAD.LOG which you can view on-screen or email to the support department.
  
• RRFIXALL: NEW! Version 5.0 06/17/08 now with AR batch number repairs.  Fixes the most common data damage automatically. Syntax is simply RRFIXALL pppp {enter}. The repair results are stored to a log file pppp_FIX.LOG.
  
• BALANCES: NEW!  version 5.01 07/03/2008 handles subjournals too! BALATENA will scan (and optionally fix) your tenant balances. Good for locating the cause of 2.5.4 and 1.7.2 not matching up. Syntax is balatena pppp . The results are put in ppppBALA.LOG and contain details on which tenant balances (if any) have problems, and what steps you can take to correct them. The log file format is a little sloppy because I threw in extra warnings for various problems that came up, and at the time the only person who needed to understand how it works was me. If the situation requires it, you can perform a "quick" balance fix with the command:
  balatena pppp fix . This will change the 2.2 tenant balance total without changing the tenant ledger or rebuilding delinquent history, and only rare circumstances will make this a desirable choice.
  
  BALATPTD will likewise scan (and optionally fix) the total period to date amounts as reported in the 1.7.2 report. You need to supply the property code and at least one month in the form YYYYMM to make it work:
  balatptd pppp 200401
  You can also optionally specify an ending date to scan a series of months all at once:
  balatptd pppp 200401 200403
  You can also tell it to fix balance problems as it finds them with the FIX parameter, either with or without the ending month: balatptd pppp 200401 FIX
  balatptd pppp 200401 200403 FIX
  
  The results are reported to ppppTPTD.LOG which you can view on screen, print, or send as email if you have questions.
  
  
• NOMOLTOL: This means "no mo' LTOL" and refers to the fact that after a purge, you sometimes end up with years of nothing but LTOL/LTOR entries that predate the purge. NOMOLTOL will not only clean out those unwanted LTOL prehistory entries, but also pack out deleted and blank transactions that result from extensive 2.5.2c rebuilds. If your site has done a lot of purging or 2.5.2c history rebuilds, NOMOLTOL can reduce your backup size by a disk or two! The syntax is either NOMOLTOL pppp to find the last purge date and remove only the charge variance history that predates the purge, or you can tell it NOMOLTOL pppp mm/dd/yyyy where mm/dd/yyyy is the cutoff date. That way, you can purge obsolete charge variance history up through a given date without purging the actual rent history.
• F105TEST: Locates unit database errors that cause F:105 discrepancies. Don't you hate it when lines 16 and 20 of the F:105 don't match? Often, this is due to a problem in one of the unit 3.2 screen tenant history dates. The 3.2 screen keeps a history of the current and previous 6 tenant move in and out dates, and if those ever get messed up you will see problems in the vacancy count. F105TEST.EXE will identify every unit that is (or was last week) counted as vacant, and explain why it thinks so. Save it to your Rent Roll data folder, use LHA X F105TEST to extract it, and run F105TEST pppp where pppp is the property code. The results are listed in pppp_105.LOG.