Captools/net is a computation intensive software application.  Most of these computations occur in the Captools/net server-side applications, so as to minimize any need to update the desktop application as a result of changes in computational methodology, although as noted in the next topic, some computation do occur in the desktop application.

 

Captools/net Desktop Column Computations - Column computations for Captools/net Desktop are performed in that application in order to provide relatively quick response to the user while they are entering or editing data.  Column computations is where one column in a record is recomputed as a result of a change in value manually edited in another column of the same record, e.g. the amount being recomputed in a transaction record when the trade price is changed.  This type of computation is triggered when you move out of an edited column by tabbing out of the field or clicking on another cell in the Desktop grid.

 

Captools/net Desktop Row Computations - Row computations for Captools/net Desktop are performed in the CTServer application, with the results sent back to the Desktop grid.  An example of these computations is the computation of the transaction estimated tax field.  These computations are triggered when you move outside of the current record by clicking upon another record or by using the keyboard arrow keys to move out of the record row.   Moving between portfolio transaction records rows also triggers immediate recomputation of portfolio position and valuation records for share quantity, cost bases and valuation changes due to changes made in the edited transaction.  These computations also occur in the CTServer application.  Because these types of computations tend to be more complicated, and because the relevant data makes a round trip to the server application, there may be some slight delay when moving out of an edited portfolio transaction record.  However this delay is more than compensated by the elimination of the need to re-compute "perturbed" portfolio valuations as in prior versions of Captools.

 

Captools/net Desktop "Compute" Function - The CT/net Desktop contains a "Compute" function which allows you to "force" the computation of the selected field.  The computations triggered by this command take place on in the CTServer or CTTasker program in a fashion similar to the row computations.

 

Batch Operations & Reports - All Captools batch operations and reports perform their computations on the server in either CTServer or CTTasker, where each process is executed in its own "thread" so that these processes do not unduly impact performance for Captools/net end users while they occur.

 

 

Computational Methods

 

Captools/net computations are embedded in pre-programmed Captools Co. proprietary software code and are not available for manipulation by the end user as is the case of a generic spreadsheet or database where the user themselves must develop and maintain all of the computational formulas and routines.  Where more than one generally accepted computational methodology exists, Captools/net often offers the user a choice of methodology through a user preference at the program level, reporting specification level or at the individual data record level as is appropriate to the case.  One example of such controls are the Portfolio Computations controls which may be set at the program level and also at the account record level.  Security records and reports also give you selection of various computational methodologies.

 

Occasionally a user will question a computational result and inquire about the methodology.  Because our software code is proprietary, and furthermore because many computations are involved, multi-step procedures, we will not respond to questions such as "please show me the formula as to how such and such is computed".  However, we will entertain challenges to computational results, provided that the user states the alternative result that they think is correct and furthermore provide complete computational justification for such result.  Such justification must be provided, however, in complete formulaic entirety, and not simply be the result of another software program for which the underlying methodology is unknown.   In those cases where the user has satisfactorily (to us) demonstrated sufficient superiority of the alternative methodology, we will entertain making the appropriate software changes, albeit on a time line that we reserve the right to determine.