CFLRSuite 2008-1a

DissoMaster               Propertizer              Executioner

Updated September 9, 2008

I.   NETWORK INSTALLATION STRATEGIES

II.  KNOWN ISSUES

III. FIXES/ENHANCEMENTS

1.         DissoMaster

2.         Propertizer

3.         Executioner

 

 

==================================================================

 I. NETWORK INSTALLATION STRATEGIES

==================================================================

 

1.     Installing to a client from a network drive.

a. Normal installation.

b. MSI Advertisement installation.

2. Installing from a client to a network drive.

3. Installing to a shared network drive, then creating shortcuts to the program on the shared drive from other client machines.

4. Sharing DissoMaster case files over a network.

5. Installing the program once on a shared network drive for use by multiple clients.

 

1. Installing to a client from a network drive.

     

a. Normal installation.

 

This should work normally, same as installing from a CD-ROM.

 

b. MSI Advertisement installation.

 

Advertisement installs are supported. In order to set the license and default case to values other than the default, create a MSI transform to set property values, and then specify the transform during the advertisement installation.

 

      2. Installing from a client to a network drive.

     

This should work fine. However, even though some program files will get copied to the network drive, some files still get created locally to the user’s machine. The user’s default case file (default.dmr) gets created in the user’s Common Application Data directory. The location of this directory varies depending on the version of Windows, but it is normally on a local disk. Also, several required components get copied to the user's Windows System directory, and the installation will install or update key Windows DLLs if required. The installation also registers ActiveX DLL’s in the client machines Windows registry.

 

Generally, there is little advantage to installing to a network drive. In fact, it is not recommended.

 

A specific case study: Installing the program to a shared network drive from multiple client machines. For each client machine, the program is installed the same network path. Only the first client works   properly.

 

Here is the reason. The installation only installs and registers a file if the file does not already exist, or the existing file is an older version. When installing into the network path where the current version has already been installed by another client machine, the setup does not need to install some files, and hence does not register those files with Windows. The registration step is necessary, so in this case the installation is incomplete and DissoMaster will not work.

 

3. Installing to a shared network drive, and then creating shortcuts to the program on the shared drive from other client machines.

 

This will not work. There are changes that need to be made to the local machine in order for DissoMaster to run properly. The setup accomplishes the necessary steps, and must be run on each client machine. See number 2 above.

 

Note:

This seems to have been a common strategy for installing previous versions of DissoMaster (pre-2001). It worked because the previous version did not need to make any registry changes, and did not use the standard windows data directories. The advantage to this simple installation was, well, a simple installation. The disadvantage is that it doesn't benefit from using components like print preview, grid controls, etc. It also doesn't take advantage of the Window's multiple user login features, which allows different users a single machine to have their own data directories and settings.

 

4. Sharing DissoMaster case files over a network.

           

The case files can be saved and opened from a shared network drive. Sharing the files does not require the program to be installed on a network.

 

5. Installing the program once on a shared network drive for use by multiple clients.

 

The program is not conducive to this installation strategy. In fact, it is not recommended. See item #3 above.

 

 

==================================================================

 II. KNOWN ISSUES

==================================================================

   None.

 

==================================================================

 III. FIXES/ENHANCEMENTS/CHANGES:

==================================================================

NOTE: For fixes and enhancements to version prior to this year, see the History file.

 

1. DissoMaster

 

Version 2008-1a

 

** In rare circumstances, certain combinations of support case input figures were causing the Proposed Calculation to lock up the application for tactics other than Tactic 9. This has been fixed.

 

Version 2008-1:

 

      ** Updated 2007 actual taxes, and 2008 and 2009 estimated taxes.

** Changed labels on Include Federal/State Income Taxes checkboxes in the Taxes tab of the Settings dialog to read Include Federal/State Income Taxes and Credits.

** Changed FICA label on Findings and Rebuttals report, Formal Report, and Printed Order, to read FICA + Medicare.

** We have removed the calculation report tab.

** We have adjusted the FC § 4061(b) calculation, which involves subtracting spousal support paid from the payor’s net, so that the high net cannot exceed the parties’ total net.

** As a result of Microsoft changing the behavior of the ALLUSERS property on Vista, we can no longer support the “install for current user only” installation.

** We fixed the total federal tax value (Line 76 on the Form 1040) in the proposed column, which was incorrectly displaying as 0 for both parties, even though the actual proposed total federal tax was being calculated correctly. The guideline column was displaying this figure correctly, and was unaffected by this bug.

** We fixed the child tax credit value (Line 56 on the Form 1040) in the proposed column, which was incorrectly displaying as 0 for both parties, even though the actual proposed child tax credits were being calculated correctly. The guideline column was displaying this figure correctly, and was unaffected by this bug.

** We fixed the value for Deductible Miscellaneous, under the Federal Tax Information heading in the Cash Flow Pane, which was incorrectly reporting the 2% floor, instead of the deduction.

** We fixed an issue whereby section 1250 gains were failing to zero out when the Other Taxable Income parent-value was zeroed.

** We fixed an error whereby the figure displayed on the Printed Order representing the net disposable income used to calculate spousal support appeared to include Significant Other/New Mate Income. This error was confined to the  value displayed on the Printed Order; the actual spousal support calculation did not include new mate income.

** We fixed an issue whereby using the add alternate weekdays option on the right-click menu was adding the days in evenly numbered weeks only (where Week 1 commenced January 1); using this option will now correctly add the days in alternate weeks beginning with the day you have selected.

 

    

2. Propertizer

Version 2008-1:

** No significant changes

 

3. Executioner

 

Version 2008-1:

** We updated the IRS interest rates.

** Fixed issue relating to losing the Delinquency Notices tab when switching case-type back and forth between Spousal Support and Child Support