Home

Samples and figures provided in this document are not necessarily coherently in binding in design. It is up to the user to make his or her 'story' complete by applying the principles.

4. Version Icons

Icons like these

... indicate the associated section is a new or revised section with a new version number.

EAT is a software tool. It was built to run on MS Windows. The head program is called Eat Manager in Windows GUI. It takes input Excel file(s) and produces an output files either in Excel spreadsheet, text or in HTML, while the Excel Sheets are industrial standard and the most popular software tool in data processing worldwide. The tool is very convenient and versatile.

2. System requirements

It requires :

a Windows 7, 8, 10 or 11 OS system
a Windows Microsoft.NET Framework 4.6.1
an Internet browser
a Microsoft Office Excel program, Google Sheets On-line or other equivalents
a license from Teknewell
The download may be blocked by your browser. Choose 'Keep' or 'Keep Anyway'.
The zip file may be blocked by Windows, goto the zip file's property, unblock it, and then extract to your desired disk location.
The program executable may be blocked by Windows or Virus Protection. Choose 'Run' or 'Run Anyway' or Excludsion.

3. Purposes

The output file contains accounting reports of financial accounts primary and summary for families and organizations.

4. How it works

A family member or company employees add basic account ledger records. These records are basic financial records and are minimum in number and the least time consuming. Once the ledger Excel files are collected at the directories defined in parameter file, the Eat Manager can run EAT command line tool and produce the report Excel file flashing easy.

5. Benefits

EAT is a economic, cost-effective to own and convenient and safe to operate. Once EAT is installed and a accounting model is configured for business, there is no need to change the model often. The model is also easy to adapt if such a need arises. The only task requiring a user to take routinely is to enter ledger transactions according to business activities and create reports for analysis of account health (audit) and purposes.
No fancy installation process to run and no host PC environmental variables to set up. Just unzip the downloaded zip file to be ready for production.
EAT Tool makes family and company financial data available right away for college financial aid or other applications.
EAT Tool allows a parent or a manager forecast or predict next month's account balances by utilizing previous month's average data, pattern and unusual transactions.
By changing credit card's due date to 7th of each month and setting up auto payment on statement balance, you basically are left nothing to do except making checking account fund available for next month by transferring fund from savings to checking on 5th of each month right before the due date, and except downloading CSV statement files and pulling 2 or 3 amounts from banks and updating the ledger records and in the meantime auditing and monitoring the account's health.
This bill-pay activity only happens once in 1 day of a month and saves you a lot of time and allows you to attend to other family activities. This EAT Tool does not electronically and automatically pull the data from banks. You must do the small amount of work to see if your accounts match up your bank accounts. Knowing your accounts are healthy makes you sleep tight at night.
EAT tool is for managers to create financial reports of all accounts. One license is good for one manager of an organization unless there is a need to divide business to acquire multiple licenses.
Multiple Excel files enable company to have multiple employees working from different departments to contribute adding ledger records.
Eat does not transmit user accounting data across the Internet. So it is safe to operate and user financial data is by no means to be leaked away to create security worries. Eat may use Internet to verify license validity though.

6. License Agreement

Users should have at least once read the User Purchase and License Agreement at time of using the Trial version. Subsequent decision to purchase the software indicates user agrees without preservation the provisions set forth in the document of User Purchase and License Agreement.

Teknewell is a registered legal company in Massachusetts USA, The product tools are safe. Please also read the readme.txt if available.
Here you can access User Purchase and License Agreement

C. How to acquire EAT

1. Ownership Time-line

2. Trial Version

To download a trial version, click a menu item. The trial version only lasts for a few months. Follow on-screen instructions, and you should have downloaded the file through the browser. The zip file is like the pattern 'eat*.zip'. The browser, virus defender and Windows OS may block the zip file and its exe files as suspects. User should choose trust, 'run anyway' or exclude from protections.

3. Product Version

If you felt EAT is a useful tool and can help you manage your family's or company's financial accounts and analysis, and decided to use, then click a menu item to purchase the real product. The process is similar to that of the trial version.

D. Install EAT

1. Unzip file

Unzip the zip file, normally in 'download' directory. Save the files into a directory in which you will work in the future. This directory is called Installation Full Path (IFP).

2. Pin to Taskbar

The tool's main executable is 'EatUI.exe'. Making a Run Icon in the task bar will help to run the program easily. Goto IFP, right click on 'EatUi.exe', then click on 'Pin to Taskbar', and a new Icon will show up on the task bar. Click the icon to run the program.

E. Graphic user interface

1. Purpose

This latest program 'EatUi.exe' encompasses all functions of the tool. Because it is a Windows Form program, it is easy and direct to carry out tasks important to businesses. It serves as a overall manager for user. The program was developed at a later stage and replaces the previous Console applications. It is also straight forward or self explanatory to navigate around the interfaces. In this document we will not provide more details of each functions. User should be able to familiarize one self without issue. If not, send a support ticket to get a answer.

2. The Models box

On the left is the model box. The box lists all model files prefixed by 'model'. All model files reside in the directory 'model'. Refer Model in later chapter regarding commands available in Model file. When a model is selected, it becomes active and all subsequent functions are carried out for the model.

3. Instruction page

On the right is the box for all other pages. Instruction page contains an editing box to allow user to record instructional notes.

4. Model page

Model page presents the parameters of all commands in the Model file. User could alter the parameters to fit for a particular run.

5. Manual page

Manual page consists the locations and all manual input files. The word 'manual' indicates all commands are entered by user into input sheets of Excel files specified here.

6. Auto page

Auto page consists the locations and all bank CSV input files. User does not need to modify the CSV files. They can directly participate in the 'run'.

7. Run page

Run page is the dividing page. On its left are the pages of preparation before the execution. On its right are the pages of results of the execution. This page allows user to click a button to produce the reports. There are few argumental UI choices user could consider before the 'run'.

8. Log page

Log page lists all log files of the executions.

9. Rpt page

Rpt page lists all resulting report files which includes XLSX and HTML file types.

10. Archive page

Archive page lists all archived files. The archived files are not generated by the execution, and not subject to being deleted by the 'clean' operation. On the Log and Rpt pages there is a button 'Archive' user could click to archive a particular file. We recommned user to archive at least 2 files for each cycle. One is the report file that has beed reconciled, the other the result report file that has been forecasted. Archive is a great way to keep history files at bay for future references.

11. Backup page

Backup page provides a way to backup the tool and user's family or business accounting data to a location deemed safe and can be recovered if a break-down took place unexpectively. We recommend user to backup the files when significant additions of data have taken place, or at least after each cycle's forecast has been done successfully.

12. Clean page

Clean page allows user to delete files in the directory 'log' and 'rpt'. These files are created after each execution and cumulatively increasing in number. We recommend user to delete the files every half year and also consider a reasonal minimum number of files to be kept for refernece in immediate future.

13. Doc page

Doc page provides few URL link buttons for easy access of on-line User Manual and others.

14. Support page

Support page provides a URL link button to access the on-line support page.

15. Upgrade page

Upgrade page provides a URL link button to access the on-line upgrade page. Upgrade is free within the term of a valid license.

16. About page

About page describes informational detail about our company Teknewell Engineering.

F. Work flow chart

1. The Chart

Follow the below work-flow chart which resembles a family monthly financial management activities.

G. The model

1. The model file

Under the directory 'model', user creates model files prefixed with 'model' like model-*.xlsx. In this file you can specify the location of input files. There are few commands available. See following table of commands. Note user can edit Excel file in Microsoft Office Excel, LibreOffice Calc or a Google Spreadsheet.

2. The input sheet files

Under the directory specified by command 'scan' in model file, you can supply Input sheet files prefixed with 'eat' like eat-*.xlsx. The commands are described in following chapter.

3. The bank CSV files

Under the directory specified by command 'scanBank' in model file, you can supply Credit Card Bank CSV statement files. Further detail will be provided in a later chapter.

H. The model commands

1. scan

Fields:

Column	What	Example
A	CommandName	scan
B	Directory	sale

Column A 'CommandName' is used to specify the command.
Column B 'Directory' is used to specify the directory where the input files are located.

Sample: 'scan':

scan	data-family-manual-input				input book directory

2. scan

Fields:

Column	What	Example
A	CommandName	scan
B	Directory	service

Column A 'CommandName' is used to specify the command.
Column B 'Directory' is used to specify the directory where the input files are located.

Sample: 'scan':

scan	C:\Users\yongx\OneDrive\ExcelAccountingTool\eat				oneDrive network drive	replace with yours

2nd sample

3. scanBank

Fields:

Column	What	Example
A	CommandName	scanBank
B	Directory	bank-23-1st-quater

Column A 'CommandName' is used to specify the command.
Column B 'Directory' is used to specify the directory where the bank CSV statement files are located.

Sample: 'scanBank':

scanBank	bank-2023-quarter-1				input CSV directory

4. setDebugMode

Fields:

Column	What	Example
A	CommandName	setDebugMode
B	Flag	yes/no

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to switch the debug mode. The debug mode will enable to write extra log data for examination.

Sample: 'setDebugMode':

setDebugMode	no				specify the flag of if to set the debug mode.

5. ExternalCsvMapFile

Fields:

Column	What	Example
A	CommandName	ExternalCsvMapFile
B	Flag	yes/no
C	FileName	data\csvmaps.xlsx

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not use the map file.
Column C 'FileName' is used to specify the name of the file. This file is supplied by Teknewell. The file is used to translate the bank's credit card CSV file into this tool's data input.

Sample: 'ExternalCsvMapFile':

ExternalCsvMapFile	yes	data\csvmaps.xlsx			specify the csv map file name.

6. SaveInputFiles

Fields:

Column	What	Example
A	CommandName	SaveInputFiles
B	Flag	yes/no

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not save all input files.

Sample: 'SaveInputFiles':

SaveInputFiles	no				note: cell B = flag equals yes or no

7. createOneBook

Fields:

Column	What	Example
A	CommandName	createOneBook
B	Flag	yes/no

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not create a consolidated input one book. This book stores all input sheets as if the user has entered them in one book with the categorizing method we recommend.

Sample: 'createOneBook':

createOneBook	no				note: cell B = flag equals yes or no

8. createAccountHierarchy

Fields:

Column	What	Example
A	CommandName	createAccountHierarchy
B	Flag	yes/no

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not create an account hierarchy book. This book stores all account relationships in a hierarchical way by Command GetFrom and PullFrom.

Sample: 'createAccountHierarchy':

createAccountHierarchy	no				note: cell B = flag equals yes or no

9. cutOffDate

Fields:

Column	What	Example
A	CommandName	cutOffDate
B	Flag	yes/no
C	Month	4
D	Date	30
E	Year	2023

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not create a sheet for InitCommands with a Cut Off Date.
Column C 'Month' is used to specify the month of the Cut Off Date.
Column D 'Date' is used to specify the date of the Cut Off Date.
Column E 'Year' is used to specify the year of the Cut Off Date.

Sample: 'cutOffDate':

cutOffDate	no	1	1	2024	note: cell B = flag of to write Init Commands Book at all.  column C =month	D=date	E=year. This command is for writing out the command 'setInitValue' with last balances for each account as of the cutoff date.

10. useStyleTemplates

Fields:

Column	What	Example
A	CommandName	useStyleTemplates
B	Flag	yes/no
C	FileName	data\csvmaps.xlsx

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not use the map file.
Column C 'FileName' is used to specify the name of the file. The file is used to provide style to the end reports. The sample model downloaded includes such a file. It uses a rule of sheet name matching sheet name.

Sample: 'useStyleTemplates':

useStyleTemplates	yes	data\templateBook1.xlsx			specify the style template file name.

11. createNextCycle

Fields:

Column	What	Example
A	CommandName	createNextCycle
B	Flag	yes/no

Column A 'CommandName' is used to specify the command.
Column B 'Flag' is used to specify the flag value to whether or not execute the command 'prepareSheet'.

Sample: 'createNextCycle':

createNextCycle	no				note: cell B = flag equals yes or no

12. numberOfFilesToKeep

Fields:

Column	What	Example
A	CommandName	numberOfFilesToKeep
B	The number	200

Column A 'CommandName' is used to specify the command.
Column B 'The number' is used to specify an integer number which is used to keep the latest files within the limit when user cleans the history files in directory log, rpt and copy.

Sample: 'numberOfFilesToKeep':

numberOfFilesToKeep	197				minimum 10

I. The input sheets

1. General

The input sheets are a collection of Excel Sheets from 1 or multiple Excel files. Following rules are enforced to qualify as input commands.

The Excel files reside in a directory specified by command 'scan' in Model.
The Excel file names contain a prefix 'eat'.
The sheet names contain a prefix 'Sheet' or 'Cycle'.
On column 1 of each sheet, a valid command name must be there and its syntax must be complying with what defined in this document.

2. Command dependencies

Following listed the order in which the later ones depend on the previous ones.

Define account types.
Define accounts.
Define account modifiers.
Define account header forms.
Define analytical commands.
Define cycle sheet.
Add records on form.

3. Arithmetic Expression

Following is the EAT definition of Arithmetic Expression.

Basic Operands

Operand	Function
Field Name	These field names are the ones that were already defined as a table's column names.
Double	Any valid double value character sequence. For example, 100.15 or -90.07.
PREV	This reserved word indicates the previous row value at the same field is used in calculation.

4 2-operand arithmetic operators

Operator Function

/ Division

* Multiplication

- Subtraction

+ Addition
MathCase Formula
1. Wrap multiple Arithmetic Expression with MathCase Formula.
2. MathCase Formula goes like this: 'MathCase [condition 1]{Arithmetic Expression 1} [condition 2]{Arithmetic Expression 2} [condition 3]{Arithmetic Expression 3} '.
3. This MathCase Formula evaluates each condition from left to right, and if one is failed, continue next one. If one is true, its Arithmetic Expression is returned, and all other conditions that follow will be ignored.
4. This MathCase Formula is only applicable in 'type' command.
General rules
1. The operator order goes: First division, seocond multiplication, third subtraction, forth addition.
2. User can change the operator order by placing parenthesis '(' and ')'.

4. Conditional Logic Expression

Following is the EAT definition of Conditional Expression.

Basic Operands

Operand	Function
Field Name	These field names are the ones that were already defined as a table's column names.
String	Any valid charactor sequence. It does not need to be double quoted. For example, Bank of America. It shouldn't be a Field Name, otherwise it will be treated so.
Double	Any valid double value character sequence. For example, 100.15 or -90.07.

8 none-case-sensitive 2 operand comparison operators
If the 2 operand values are deemed to be double values, the operator is a streight math equivalent one. If one of the 2 operand values is a double value and the other is empty, then the empty one is converted to 0.0, the the operator is a streight math equivalent one. Following table is a description for String Comparison only.

Operator	Function
==	If the 2 strings are not in equal length, it is false; If one of their chars in same index position is not same ('a' is considered the same as 'A' in none-case-sensitive), it is false.
!=	If the 2 strings are not in equal length, it is true; If one of their chars in same index position is not same ('a' is considered the same as 'A' in none-case-sensitive), it is true.
+>	If first string contains second string, it is true, otherwise false.
->	If first string does not contains second string, it is true, otherwise false.
>	First leading and trailing Space chars are removed and second the short string is padded with space char ' ' to the length of the longer string, then compare each char starting from the left most to the right end, if the char at same index position in first string is smaller, it is false. otherwise true;
<	First leading and trailing Space chars are removed and second the short string is padded with space char ' ' to the length of the longer string, then compare each char starting from the left most to the right end, if the char at same index position in first string is larger, it is false. otherwise true;
>=	First apply the rule for operator '==', if false, apply the rule for operator '>'.
<=	First apply the rule for operator '==', if false, apply the rule for operator '<'.

8 case-sensitive 2 operand comparison operators

Operator	Function
#==	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#!=	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#+>	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#->	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#>=	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#<=	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#>	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.
#<	same as the equivalent one above except a sharp char # is added at leading position and it is case-sensitive.

logic operators

Operator	Function
&&	this operator takes 2 operands. If both operands are true, then the expression is true, otherwise false.
\|\|	this operator takes 2 operands. If one of them is true, then the expression is true, otherwise false.
	The operator "&&" is evaluated first and "\|\|" second.
	Use parenthesises '(' and ')' to promote expression priority.

EAT does not offer singular logic operator !
General rules
1. If the expression is true, then the record is evaluated to be picked up.
2. Use a boolean value 'true' or 'false' to arbitrarily indicate the condition value.
3. For logic operators, the operator "&&" is evaluated first, the operator "||" is evaluated second. If you have a different order, use the parenthesis '(' and ')'. The expression in the parenthesises is evaluated first, then proceed to the rest of the entire expression.
4. See example in command CopyAccount below.
5. The char # called Sharp means more detailed and clearer. and Case-sensitive means considering more details. So they do connect in meaning, so good for memory to remember.

J. The input commands

1. DfnType

Fields:

Column	What	Example
A	CommandName	DfnType
B	TypeName	UtilityBill
C	FieldName	Minus
D	FieldName	Plus
E	FieldName	Net\|Calc=Plus-Minus\|
F	FieldName	Balance\|Calc=PREV+Net

Column A 'CommandName' is used to specify the command.
Column B 'TypeName' is used to specify the type name.
Column C 'FieldName' is used to specify the amount deducted.
Column D 'FieldName' is used to specify the amount added.
Column E 'FieldName' is used to specify the net amount.
Column F 'FieldName' is used to specify the incremental amount.

Sample: 'DfnType':

DfnType	PayCheck	CheckNumber	StartDate	EndDate	HideToo	PayRange		Rate	Hours	Gross|Calc=Rate*Hours|	FedTax	SSTax	MCTax	StateTax	FamilyLeave	MedicalLeave	Bonus		MedInsurance	Inv401K		Net|Calc=Gross+Bonus-FedTax-SSTax-MCTax-StateTax-FamilyLeave-MedicalLeave-MedInsurance-Inv401K|	Balance|Calc=PREV+Net|																																							LastField																					Description	PreviousBalance	NewBalance	PreviousBalance2	NewBalance2	Status|Hide=no	Notes

Description:
The command 'type' is the first record a user has to write because a user has to start with an account and an account depends on a type. The command 'type' specifies the fields an account uses. A 'type' record comes with several other features like hiding a column positioning a column or a column calculation. Once a Type is defined one or more account(s) can derive from it.

The reserved word 'PREV':
The key word 'PREV' is reserved and represents a value from previous record in order in the same field.

The reserved word 'ConstE':
The key word 'ConstE' is reserved and represents a value of math constant. The value is 2.7182818284590451. User can use 'ConstE' or type in directly the value.

The reserved word 'ConstPI':
The key word 'ConstPI' is reserved and represents a value of math constant. The value is 3.1415926535897931. User can use 'ConstPI' or type in directly the value.

Hide a field:
In 'Note|Hide=yes' 2 strings are seperated by |. The first string is the field name 'Note' second string is 'Hide=yes'. 'yes' means this field is to be hidden in resulting report. Use 'Hide=no' to do the opposite.

Calculate a field:
In 'Balance|Calc=PREV+Net' 2 strings are seperated by |. The first string is the field name 'Balance' second string is 'Calc=PREV+Net'. The second string 'Calc=PREV+Net' means this field is calculated from the result the sum of the previous value and the value of field 'Net'. Currently the arithmetic calculation only involves the 4 basic operators + - * and / with round brackets '(' and ')' for example Calc=(Plus-Minus)*Scale+PREV'. The char 'c' is reserved to mark the calculation. Refer to Arithmetic Expression above.

Position a field:
In 'Description|Index=5' 2 strings are seperated by |. The first string is the field name 'Description' the second string is 'Index=5'. The second string 'Index=5' means this field is to be shown in position 5 relatively.

Reset balance:
In 'GroupBalance|GCalc=PREV+Net' the formula will just act like 'Calc=PREV+Net' except that the GroupBalance will start from 0.0 when it arrives on a different group of the record key on which the transactions were sorted.

Default fields:

'DateSeqAsKey' combines field Year (4 digits) Month (2 digits) Date (2 digits) and SeqNumber (4 digits) seperated by a '.'. This field serves as a default record and group key which in turn serves other operations. User can use command 'SetKeyField' to set a different key.
'Year'
'Month'
'Date'
'SeqNumber' is an integer number. This allows multiple transactions on the same date.
'Marker' holds the string 'good here' to allow pulling over to another account.
'HyperLinkFieldId' is internally used for HyperLink for field Source Target and LinkTo.
'Source' holds the account name the row transactional data comes from.
'Target' holds the account name the row transactional data to be updated to.

2. DfnType

Get Command:
This coomand 'Get' allows to copy data from a source to this field in all records.

Fields:

Column	What	Example
A	CommandName	DfnType
B	TypeName	UtilityBill
C	FieldName	test02\|Get=UtilityBase\|RateAmount\|2024.8.16.30

Column A 'CommandName' is used to specify the command.
Column B 'TypeName' is used to specify the type name.
Column C 'FieldName' is used to specify the value for test02 by using the command "Get". The | is a second level seperator of |.

Sample: 'DfnType':

DfnType	UtilityElect												StartDate	EndDate	Charge|Calc=D10Electric+ED1Distribution+BaseCharge|	PayAmount	Net|Calc=PayAmount-Charge|	Balance|Calc=PREV+Net	Reading	Kwh|Calc=Reading-LastOf:Reading|	Multiplier	RateElectric	RateDistribution	D10Electric|Calc=Kwh*RateElectric	ED1Distribution|Calc=Kwh*RateDistribution	BaseCharge	Test01	test02|Get=UtilityBase&verbar;RateAmount&verbar;2024.8.16.30														LastField																																									Description	PreviousBalance	NewBalance	PreviousBalance2	NewBalance2	Status|Hide=no	Notes

3. DfnType

Field Directives and Math:
These are the directives and math function names. All directives can be placed one after another in multiple instances in front of a field separated by colon :. For example LastOf:Round:Reading here Reading is the field.

Sample: 'DfnType':

DfnType	UtilityGas												StartDate	EndDate	Charge|Calc=BaseCharge+G10Supply+D10Distribution+Tp2Transportation|	PayAmount	Net|Calc=PayAmount-Charge|	Balance|Calc=PREV+Net	Reading	CcfUsage|Calc=(Reading-LastOf:Reading)*Multiplier|	Multiplier	ThermFactor	Therms	UsageTFAed|Calc=Round:UsageTFAedNr|	UsageTFAedNr|Calc=CcfUsage*ThermFactor|	BaseCharge	RateSupply	RateDistribution	RateTransportation	G10Supply|Calc=UsageTFAed*RateSupply	D10Distribution|Calc=UsageTFAed*RateDistribution	Tp2Transportation|Calc=UsageTFAed*RateTransportation										LastField																																									Description	PreviousBalance	NewBalance	PreviousBalance2	NewBalance2	Status|Hide=no	Notes

LastOf
This directive instructs to get the field value from the previous record in sorting. This directive is placed in front of a field separated by colon : for example 'LastOf:Reading'.

Round
This directive instructs to round the field to an integer. This directive is placed in front of a field separated by colon : for example 'Round:UsageTFAed' which renders no decimals. Following are 3 different variations.

'Round,2:UsageTFAed'. Here ',' is a separator. 2 is the number of decimals.
'Round,MidpointRounding:UsageTFAed'. Here ',' is a separator.MidpointRounding is a type of Round either ToEven or AwayFromZero.
'Round,2,MidpointRounding:UsageTFAed'. Here it has 2 ',' separators. 2 is the number of decimals. MidpointRounding is a type of Round either ToEven or AwayFromZero.

Max
This directive instructs to pick the larger one among 2 values. This directive is placed in front of a field separated by colon : for example 'Max,2ndField:FstField'. Here ',' is the separator. 2ndField is the second field. FstField is the first field.

Min
This directive instructs to pick the smaller one among 2 values. This directive is placed in front of a field separated by colon : for example 'Min,2ndField:FstField'. Here ',' is the separator. 2ndField is the second field. FstField is the first field.

Log
This directive instructs to compute a Log value. This directive is placed in front of a field separated by colon : for example 'Log:Field'. Here the result will be the Log value of Field. There is a variation 'Log,NewBase:Field'. Here the result will be the Log value of Field based on the NewBase. Again ',' is the separator.

Log10
This directive instructs to compute a Log10 value. This directive is placed in front of a field separated by colon : for example 'Log10:Field'. Here the result will be the Log value of Field based on 10.

IEEERemainder
This directive instructs to compute a IEEERemainder value. This directive is placed in front of a field separated by colon : for example 'IEEERemainder,2ndField:FstField'. Here ',' is the separator. 2ndField is the second field. FstField is the first field.

Atan2
This directive instructs to compute a Atan2 value. This directive is placed in front of a field separated by colon : for example 'Atan2,2ndField:FstField'. Here ',' is the separator. 2ndField is the second field. FstField is the first field.

Pow
This directive instructs to compute a Pow value. This directive is placed in front of a field separated by colon : for example 'Pow,2ndField:FstField'. Here ',' is the separator. 2ndField is the second field. FstField is the first field.

Truncate
This directive instructs to compute a Truncate value. This directive is placed in front of a field separated by colon : for example 'Truncate:FstField'. Here FstField is the only field.

Abs
This directive instructs to compute a Abs value. This directive is placed in front of a field separated by colon : for example 'Abs:FstField'. Here FstField is the only field.

Acos
This directive instructs to compute a Acos value. This directive is placed in front of a field separated by colon : for example 'Acos:FstField'. Here FstField is the only field.

Asin
This directive instructs to compute a Asin value. This directive is placed in front of a field separated by colon : for example 'Asin:FstField'. Here FstField is the only field.

Atan
This directive instructs to compute a Atan value. This directive is placed in front of a field separated by colon : for example 'Atan:FstField'. Here FstField is the only field.

Ceiling
This directive instructs to compute a Ceiling value. This directive is placed in front of a field separated by colon : for example 'Ceiling:FstField'. Here FstField is the only field.

Cos
This directive instructs to compute a Cos value. This directive is placed in front of a field separated by colon : for example 'Cos:FstField'. Here FstField is the only field.

Cosh
This directive instructs to compute a Cosh value. This directive is placed in front of a field separated by colon : for example 'Cosh:FstField'. Here FstField is the only field.

Exp
This directive instructs to compute a Exp value. This directive is placed in front of a field separated by colon : for example 'Exp:FstField'. Here FstField is the only field.

Floor
This directive instructs to compute a Floor value. This directive is placed in front of a field separated by colon : for example 'Floor:FstField'. Here FstField is the only field.

Sin
This directive instructs to compute a Sin value. This directive is placed in front of a field separated by colon : for example 'Sin:FstField'. Here FstField is the only field.

Sinh
This directive instructs to compute a Sinh value. This directive is placed in front of a field separated by colon : for example 'Sinh:FstField'. Here FstField is the only field.

Sqrt
This directive instructs to compute a Sqrt value. This directive is placed in front of a field separated by colon : for example 'Sqrt:FstField'. Here FstField is the only field.

Tan
This directive instructs to compute a Tan value. This directive is placed in front of a field separated by colon : for example 'Tan:FstField'. Here FstField is the only field.

Tanh
This directive instructs to compute a Tanh value. This directive is placed in front of a field separated by colon : for example 'Tanh:FstField'. Here FstField is the only field.

4. DfnAccount

Fields:

Column	What	Example
A	CommandName	DfnAccount
B	AccountName	GasBill
C	TypeName	UtilityBill
D	CategoryName	Utility
E	ReportFlag	yes/no
F	Description	any notes

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'TypeName' is used to specify the type name the account is going to derive from
Column D 'CategoryName' is used to specify the category the account falls in. The category is used to group accounts together on reports.
Column E 'ReportFlag' is used to specify the report flag. 'yes' means to show the account records on report, 'no' otherwise.
Column F 'Description' is used to specify notes a user can take and has no impact on reports.

Sample: 'DfnAccount':

DfnAccount	rDrZhang	PayCheck	221	Income	yes	1	first tier	tie to BAChecking

Description:
Defining an account is quite simple. Multiple accounts can be grouped together and be derived from a same 'type'.

5. DfnEntryForm

Fields:

Column	What	Example
A	CommandName	DfnEntryForm
B	AccountName	Checking
C	FormName	Way01
D	FieldName	Year
E	FieldName	Month

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FormName' is used to specify the form name to enter data in.
Column D 'FieldName' is used to specify the field name for which a value can be entered in command 'JnlFormAdd' at the same column.
Column E 'FieldName' is used to specify more fields are listed beyond.

Sample: 'DfnEntryForm':

DfnEntryForm	DevHoa	BestWay		Description	Status	Year	Month	Date	SeqNumber	Marker	Minus	Plus	DisbDate	Pricipal	Net	Balance	PreviousBalance	NewBalance	PreviousBalance2	NewBalance2	Notes

Description:
This command defines a data entry form for an account. A different form can be defined by a different form name at column C. This command is used in conjunction with command 'JnlFormAdd'. The values entered in the latter command must match the columns in this command 'DfnEntryForm'. This command can only be written once for the same form or an warning is logged.

6. DfnEntryForm

Fields:

Column	What	Example
A	CommandName	DfnEntryForm
B	AccountName	Checking
C	FormName	Way01
D	FieldName	Year
E	FieldName	Month

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FormName' is used to specify the form name to enter data in.
Column D 'FieldName' is used to specify the field name for which a value can be entered in command 'JnlFormAdd' at the same column.
Column E 'FieldName' is used to specify more fields are listed beyond.

Sample: 'DfnEntryForm':

DfnEntryForm	DevElect	BestWay		Description	Status	Year	Month	Date	SeqNumber	Marker	Minus	Plus	DisbDate	Pricipal	Net	Balance	PreviousBalance	NewBalance	PreviousBalance2	NewBalance2	Notes

7. DfnEntryForm

Description:
Second sample.

Sample: 'DfnEntryForm':

DfnEntryForm	BASavings	BestWay		Description	Status	Year	Month	Date	SeqNumber	Marker	Minus	Plus	EntryCategory	PreviousBalance	NewBalance	PreviousBalance2	NewBalance2	Notes	CheckNumber

8. JnlEasyAdd

Fields:

Column	What	Example
A	CommandName	JnlEasyAdd
B	AccountName	Checking
C	FieldName	Year
D	FieldValue	2023

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name to enter data for.
Column D 'FieldValue' is used to specify the field value for the field right before it on the left.

Sample: 'JnlEasyAdd':

JnlEasyAdd	CornerStone	Description	rate:0% no longer see account balance on web site	wait for Fed Servicing to open new account	Status		Year	2018	Month	8	Date	18	SeqNumber	100	Minus		Plus	1750	Marker	good here	PreviousBalance	7770

Description:
This is a free style of data entry method. Starting at cell C the field name and value appear as a pair one after another. If user needed to insert blank cell a pair of blank cells must be entered so that all the pairs start at a column of odd number like 3 5 etc. Here column C is odd number 3.

9. JnlEasyAdd

Description:
Second sample.

Sample: 'JnlEasyAdd':

JnlEasyAdd	eCollege1Fall	Description	Campus Health Fee - Health Svcs	Status		Year	2018	Month	7	Date	7	SeqNumber	1			Category	1. Charge	SubGroup	2			Minus	520	Plus	0	PreviousBalance	0	Marker

10. JnlEasyAdd

Description:
Third sample with formula 'PullFrom'. This 'PullFrom' formula has 3 or 4 fields separated by char '|'. The 4th field is optional can be omitted. When omitted the default key phrase 'good here' is used to validate the row in which a value is pull from or otherwise the user key word is used.

Sample: 'JnlEasyAdd':

JnlEasyAdd	Cash	Description	BASavings			Year	2020	Month	1	Date	1	SeqNumber	901	Plus	PullFrom|BASavings|Balance	Marker	good here

11. JnlFormAdd

Fields:

Column	What	Example
A	CommandName	JnlFormAdd
B	AccountName	Checking
C	FormName	Way01
D	FieldValue	Year
E	FieldName	Month

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FormName' is used to specify the form name to enter data in.
Column D 'FieldValue' is used to specify the field value that can be entered according to its form.
Column E 'FieldName' is used to specify more field values are listed beyond.

Sample: 'JnlFormAdd':

JnlFormAdd	BASavings	BestWay	302			2022	13	31	302		1		ReconcileAdjustment

Description:
This command allows user to enter transactional record values according to its form defined in command 'DfnEntryForm'.

12. JnlEasyRepeat

Sample: 'JnlEasyRepeat':

JnlEasyRepeat	BASavings		2	Status	GetFrom|yAlexanT|Status	Year	Copy	SeqNumber	2	Plus	GetFrom|yAlexanT|Net	EntryCategory	Income Alexander

Description:
This command has the same syntax as the command 'Add'. It will duplicates an 'Add' command in a sheet prefixed with 'JnlEasyRepeat' provided it has the same SeqNumber. User can also utilize the preserved word 'copy' in the field 'Year' to copy the year month and date values to the duplicate.

13. JnlFormRepeat

Sample: 'JnlFormRepeat':

JnlFormRepeat	BASavings	BestWay	3		GetFrom|yAlexanT|Status	Copy			3			GetFrom|yAlexanT|Net	Income Alexander

Description:
This command has the same syntax as the command 'AddRecord'. It will duplicates an 'AddRecord' command in a sheet prefixed with 'Cycle' provided it has the same SeqNumber. User can also utilize the preserved word 'copy' in the field 'Year' to copy the year month and date values to the duplicate. It inherits the Header form definition for account named in cell B.

14. JnlFormSubRepeat

Sample: 'JnlFormSubRepeat':

JnlFormSubRepeat	Peter|checking	bestway			From Peter 1	Copy			100				GetFrom|j_gas|Minus

Description:
This command is a variation of the command JnlFormRepeat. Its second column B was oringinally for an account name but now for a conbination of a prefix key word and an account name separated by char |. but user could also name the sheet as CycleJohn2024March. So user writes in cell B the kew word 'John|AccountName' then this command is only copied to sheet prefixed by 'CycleJohn'. Note here 'John' becomes a second key word after first key word 'cycle'. All cells after to the right remain the same. It inherits the Header form definition for account named in cell B's second string.

15. JnlAddByLink

Fields:

Column	What	Example
A	CommandName	JnlAddByLink
B	SourceAccountName	DevGasss
C	SourceFieldName	Minus
D	TargetAccountName	BaChecking
E	TargetFieldName	Minus
F	MatchWord	Link
G	FieldName	Category
H	FieldValue	Bill

Column A 'CommandName' is used to specify the command.
Column B 'SourceAccountName' is used to specify the source account name.
Column C 'SourceFieldName' is used to specify the source account field name.
Column D 'TargetAccountName' is used to specify the target account name.
Column E 'TargetFieldName' is used to specify target account field name.
Column F 'MatchWord' is used to specify the matching word in field Marker used to validate a transaction to move the field value from source to target.
Column G 'FieldName' is used to specify the field name to be appended to the transaction.
Column H 'FieldValue' is used to specify the field value to be appended to the transaction.
Column I 'maybe more' is used to specify maybe more

Sample: 'JnlAddByLink':

JnlAddByLink	DevGasss	Minus	BAChecking	Minus	Link	EntryCategory	Devens gas added by JnlAddByLink

Description:
This is the second method to move a field data to a target field. The first method is to use the command 'JnlFormRepeat'. These 2 methods should be used exclusively. The column F specify a match word which should also be written in a record's Marker field so that to allow the record to be validated. Starting at column G pairs of field name and value can be attached. Empty pairs can be inserted too but all must be entered in pairs immediately one after another.

16. GroupSubTotalForChart

Fields:

Column	What	Example
A	CommandName	GroupSubTotalForChart
B	AccountName	Checking
C	FieldName(s)	Year\|Month
D	FieldName(s)	Plus\|Minus

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName(s)' is used to specify the field name(s) to group upon. The field names are seperated by a pipe '|'.
Column D 'FieldName(s)' is used to specify the field name(s) to get total on group. The field names are seperated by a pipe '|'.

Sample: 'GroupSubTotalForChart':

GroupSubTotalForChart	BAChecking	Year|Month	Minus|Plus

Description:
The result of the group totals are appended at the bottom of the account in report. User can utilize the Excel graph function to draw a picture.

17. SetInitValue

Fields:

Column	What	Example
A	CommandName	SetInitValue
B	AccountName	BaChecking
C	FieldName	Balance
D	Value	103.67

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name of a field at which an initial value will be set.
Column D 'Value' is used to specify a value as an initial for the field.

Sample: 'SetInitValue':

SetInitValue	USBank20	CountDownBalance	16	as of 04/01/2022

Description:
An accumulative field like 'Balance' is increasing by adding current net value to the previous value. So the very first previous value is called an initial value and user can set it with this command.

18. SetKeyField

Fields:

Column	What	Example
A	CommandName	SetKeyField
B	AccountName	BaChecking
C	FieldName	Category

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name of a field which will serve as a key. Or multiple field names separated by '|', like Category|Location.

Sample: 'SetKeyField':

SetKeyField	eCollege1Spring	CategorY

Description:
User can choose a field other than the Year Month Date and SeqNumber combination as a key. The records of an account in report will be sorted by the key.

19. SetKeyField

Description:
The second sample with multiple key fields.

Sample: 'SetKeyField':

SetKeyField	eCollege2Fall	Category|SubGroup

20. SetGroupField

Fields:

Column	What	Example
A	CommandName	SetGroupField
B	AccountName	BaChecking
C	FieldName	Category

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name of a field which will serve as a group key. Or multiple field names separated by '|', like Category|Location.

Sample: 'SetGroupField':

SetGroupField	eCollege2Fall	Category

Description:
The default group key filed is the Year Month Date and SeqNumber combination which is the same as the sorting key. User must use this command in order to use a different field as the grouping field. Note the sorting key and grouping key are 2 different functions.

21. SetOrderIndex

Fields:

Column	What	Example
A	CommandName	SetOrderIndex
B	AccountName	DevElect
C	FieldName	Month
D	Value	12

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name of a field which will assume a different index in order on report.
Column D 'Value' is used to specify the value of an integer which serves as an index on which the fields are sorted on report.

Sample: 'SetOrderIndex':

SetOrderIndex	DevElect	Marker	12

Description:
This command allows user to move a field of an account to a new position on report.

22. SetVisibility

Fields:

Column	What	Example
A	CommandName	SetVisibility
B	AccountName	DevElect
C	FieldName	Month
D	Value	yes/no

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name of a field which will be hidden on report.
Column D 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to hind the field, 'no' is otherwise.

Sample: 'SetVisibility':

SetVisibility	DevElect	Month	no

Description:
This command allows user to hind a field of an account on report.

23. SetOrientation

Fields:

Column	What	Example
A	CommandName	SetOrientation
B	AccountName	TaxLine16
C	Orientation	down

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Orientation' is used to specify the orientation. This takes either 'down' or 'right'. 'right' is the default, and it means to print from left to right. 'down' means to print from top to bottom.

Sample: 'SetOrientation':

SetOrientation	AccountOfLine16WsCalc	down

Description:
Use this command when there are many columns and a few rows. This provides better readability.

24. SetCalculationPrint

Fields:

Column	What	Example
A	CommandName	SetCalculationPrint
B	AccountName	TaxLine16
C	Flag	yes
D	Row	5

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Flag' is used to specify the flag. This takes either 'yes' or 'no'. 'no' is the default, and it means not to print the analytic calculation formulas. 'yes' means the otherwise.
Column D 'Row' is used to specify the row number. This takes an integer, an value 1 or beyong.

Sample: 'SetCalculationPrint':

SetCalculationPrint	AccountOfLine16WsCalc	yes	5

Description:
Use this command when wanting to see the formulas of each fields on the report. User can check the 'debug' box and the field dependencies will be printed in the log file.

25. SetAccountReportStartRowColumn

Fields:

Column	What	Example
A	CommandName	SetAccountReportStartRowColumn
B	AccountName	DevElect
C	Value	7
D	Value	3

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of an integer which serves as a row number at which the account records start to be shown.
Column D 'Value' is used to specify the value of an integer which serves as a column number at which the account records are to be shown starting.

Sample: 'SetAccountReportStartRowColumn':

SetAccountReportStartRowColumn	BAChecking	7	3

Description:
This command allows user to specify the starting row and column number the account records start to be shown.

26. SetFieldIndexRow

Fields:

Column	What	Example
A	CommandName	SetFieldIndexRow
B	AccountName	DevElect
C	Value	yes/no
D	Value	1

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to show the index row , 'no' is otherwise.
Column D 'Value' is used to specify the value of an integer which serves as a row number to show the index row.

Sample: 'SetFieldIndexRow':

SetFieldIndexRow	BAChecking	no	1

Description:
This command allows user to write the indexes assigned to fields on a row specified.

27. SetFieldNameRow

Fields:

Column	What	Example
A	CommandName	SetFieldNameRow
B	AccountName	DevElect
C	Value	yes/no
D	Value	2

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to show the field name row , 'no' is otherwise.
Column D 'Value' is used to specify the value of an integer which serves as a row number to show the field name row.

Sample: 'SetFieldNameRow':

SetFieldNameRow	BAChecking	no	2

Description:
This command allows user to write the field names on a row specified.

28. SetColumnNumberRow

Fields:

Column	What	Example
A	CommandName	SetColumnNumberRow
B	AccountName	DevElect
C	Value	yes/no
D	Value	3

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to show the number row , 'no' is otherwise.
Column D 'Value' is used to specify the value of an integer which serves as a row number to show the number row.

Sample: 'SetColumnNumberRow':

SetColumnNumberRow	BAChecking	no	3

Description:
This command allows user to write the number row which simply count and show integers from 1 to N where 1 is column A 2 is B etc.

29. SetInitialValueRow

Fields:

Column	What	Example
A	CommandName	SetInitialValueRow
B	AccountName	DevElect
C	Value	yes/no
D	Value	6

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to show the initial value , 'no' is otherwise.
Column D 'Value' is used to specify the value of an integer which serves as a row number to show the initial value.

Sample: 'SetInitialValueRow':

SetInitialValueRow	rAmeriFund	yes	6

Description:
This command allows user to write the initial value onto a row on report. The column is decided by the field name the value is associated.

30. SetInitialValueRow

Fields:

Column	What	Example
A	CommandName	SetInitialValueRow
B	AccountName	DevElect
C	Value	yes/no
D	Value	6

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to show the initial value , 'no' is otherwise.
Column D 'Value' is used to specify the value of an integer which serves as a row number to show the initial value.

Sample: 'SetInitialValueRow':

SetInitialValueRow	BAChecking	yes	6

Description:
This command allows user to write the initial value onto a row on report. The column is decided by the field name the value is associated.

31. SetNavigationColumn

Fields:

Column	What	Example
A	CommandName	SetNavigationColumn
B	AccountName	DevElect
C	Value	yes/no
D	Value	2

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Value' is used to specify the value of 'yes' or 'no'. 'yes' is to write the navigational hyperlinks , 'no' is otherwise.
Column D 'Value' is used to specify the value of an integer which serves as a column position the HyperLinks will be written at on report.

Sample: 'SetNavigationColumn':

SetNavigationColumn	BAChecking	no	1

Description:
This command allows user to write the Sheet Navigational Hyperlinks on a specified column.

32. SetStartRowColumnForGSC

Fields:

Column	What	Example
A	CommandName	SetStartRowColumnForGSC
B	Account	BaChecking
C	Row	5
D	Column	F

Column A 'CommandName' is used to specify the command.
Column B 'Account' is used to specify the account name.
Column C 'Row' is used to specify the row number starting at 1. For GSC, if it is within the same account, the row number is 2 row below the main report. This parameter is ignored. Otherwise the default number 7 is used.
Column D 'Column' is used to specify the column letter or number starting at 1. This command allows user to move the cell block horizontally.

Sample: 'SetStartRowColumnForGSC':

SetStartRowColumnForGSC	BAChecking		F

Description:
This command allows to move the block up and down left and right. The block is generated by commnad 'GroupSubTotalForChart'.

… … … … … …

33. SetGroupFirstRowColor

Fields:

Column	What	Example
A	CommandName	SetGroupFirstRowColor
B	AccountName	BaChecking
C	FieldName	Month
D	ColorName	Yellow

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'FieldName' is used to specify the field name used to mark the first row with a background color.
Column D 'ColorName' is used to specify the color name used to mark the first row in a group identified by the field above. The color names are listed at the end of this document.

Sample: 'SetGroupFirstRowColor':

SetGroupFirstRowColor	BAChecking	Month	Red

Description:
Marking the first row of groups makes account reading more productive.

34. SetSelectedRow

Fields:

Column	What	Example
A	CommandName	SetSelectedRow
B	AccountName	BaChecking
C	Method	Bottom
D	An integer	8

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.
Column C 'Method' is used to specify the method type. The type is either Top or Bottom.
Column D 'An integer' is used to specify a integer value that is used to add to the Top row 1 or the Bottom row.

Sample: 'SetSelectedRow':

SetSelectedRow	BASavings	Bottom	1

Description:
Without this command a sheet is normally displayed from top. User can use this command to select another row for intial display. At cell C Top is for calculating the row number of a selected row which is away from row 1 plus the integer defined in cell D. If a negative integer is specified the selected row is at row 1. At cell C Bottom is for calculating the row number of a selected row which is away from bottom row plus the integer defined in cell D. Using a negative integer to select a row above bottom row. If the resulting row number is negative the selected row is at row 1.

35. SetFirstAccount

Fields:

Column	What	Example
A	CommandName	SetFirstAccount
B	AccountName	BaChecking

Column A 'CommandName' is used to specify the command.
Column B 'AccountName' is used to specify the account name.

Sample: 'SetFirstAccount':

SetFirstAccount	HistoryOfTotalx2

Description:
When the report is brought up which sheet is to be displayed first? So use this command to specify.

36. ActDiscardRowAt

Fields:

Column	What	Example
A	CommandName	ActDiscardRowAt
B	OrderIndex	4
C	AccountName	DevElect
D	Conditional Expression	Net==0

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'AccountName' is used to specify the account name.
Column D 'Conditional Expression' is used to specify the conditional expression upon which the records are evaluated to be descarded or not.

Sample: 'ActDiscardRowAt':

ActDiscardRowAt	5	AESuccess	Net==0

Description:
This command allows user to specify whether to skip a record if the conditional expression is true. For example if the calculation 'Net==0' is true the record is not shown on report (discarded). Refer Conditional Expression above.

37. ActBcDiscardRowAt

Fields:

Column	What	Example
A	CommandName	ActBcDiscardRowAt
B	OrderIndex	4
C	Name	Value

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'Name' is used to specify the other parameter to follow.

Sample: 'ActBcDiscardRowAt':

ActBcDiscardRowAt	5	AESuccess	Net==0

Description:
This command has exact same effects of the command ActDiscardRowAt except it is to be executed before the data transfer and math calculation.

38. ActCopyAccount

Fields:

Column	What	Example
A	CommandName	ActCopyAccount
B	OrderIndex	4
C	SourceAccountName	BaChecking
D	TargetAccountName	BaCheckingByCategory
E	Conditional Expression	FieldName> 100

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'SourceAccountName' is used to specify the source account name of the account from which to copy data to target account.
Column D 'TargetAccountName' is used to specify the target account name of the account to which to copy data from a source account.
Column E 'Conditional Expression' is used to specify how to pick records. This cell is optional. Leave it blank for all records. See example below and the definition of Conditional Expression above.

Sample: 'ActCopyAccount':

ActCopyAccount	1	BACheckinG	BACheckingSortByCategory

Description:
This command simply copies an account records to another. The order index indicates all action commands are executed in order by the index.

39. ActCopyAccount

Description:
The second sample with record-picking conditional expression

Sample: 'ActCopyAccount':

ActCopyAccount	2	eCollege4Spring	eCollegeOnCategory	Category!=0. Leftover

40. ActCopyAccount

Description:
The third sample with record-picking conditional expression

Sample: 'ActCopyAccount':

ActCopyAccount	3	BAChecking	BACheching_CopyMatched	EntryCategory+>gas && Minus>100

41. ActBcCopyAccount

Fields:

Column	What	Example
A	CommandName	ActBcCopyAccount
B	OrderIndex	4
C	Name	Value

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'Name' is used to specify the other parameter to follow.

Sample: 'ActBcCopyAccount':

ActBcCopyAccount	1	BACheckinG	BACheckingSortByCategory

Description:
This command has exact same effects of the command ActCopyAccount except it is to be executed before the data transfer and math calculation.

42. ActJoinAccounts

Fields:

Column	What	Example
A	CommandName	ActJoinAccounts
B	OrderIndex	16
C	SourceAccountName	BaChecking
D	SourceAccountName	BaSavings
E	TargetAccountName	BaCheckingSavingsJoined
F	KeyFieldNames	Category\|Net
G	JoinTypes	yours\|mm
H	FieldControls	BaChecking\|Minus\|none#BaChecking\|Plus\|Credit

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'SourceAccountName' is used to specify the account name of the first source account from which the records are joined with the second account into a traget account.
Column D 'SourceAccountName' is used to specify the account name of the second source account from which the records are joined with the first account into a traget account.
Column E 'TargetAccountName' is used to specify the account name of the target account into which the 2 source accouts are joined.
Column F 'KeyFieldNames' is used to specify the key field names of both source accounts.
Column G 'JoinTypes' is used to specify the types of joinning methods.
Column H 'FieldControls' is used to specify Additional rules to deal with other fields.

Sample: 'ActJoinAccounts':

ActJoinAccounts	6	BACheching_CopyMatched	BACheCkingX2TextJoin	BACheCkingX2TextJoinResult	EntryCategory	1m|yours	BACheching_CopyMatched|EntryCategory|none#BACheCkingX2TextJoin|Minus|MinusX3#BACheCkingX2TextJoin|Plus|PlusX3#BACheCkingX2TextJoin|Description|none#BACheching_CopyMatched|Description|none

Description:
This command joins 2 source accounts into 1 target account.

Key Fields:
The key fields are used to join records. If multiple fields were to be used use '|' to separate the field's names. All accounts must have the same key fields.

Join Types:
The first type is 'mine'. The second type is 'yours'. The third type is 'mm m1 1m'. The adoption of word 'mine' and 'yours' is derived from a metaphor which is saying that the user is the owner of the first account of 'mine' and he is trying to join the first account to the second account which is owned by a second person of 'yours' .
'mine' means the records are of first account and have no match from second account. 'yours' means the records are of second account and have no match from first account.
The third type is 'mm m1 1m'. This type means the records are matching from both source accounts.
'mm' means 'many to many' and the matched records are joined completely. For example if there are 2 records from first account and 3 records from second account that they share same key value there will be 6 joined records in the traget account.
'm1' means 'many to 1' and the matched records are joined partially. For example if there are 2 records from first account and 3 records from second account that they share same key value there will only be 2 joined records in the traget account 2 from first account and 1 from second account.
'1m' means '1 to many' and the matched records are joined partially. For example if there are 2 records from first account and 3 records from second account that they share same key value there will only be 3 joined records in the traget account 1 from first account and 3 from second account.
mm' 'm1' and '1m' are mutually exclusive meaning only one can be used at a time. So 'mine' 'yours' and one of the 'mm' 'm1' and '1m' can be used together using a seperator '|' for example 'your|m1' or 'mine|1m' etc.

FieldControls:
Without the additional FieldControls the default function is to move data from a source field to a matching target field. All source fields that are not in the target account are abandoned.
The rule is written in format 'account|field|field' or 'account|field|none'. The format has 3 strings. The first string is the account name. The second string is a field from the account of first string. The third string is either the reserved word 'none' or a target field name. The word 'none' indicates the field from the first string account will not participate in the 'join'. A target field name indicates the field from the first string account will be joined over to the target field (renamed).
Multiple rules are concatenated using the seperator char '#'.

More Illustration:

43. ActBcJoinAccounts

Fields:

Column	What	Example
A	CommandName	ActBcJoinAccounts
B	OrderIndex	4
C	Name	Value

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'Name' is used to specify the other parameter to follow.

Sample: 'ActBcJoinAccounts':

ActBcJoinAccounts	6	BACheching_CopyMatched	BACheCkingX2TextJoin	BACheCkingX2TextJoinResult	EntryCategory	1m|yours	BACheching_CopyMatched|EntryCategory|none#BACheCkingX2TextJoin|Minus|MinusX3#BACheCkingX2TextJoin|Plus|PlusX3#BACheCkingX2TextJoin|Description|none#BACheching_CopyMatched|Description|none

Description:
This command has exact same effects of the command ActJoinAccounts except it is to be executed before the data transfer and math calculation.

44. ActSortAccount

Fields:

Column	What	Example
A	CommandName	ActSortAccount
B	OrderIndex	4
C	AccountName	DevElect
D	Key fields	FieldName1:byString\|FieldName2:byDouble

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'AccountName' is used to specify the account name.
Column D 'Key fields' is used to specify the key fields upon which the records are sorted.

Sample: 'ActSortAccount':

ActSortAccount	50	DrugInventory	name|price:byDouble

Description:
This command allows user to sort the account in a different way. The key fields are separated by pipe. For each field user can append a colon ':' and either byString or byDouble as in example above. This allows the sorting algorithm to compare by string or by double value.

45. ActBcSortAccount

Fields:

Column	What	Example
A	CommandName	ActBcSortAccount
B	OrderIndex	4
C	Name	Value

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'Name' is used to specify the other parameter to follow.

Sample: 'ActBcSortAccount':

ActBcSortAccount	50	DrugInventory	name|price:byDouble

Description:
This command has exact same effects of the command ActSortAccount except it is to be executed before the data transfer and math calculation.

46. ActWriteGroupSubTotalForChart

Fields:

Column	What	Example
A	CommandName	ActWriteGroupSubTotalForChart
B	OrderIndex	4
C	AccountName	DevElect
D	FieldName	Year
E	FieldName	w2_1_WagesTipsComps
F	AccountName	yW2Group

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'AccountName' is used to specify the source account name.
Column D 'FieldName' is used to specify the field name on which the values of the next field are grouped.
Column E 'FieldName' is used to specify the field name on which the values are summarized and compared to previous period.
Column F 'AccountName' is used to specify the target account name. This field is optional. If it is missing, the source account is also the target account.

Sample: 'ActWriteGroupSubTotalForChart':

ActWriteGroupSubTotalForChart	7	yW2	Year	w2_1_WagesTipsComps	yW2Group

Description:
This command groups records on fields specified in cell D and summarize the values of fields specified in cell E and also compares the summary to previous group or period. The command presents the resulting table to a sheet belong to an account specified by cell F. This target account usually contains no records of its own.

47. ActBcWriteGroupSubtotalForChart

Fields:

Column	What	Example
A	CommandName	ActBcWriteGroupSubtotalForChart
B	OrderIndex	4
C	Name	Value

Column A 'CommandName' is used to specify the command.
Column B 'OrderIndex' is used to specify an integer which serves as value on which all action commands are sorted and executed in order.
Column C 'Name' is used to specify the other parameter to follow.

Sample: 'ActBcWriteGroupSubtotalForChart':

ActBcWriteGroupSubtotalForChart	7	yW2	Year	w2_1_WagesTipsComps	yW2Group

Description:
This command has exact same effects of the command ActWriteGroupSubtotalForChart except it is to be executed before the data transfer and math calculation.

48. OneFileCopy

Fields:

Column	What	Example
A	CommandName	OneFileCopy
B	DirectoryName	OneFile
C	Flag	yes

Column A 'CommandName' is used to specify the command.
Column B 'DirectoryName' is used to specify the directory name.
Column C 'Flag' is used to specify the flag of indicating whether or not to delete the existing directory. The value is either 'yes' or 'no'.

Sample: 'OneFileCopy':

OneFileCopy	OneFileFamily	yes

Description:
This command will copy the OneFile to the directory and the file name is added and prefixed by 'eat-'. Note the directory should be in test thus temporary. It should not hold any permanent valuable files. This command makes it convenient for user to test the OneFile model. The OneFile model is a equivalent model to a source model. It was created by assembling all input commands of the source model and inject into the OneFile model.

49. PrepareCycle

Fields:

Column	What	Example
A	CommandName	PrepareCycle
B	SheetName	Cycle2023May
C	SheetName	Cycle2023June
D	CommandNames	Axdd\|AxddRecord
E	First of the Pair of Type 1	column\|f
F	Second of the Pair of Type 1	value\|empty
G	First of the Pair of Type 2	field\|PreviousBalance
H	Second of the Pair of Type 2	fieldValue\|NewBalance

Column A 'CommandName' is used to specify the command.
Column B 'SheetName' is used to specify the sheet name of a sheet which is based to copy from as source.
Column C 'SheetName' is used to specify the sheet name of a sheet which is to be created by copying a source sheet intoi it.
Column D 'CommandNames' is used to specify command names of the commands of which their fields are to be modified based on the formulas in pairs that follow.
Column E 'First of the Pair of Type 1' is used to specify the formula which consists 2 strings seperated by |. The first is reserved name 'column' which indicates the second is a column letter like 'f' etc.
Column F 'Second of the Pair of Type 1' is used to specify the formula which consists 2 strings seperated by |. The first is reserved name 'value' which indicates the second is a pure value. The string 'empty' indicates nothing in value.
Column G 'First of the Pair of Type 2' is used to specify the formula which consists 2 strings seperated by |. The first is reserved name 'field' which indicates the second is a field defined in 'type'. The field is to be updated from the second of the pair.
Column H 'Second of the Pair of Type 2' is used to specify the formula which consists 2 strings seperated by |. The first is reserved name 'filedvalue' which indicates the second is also a field name. This field is pulled from its value and the value is updated to the field defined in the first of the pair.

Sample: 'PrepareCycle':

PrepareCycle	Cycle2024July	Cycle2024August	Axdd|AxddRecord	column|f	value|empty	column|h	Value|8			field|PreviousBalance	fieldValue|NewBalance	field|PreviousBalance2	fieldValue|NewBalance2

Description:
This command will create a new cycle sheet for a new cycle. The new cycle sheet will most inherits the previous cycle values except the updates made through the formulas. This enables the next cycle forecasting very effectively. The formula pairs are to be placed starting at cell E. Empty pairs can be placed in between. They must be appearing in pairs. There is a UI CheckBox on page Model. User can disable the generation of the new cycle sheet even though the command is present as input.

K. The dll commands

1. DllEat

Fields:

Column	What	Example
A	CommandName	DllEat
B	DllFileName	codeSnippet.dll
C	NameSpace	CodeSnippet
D	ClassName	Class1
E	MethodName	writeCodeSnippet
F	SheetName	CodeSpippet
G	AccountName	BaChecking
H	Extra data 1	data1
I	Extra data 2	data2
J	Extra data 3	data3

Column A 'CommandName' is used to specify the command.
Column B 'DllFileName' is used to specify the dll file name with extension.
Column C 'NameSpace' is used to specify the NameSpace name in the dll project.
Column D 'ClassName' is used to specify the class name within the NameSpace.
Column E 'MethodName' is used to specify the method name to which the main program EatUi.exe will calll. Copy the method prototype from below.
Column F 'SheetName' is used to specify the sheet name.
Column G 'AccountName' is used to specify the account name. User can place more than 1 account names here , the names are separated by a string '[0]'. For each account, user can add a condition expression after the account name and a separator string '[1]'. Here is an example 'AccountName1[1]fieldName==aValue[0]AccountName2[1]fieldName2==aValue2'. If they are multiple account names, the multiple method prototype is used instead of the single one. Refer to below for the second prototype.
Column H 'Extra data 1' is used to specify the additional data at user‘s disposal, optional.
Column I 'Extra data 2' is used to specify the additional data at user‘s disposal, optional.
Column J 'Extra data 3' is used to specify the additional data at user‘s disposal, optional. No limit is set for how many data row to follow.

Sample: 'DllEat':

DllEat	eatExtdll.dll	EatExtDll	EatExtDllSampleCode	MethodFor_EatExtDll	CS_x02	ActCodeSnipet02	StorageClassCodeSnipetByDllx2	dataType	dataName	dataValue

Description:
Please copy the method prototype to build a dll project. The returned array will be presented in a sheet named in field F. 3 dll app code files are presented as example below. When creating a dll project in Visual Studio 2022 use the project type 'Class Library (.NET Framework)'. The dll function includes a delegate function at the end. User can call it to get more data. This delegate function is defined in a dll named EatUserDllExtension. User must includes it as a reference in project. The delegate name is AskForMore.

Dll Sample Code for Command DllEat:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using EatUserDllExtension;

namespace EatExtDll
{
    public class EatExtDllSampleCode
    {
        public String MethodFor_EatExtDll(String[] UserCommand	List<String[]> AccountRecords	String[] FieldNames	int[] FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore)
        {
            //ReturnRecords.Add(String.Format("{0}\t{1}"	123	"abc"));
            //ReturnRecords.Add(String.Format("{0}\t{1}"	124	"xyz"));
            //ReturnRecords.Add(String.Format("{0}\t{1}"	127	"xyz"));
            //return "abc";
            if (UserCommand == null) return "missing argument UserCommand";
            if (AccountRecords == null) return "missing argument AccountRecords";
            if (FieldNames == null) return "missing argument FieldNames";
            if (FieldPositions == null) return "missing argument FieldPositions";
            if (ReturnRecords == null) return "missing argument ReturnRecords";
            if (UserCommand.Length < 11) return "wrong number of arguments";
            if (UserCommand[7].Length == 0) return "missing argument at cell H";
            if (UserCommand[8].Length == 0) return "missing argument at cell I";
            if (UserCommand[9].Length == 0) return "missing argument at cell J";
            if (UserCommand[10].Length == 0) return "missing argument at cell K";

            int p1 = CommonTools.getPositionByName(UserCommand[8].Trim()	FieldNames	FieldPositions);
            int p2 = CommonTools.getPositionByName(UserCommand[9].Trim()	FieldNames	FieldPositions);
            int p3 = CommonTools.getPositionByName(UserCommand[10].Trim()	FieldNames	FieldPositions);
            string[] r1 = new string[1]; r1[0] = "1234.8794"; //ReturnRecords.Add(r1);
            r1 = new string[1]; r1[0] = String.Format("internal class {0}"	UserCommand[7].Trim()); ReturnRecords.Add(r1);
            r1 = new string[1]; r1[0] = "{"; ReturnRecords.Add(r1);
            foreach (string[] rc in AccountRecords)
            {
                r1 = new string[2]; r1[1] = String.Format("{0} {1} = {2};"	rc[p1].Trim()	rc[p2].Trim()	rc[p3].Trim()); ReturnRecords.Add(r1);
            }
            foreach (string[] rc in AccountRecords)
            {
                r1 = new string[2]; r1[1] = String.Format("public {0} p_{1} {{ get {{ return {1}; }} set {{ {1} = value; }} }}"	rc[p1].Trim()	rc[p2].Trim()); ReturnRecords.Add(r1);
            }
            r1 = new string[2]; r1[1] = "public void setValues ("; ReturnRecords.Add(r1);

            bool first = true;
            foreach (string[] rc in AccountRecords)
            {
                if (!first)
                {
                    r1 = new string[3]; r1[2] = String.Format("	{0} p{1} = {2}"	rc[p1].Trim()	rc[p2].Trim()	rc[p3].Trim()); ReturnRecords.Add(r1);
                }
                else
                {
                    r1 = new string[3]; r1[2] = String.Format("{0} p{1} = {2}"	rc[p1].Trim()	rc[p2].Trim()	rc[p3].Trim()); ReturnRecords.Add(r1);
                }
                first = false;
            }
            r1 = new string[2]; r1[1] = ")"; ReturnRecords.Add(r1);
            r1 = new string[2]; r1[1] = "{"; ReturnRecords.Add(r1);

            foreach (string[] rc in AccountRecords)
            {
                r1 = new string[3]; r1[2] = String.Format("{1} = p{1};"	rc[p1].Trim()	rc[p2].Trim()	rc[p3].Trim()); ReturnRecords.Add(r1);
            }
            r1 = new string[2]; r1[1] = "}"; ReturnRecords.Add(r1);
            r1 = new string[2]; r1[1] = "/*"; ReturnRecords.Add(r1);
            r1 = new string[2]; r1[1] = "setValues ("; ReturnRecords.Add(r1);
            first = true;
            foreach (string[] rc in AccountRecords)
            {
                if (!first)
                {
                    r1 = new string[3]; r1[2] = String.Format("//	p{1} : {2}"	rc[p1].Trim()	rc[p2].Trim()	rc[p3].Trim()); ReturnRecords.Add(r1);
                }
                else
                {
                    r1 = new string[3]; r1[2] = String.Format("//p{1} : {2}"	rc[p1].Trim()	rc[p2].Trim()	rc[p3].Trim()); ReturnRecords.Add(r1);
                }
                first = false;
            }
            r1 = new string[2]; r1[1] = ");"; ReturnRecords.Add(r1);
            r1 = new string[2]; r1[1] = "*/"; ReturnRecords.Add(r1);
            r1 = new string[1]; r1[0] = "}"; ReturnRecords.Add(r1);

            return null; // means good
        }
    }
}

Dll Support Library:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace EatUserDllExtension
{
    public delegate String AskForMore(String AccountName	String Condition	List<String[]> AccountRecords	ref String[] FieldNames	ref int[] FieldPositions);

    public static class CommonTools
    {
        //common for all cs files
        public static int getPositionByName(string n	String[] FieldNames	int[] FieldPositions)
        {
            int p = 0;
            foreach (string af in FieldNames)
            {
                if (af.Trim().ToUpper() == n.Trim().ToUpper())
                {
                    return FieldPositions[p];
                }
                p++;
            }
            return -1;
        }
        public static String getValueByName(String[] record	string n	String[] FieldNames	int[] FieldPositions)
        {
            int p1 = getPositionByName(n	FieldNames	FieldPositions);
            if (p1 == -1)
            {
                return "nf"; // not found
            }
            else
            {
                if (p1 >= 0 && p1 < record.Length)
                {
                    return record[p1];
                }
                else
                {
                    return "oi"; //out of index
                }
            }
        }
        public static String ConvertExcelCellValueToCSharpCode(String cellValue	bool vQuoteValue)
        {
            String rcd1 = cellValue.Trim();
            String rcd = String.Empty;
            if (rcd1.ToUpper() == "TRUE") return "true";
            else
            if (rcd1.ToUpper() == "FALSE") return "false";
            else
            if (rcd1.ToUpper() == "NULL") return "null";
            else
            if (rcd1.ToUpper() == "STRING.EMPTY") return "String.Empty";
            else
                rcd = String.Format("{0}"	rcd1);

            if (vQuoteValue) return String.Format("\"{0}\""	rcd);
            return rcd;

        }
    }

}

2. DllEat

Description:
The second sample with a condition.

Sample: 'DllEat':

DllEat	eatExtdll.dll	EatExtDll	EatExtDllSampleCode2	CakeCutGenericX1	For-Boston	ItalyTour23[1]MemberFrom==Richmond	MemberNumber|MemberName|MemberFrom|year|month|date|seqNumber|Minus|Plus|Category|GroupBalance|Status	MemberName|JohnThomas

Dll Sample Code 2 for Command DllEat:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
//using static EatExtDll.EatExtDllSampleCode;
using EatUserDllExtension;


namespace EatExtDll
{
    public class EatExtDllSampleCode2
    {      
        public String CakeCutGeneric  (String[] UserCommand	List<String[]> AccountRecords	String[] FieldNames	int[] FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore)
        {
            if (UserCommand == null) return "missing argument UserCommand";
            if (AccountRecords == null) return "missing argument AccountRecords";
            if (FieldNames == null) return "missing argument FieldNames";
            if (FieldPositions == null) return "missing argument FieldPositions";
            if (ReturnRecords == null) return "missing argument ReturnRecords";
            if (UserCommand.Length < 8) return "wrong number of arguments";
            if (UserCommand[7].Length == 0) return "missing argument at cell H";
            if (UserCommand[8].Length == 0) return "missing argument at cell I";

            String[] fields = UserCommand[7].Split('|');
            String[] filter = UserCommand[8].Split('|');
            if (fields.Length == 0) return "wrong fields at cell H";
            if (filter.Length != 2) return "wrong filter at cell I";
            else
            {
                if (filter[0].Length == 0 || filter[1].Length == 0) return "wrong filter at cell I";
            }

            int[] pos = new int[fields.Length];
            int idx = 0;
            foreach (string s in fields)
            {
                pos[idx] = CommonTools.getPositionByName(s	FieldNames	FieldPositions);
                idx++;
            }
            int filterPos = CommonTools.getPositionByName(filter[0]	FieldNames	FieldPositions);

            foreach (string[] rc in AccountRecords)
            {
                if (rc[filterPos].Trim().ToUpper() == filter[1].Trim().ToUpper())
                {
                    StringBuilder sb = new StringBuilder();
                    bool first = true;
                    foreach (int p in pos)
                    {
                        if (first)
                        {
                            first = false;
                            sb.Append(rc[p]);
                        }
                        else
                        {
                            sb.Append("\t" + rc[p]);
                        }
                    }
                    ReturnRecords.Add(sb.ToString().Split('\t'));
                }
            }
            return null;
        }
        public String CakeCutGenericX1(String[] UserCommand	List<String[]> AccountRecords	String[] FieldNames	int[] FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore)
        {
            if (UserCommand == null) return "missing argument UserCommand";
            if (AccountRecords == null) return "missing argument AccountRecords";
            if (FieldNames == null) return "missing argument FieldNames";
            if (FieldPositions == null) return "missing argument FieldPositions";
            if (ReturnRecords == null) return "missing argument ReturnRecords";
            if (UserCommand.Length < 8) return "wrong number of arguments";
            if (UserCommand[7].Length == 0) return "missing argument at cell H";
            if (UserCommand[8].Length == 0) return "missing argument at cell I";

            String[] fields = UserCommand[7].Split('|');
            String[] filter = UserCommand[8].Split('|');
            if (fields.Length == 0) return "wrong fields at cell H";
            if (filter.Length != 2) return "wrong filter at cell I";
            else
            {
                if (filter[0].Length == 0 || filter[1].Length == 0) return "wrong filter at cell I";
            }

            int[] pos = new int[fields.Length];
            int idx = 0;
            foreach (string s in fields)
            {
                pos[idx] = CommonTools.getPositionByName(s	FieldNames	FieldPositions);
                idx++;
            }
            int filterPos = CommonTools.getPositionByName(filter[0]	FieldNames	FieldPositions);

            foreach (string[] rc in AccountRecords)
            {
                //if (rc[filterPos].Trim().ToUpper() == filter[1].Trim().ToUpper())
                {
                    StringBuilder sb = new StringBuilder();
                    bool first = true;
                    foreach (int p in pos)
                    {
                        if (first)
                        {
                            first = false;
                            sb.Append(rc[p]);
                        }
                        else
                        {
                            sb.Append("\t" + rc[p]);
                        }
                    }
                    ReturnRecords.Add(sb.ToString().Split('\t'));
                }
            }

            List<String[]> vAccountRecords = new List<string[]>();
            String[] vFieldNames = null;
            int[] vFieldPositions = null;
            String field71 = "City";
            String field72 = "ZipCode";
            String rs = pAskForMore("TourCity23"	field71 + " == Richmond"	vAccountRecords	ref vFieldNames	ref vFieldPositions);
            if(rs!=null)
            {
                return rs;
            }
            foreach (string[] rc in vAccountRecords)
            {
                //if (rc[filterPos].Trim().ToUpper() == filter[1].Trim().ToUpper())
                {
                    StringBuilder sb = new StringBuilder();
                    sb.Append("\t");
                    sb.Append("\t");
                    sb.Append("\t");
                    sb.Append("\t");
                    int filterPos7 = CommonTools.getPositionByName(field72	vFieldNames	vFieldPositions);
                    if (filterPos7 < 0) sb.Append("zip=\t" + "NotFound");
                    else sb.Append("zip=\t" + rc[filterPos7]);

                    ReturnRecords.Add(sb.ToString().Split('\t'));
                }
            }

            return null;
        }
    }
}

Dll Support Library:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace EatUserDllExtension
{
    public delegate String AskForMore(String AccountName	String Condition	List<String[]> AccountRecords	ref String[] FieldNames	ref int[] FieldPositions);

    public static class CommonTools
    {
        //common for all cs files
        public static int getPositionByName(string n	String[] FieldNames	int[] FieldPositions)
        {
            int p = 0;
            foreach (string af in FieldNames)
            {
                if (af.Trim().ToUpper() == n.Trim().ToUpper())
                {
                    return FieldPositions[p];
                }
                p++;
            }
            return -1;
        }
        public static String getValueByName(String[] record	string n	String[] FieldNames	int[] FieldPositions)
        {
            int p1 = getPositionByName(n	FieldNames	FieldPositions);
            if (p1 == -1)
            {
                return "nf"; // not found
            }
            else
            {
                if (p1 >= 0 && p1 < record.Length)
                {
                    return record[p1];
                }
                else
                {
                    return "oi"; //out of index
                }
            }
        }
        public static String ConvertExcelCellValueToCSharpCode(String cellValue	bool vQuoteValue)
        {
            String rcd1 = cellValue.Trim();
            String rcd = String.Empty;
            if (rcd1.ToUpper() == "TRUE") return "true";
            else
            if (rcd1.ToUpper() == "FALSE") return "false";
            else
            if (rcd1.ToUpper() == "NULL") return "null";
            else
            if (rcd1.ToUpper() == "STRING.EMPTY") return "String.Empty";
            else
                rcd = String.Format("{0}"	rcd1);

            if (vQuoteValue) return String.Format("\"{0}\""	rcd);
            return rcd;

        }
    }

}

3. DllEat

Description:
The third sample rendering multiple accounts

Sample: 'DllEat':

DllEat	eatExtdll.dll	EatExtDll	EatExtDllSampleCode3	MethodMultipleAccountsFor_EatExtDll	CS_x03	TourCity23[0]ItalyTour23	Param01	boston	City	ZipCode	MemberNumber	MemberName	MemberFrom	Minus	Plus	Category	Status

Dll Sample Code 3 for Command DllEat:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
//using static EatExtDll.EatExtDllSampleCode;
using EatUserDllExtension;


namespace EatExtDll
{

    //EatDll eatExtdll.dll eatextdll   eatextdllSampleCode3 MethodMultipleAccountsFor_eatextdll CS_x03 TourCity23 ItalyTour23 Param01 boston City    ZipCode MemberNumber    MemberName MemberFrom  Minus Plus    Category Status                  EatM1a2r3k_x1_|3																																																																				
    public class EatExtDllSampleCode3
    {     

        public String MethodMultipleAccountsFor_EatExtDll_param01(String[] UserCommand	List<String[]>[] AccountRecords	List<String[]> FieldNames	List<int[]> FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore)
        {
            #region command definition
            /*
             * EatDll	EatDll.dll	EatDll	EatDllSampleCode3	MethodMultipleAccountsFor_EatDll	TourCity23|ItalyTour23	CS_x03	Param01 boston	City	ZipCode	MemberNumber	MemberName	MemberFrom	Minus	Plus	Category	Status		
             * 0	    1	        2	    3	                4	                                5	                    6	    7	    8	    9	    10	    11	            12	        13	        14	    15	    16          17
            * */
            #endregion command definition

            #region check each argument
            if (UserCommand[8].Trim().Length == 0) return "Error	missing argument at cell I";
            if (UserCommand[9].Trim().Length == 0) return "Error	missing argument at cell J";
            if (UserCommand[10].Trim().Length == 0) return "Error	missing argument at cell K";
            if (UserCommand[11].Trim().Length == 0) return "Error	missing argument at cell L";
            if (UserCommand[12].Trim().Length == 0) return "Error	missing argument at cell M";
            if (UserCommand[13].Trim().Length == 0) return "Error	missing argument at cell N";
            if (UserCommand[14].Trim().Length == 0) return "Error	missing argument at cell O";
            if (UserCommand[15].Trim().Length == 0) return "Error	missing argument at cell P";
            if (UserCommand[16].Trim().Length == 0) return "Error	missing argument at cell Q";
            if (UserCommand[17].Trim().Length == 0) return "Error	missing argument at cell R";
            if (AccountRecords.Length != 2 || 2 != FieldPositions.Count || FieldNames.Count != 2) return "Error	wrong number of accounts";
            #endregion check each argument

            #region convert each argument to a name meaningful
            String cityInIntrest = UserCommand[8].Trim();

            String city = UserCommand[9].Trim();
            String ZipCode = UserCommand[10].Trim();
            String MemberNumber = UserCommand[11].Trim();

            String MemberName = UserCommand[12].Trim();
            String MemberFrom = UserCommand[13].Trim();
            String Minus = UserCommand[14].Trim();

            String Plus = UserCommand[15].Trim();
            String Category = UserCommand[16].Trim();
            String Status = UserCommand[17].Trim();
            #endregion convert each argument to a name meaningful

            #region seperate table data
            List<String[]> account0 = AccountRecords[0];
            List<String[]> account1 = AccountRecords[1];
            String[] names0 = FieldNames[0];
            String[] names1 = FieldNames[1];
            int[] pos0 = FieldPositions[0];
            int[] pos1 = FieldPositions[1];
            #endregion seperate table data

            #region on first table
            bool fnd = false;
            foreach (String[] rcd in account0)
            {
                String c = CommonTools.getValueByName(rcd	city	names0	pos0);

                if (c.Trim().ToUpper() == cityInIntrest.Trim().ToUpper())
                {
                    String z = CommonTools.getValueByName(rcd	ZipCode	names0	pos0);

                    #region on second table
                    foreach (String[] rcd1 in account1)
                    {
                        String c2 = CommonTools.getValueByName(rcd1	MemberFrom	names1	pos1);

                        if (c2.Trim().ToUpper() == cityInIntrest.Trim().ToUpper())
                        {
                            String[] outFields = new string[9];
                            outFields[0] = c;
                            outFields[1] = z;
                            outFields[2] = CommonTools.getValueByName(rcd1	MemberNumber	names1	pos1);

                            outFields[3] = CommonTools.getValueByName(rcd1	MemberName	names1	pos1);
                            outFields[4] = c2;
                            outFields[5] = CommonTools.getValueByName(rcd1	Minus	names1	pos1);

                            outFields[6] = CommonTools.getValueByName(rcd1	Plus	names1	pos1);
                            outFields[7] = CommonTools.getValueByName(rcd1	Category	names1	pos1);
                            outFields[8] = CommonTools.getValueByName(rcd1	Status	names1	pos1);

                            ReturnRecords.Add(outFields);
                        }
                    }
                    #endregion on second table

                    fnd = true;
                    break; // 1 to many	found 1 and quit
                }
            }
            #endregion on first table

            #region to end
            if (fnd) return null; // means good
            else return String.Format("Error	can't find the city |{0}|"	cityInIntrest);
            #endregion to end
        }

        //public String MethodMultipleAccountsFor_EatD   (String[] UserCommand	List<String[]>[] AccountRecords	List<String[]> FieldNames	List<int[]> FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore) multiple accounts
        //public String MethodFor_EatDll                 (String[] UserCommand	List<String[]>   AccountRecords	String[]       FieldNames	int[]       FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore) this is for single account 	the next line is for multiple accounts.
        public String MethodMultipleAccountsFor_EatExtDll(String[] UserCommand	List<String[]>[] AccountRecords	List<String[]> FieldNames	List<int[]> FieldPositions	List<String[]> ReturnRecords	AskForMore pAskForMore)
        {
            #region check esentials
            if (UserCommand == null) return "Error	missing argument UserCommand";
            if (AccountRecords == null) return "Error	missing argument AccountRecords";
            if (FieldNames == null) return "Error	missing argument FieldNames";
            if (FieldPositions == null) return "Error	missing argument FieldPositions";
            if (ReturnRecords == null) return "Error	missing argument ReturnRecords";
            #endregion check esentials

            #region check number of table and related data
            if (AccountRecords.Length != FieldNames.Count || AccountRecords.Length != FieldPositions.Count || FieldNames.Count != FieldPositions.Count) return "Error	account data is out of sync";
            #endregion check number of table and related data

            #region check if it is Param01
            String param = "Param01";
            if (UserCommand.Length==18 && UserCommand[7].Trim().ToUpper()== param.Trim().ToUpper())
            {
                /*
                 * EatDll	EatDll.dll	EatDll	EatDllSampleCode3	MethodMultipleAccountsFor_EatDll	TourCity23|ItalyTour23	CS_x03	Param01 boston	City	ZipCode	MemberNumber	MemberName	MemberFrom	Minus	Plus	Category	Status		
                 * 0	    1	        2	    3	                4	                                5	                    6	    7	    8	    9	    10	    11	            12	        13	        14	    15	    16          17
                * */
                return MethodMultipleAccountsFor_EatExtDll_param01(UserCommand	AccountRecords	FieldNames	FieldPositions	ReturnRecords	pAskForMore);
            }
            else
            #endregion check if it is Param01

            #region check second parameter
            if (false)
            {
            }
            else
            #endregion check second parameter

            #region if none is found
            {
                string[] r1 = new string[3]; r1[2] = String.Format("//{0} p{1} = {2}"	123	345	6789); ReturnRecords.Add(r1);
                r1 = new string[2]; r1[1] = String.Format("//{0} p{1} = {2}"	"s123"	345	6789); ReturnRecords.Add(r1);
            }
            #endregion if none is found

            return null; // means good
        }
    }
}

Dll Support Library:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace EatUserDllExtension
{
    public delegate String AskForMore(String AccountName	String Condition	List<String[]> AccountRecords	ref String[] FieldNames	ref int[] FieldPositions);

    public static class CommonTools
    {
        //common for all cs files
        public static int getPositionByName(string n	String[] FieldNames	int[] FieldPositions)
        {
            int p = 0;
            foreach (string af in FieldNames)
            {
                if (af.Trim().ToUpper() == n.Trim().ToUpper())
                {
                    return FieldPositions[p];
                }
                p++;
            }
            return -1;
        }
        public static String getValueByName(String[] record	string n	String[] FieldNames	int[] FieldPositions)
        {
            int p1 = getPositionByName(n	FieldNames	FieldPositions);
            if (p1 == -1)
            {
                return "nf"; // not found
            }
            else
            {
                if (p1 >= 0 && p1 < record.Length)
                {
                    return record[p1];
                }
                else
                {
                    return "oi"; //out of index
                }
            }
        }
        public static String ConvertExcelCellValueToCSharpCode(String cellValue	bool vQuoteValue)
        {
            String rcd1 = cellValue.Trim();
            String rcd = String.Empty;
            if (rcd1.ToUpper() == "TRUE") return "true";
            else
            if (rcd1.ToUpper() == "FALSE") return "false";
            else
            if (rcd1.ToUpper() == "NULL") return "null";
            else
            if (rcd1.ToUpper() == "STRING.EMPTY") return "String.Empty";
            else
                rcd = String.Format("{0}"	rcd1);

            if (vQuoteValue) return String.Format("\"{0}\""	rcd);
            return rcd;

        }
    }

}

L. Credit card accounts

1. General

Simply download CSV monthly statement files to the directory defined by command 'scanbank' in Model. We avoided to use a PDF product to interpret PDF statements so that we could save for customers. The CSV files are working fine.

2. Supported Bank Websites

Card Name	Bank Name	Web Site
Costco	citi	citi.com
N/A	Chase	chase.com
TJX	Synchrony	tjx.syf.com
Homedepot	N/A	homedepot.com
Lowes	N/A	https://www.lowes.com/u/login
Macys	N/A	https://www.macys.com/account/signin
N/A	CapitalOne	CapitalOne.com
Checking	Bank of America	bankofamerica.com
Savings	Bank of America	bankofamerica.com
Home Equity	Bank of America	bankofamerica.com
US Bank	US Bank	https://onlinebanking.usbank.com/
figure 3571

3. CSV Map file

On Model page in the master program EatUi.exe, there is an entry for the map file. We supply the file and it works for the major bank credit card companies listed above. We recommend user don't change this file because it is too complicated to change. If a user has a CSV statement for a company other than the ones listed, we will add the map sheet for the user for free to support his or her cause.

4. Bank file names

In the map file, each sheet represent a statement. The sheet name must conform to such a format that there are 4 strings seperated by hyphone '-'. The first string must be 'sheet', second string is the bank name. The third string is the accoune name, usually the account's last 4 digits. And the last string is the file's extention which is 'csv'. So for example, if a user have 2 Capital accounts with last 4 '1234' and '5678', the sheet name will be 'sheet-capital-1234-csv' and 'sheet-capital-5678-csv', and the file names of the bank files downloaded should be renamed as 'capital-1234-20230901.csv' and 'capital-5678-20230901.csv'. All sheet content remains intact. For more than 1 statemnets, the second and beyond are just copies of the first one.

M. Move Data Between Accounts

1. General

The strength of this tool is its capability to move data between accounts effectively.

2. The 2 Formulas

There are 2 formulas 'GetFrom' and 'PullFrom'. 'GetFrom' scans the target account records and return the data at first encounter on the condition. 'PullFrom' scans the target account records and return the data at last encounter on the condition.

3. Syntax and Action

Note: any phrase that starts with 'FieldName' means it is a field name defined in the account's type by command DfnType. any phrase that starts with 'Value' means it is a constant value. In general, a formula has 3 ot 4 phrases. The 1st is the formula name. The 2nd is the target account name. The third is the target field name. The 4th is a part of or the entire lookup condition.

Type	Syntax	Lookup Action
KeyToKey	GetFrom\|Account\|Field	This foemula is missing the 4th phrase. This means it will compare the source record key with the target record key.
StaticKeyToKey	GetFrom\|Account\|Field\|2023.11.09.1234 or GetFrom\|Account\|Field\|key:2023.11.09.1234	This formula will compare the key at 4th phrase with the target record key. If the 4th phrase is further divided by colon, and has 2 subphrases, then the 2nd subphrase is used in the comparism.
OneOfFieldValues	GetFrom\|Account\|Field\|Field:FieldName1:Value1,[FieldName2],FieldName3	This formula's 4th phrase must have 3 subphrases divided by colon. The 1st subphrase must be 'Field', The 2nd sunphrase is the target field name. The third subphrase is 1 or more subsubphrases divided by comma. If the field name is bracketed by [], the field name is located in the source account and its value is used to replace the bracketed field name. This formula's action is to check if one of the subsubphrases is part of the target field value. If yes, return true.
LogicExpression	GetFrom\|Account\|Field\|Logic:[FieldName1]>Value1 && [FieldName1] < FieldName3	This formula's 4th phrase must have 2 subphrases divided by colon. The 1st subphrase must be 'Logic', The 2nd sunphrase is a logic expresion. the target If the field name is bracketed by [], the field name is located in the source account and its value is used to replace the bracketed field name. This formula's action is to evaluate the logic expresion.

N. Analyze the reports

1. General

The reports are just showing each accounts in Excel sheet. The order of the sheets is the order defined in a argument of all the command 'account'. Each sheet will list all transactions in the order of the key, usualy the combination of the fields 'year', 'month', 'date' and 'SeqNumber'.

2. The total

Each user could have the Model set up such that the financial total is calculated in the total account. The total account is the top tier account that contains transactions that aggregate the end balances from several other lower tier accounts, and which in turn could aggregate from further other lower tier accounts. For example, the 'Total' account is a sum of the end balance from 'Cash', 'Investment' and 'Liability'. And The 'Cash' account is a sum of the end balance from 'Checking' and 'Savings' , etc.

3. The style

Each sheet could be tuned to certain style. On the Model page in EatUi.exe, there is an entry for the style template file. This file contains the sheets that the names of the sheets match the account names, and then the sheets provide a base for the accounts to be written upon.

4. The Archive

The report file is named with date and model name. The file can be archived into the directory 'Archive'. The files in 'Archive' will not be deleted when user performs a 'clean' function which deletes files in directory 'rpt', 'log' and 'Copy' beyong the allowed number of files to keep.

5. Web Page Report

When user checked the CheckBox 'as Web Page' , and an equivalent report file is generated in the format of HTML. This report only selects the columns between Collumn 'DateSeqAsKey' and 'LastField'. So user should add the field 'LastField' and arrange the account fields in an order that user prefer.

O. Analyze the data

1. Group Transactions

The command 'groupSubtotalForChart' can group an account transactions and calculate the group's totals, and show the data at the end of the account report.

2. Filter & Group Transactions

Other than the command 'groupSubtotalForChart', there are 4 other commands that can move transactions to a new account. The movement can be customized with filters and groups to produce a subset of or aggregated set of transations, for analysis purposes. These commands are 'copyAccount', 'copyMatched', 'copyMismatched' and 'joinAccounts'. Refer to each commands for user's purpose.

P. Prepare next cycle

1. General

For a user, monthly recurrence of payments and reconciliation of bank accounts are mandatory or smart task. User use a cycle sheet to describe all entry forms for a cycle. When entering next cycle, the forms in the next one are exactly the same, or otherwise the model is not smart due to requiring user to constantly change the forms. The smart way is that user only need to enter the data in the form assuming the cell had been background-color-highlighted. For example, just replace the payment amount, from $40.03 to $45.32, etc. This EAT tool provides a command to copy the very last cycle sheet to a new cycle sheet with styles intact. The command can change some of the field values in the new sheet. Following 3 items are recommended to be changed for the new cycle sheet.

clear the Status field. The Status field is to flag if a record is entered and thus updated. When all is flagged, it is time to reconcile the new cycle.
replace a new month number, and maybe year number.
move a field data to another. For example, move 'currentBalance' to 'previousBalance', because a formula could calculate a new balance based on previous balance. This is true for Mortgage Balance and Escrow Balance.

Use the command 'prepareCycle' to carry out this task. Refer the command for how to use it. The new cycle sheet resides in its own Excel file. User just need to copy the sheet to where user prefers. There is a CheckBox for this command on page Model of EatUi.exe. If unchecked, the command is disabled.

Q. Create one book

1. General

All bank files are translated into the input commands. All manual input commands plus all bank input commands can be consolidated into one Excel book. In turn this one book can be fed as an input file in a model. The result generated by this new One Book should be identical to the result by the ones in user's model. User could refer to this One Book and examine as a good exercise. There is no command for this function. Only use a CheckBox of 'create one book' on page Model of EatUi.exe to carry out this task. If unchecked, the function is disabled. The new One Book file is saved as its own Excel file. User could move it to a new model to test out, just for fun if there is no other practical reasons.

R. Shorten the cycles

1. General

User may already has 4 years of data in input sheets. He is no longer concerned about the history data more than 1 year ago, want to remove them.

2. Step 1

He can remove the history cycle sheets by either renaming them with a prefix 'x' or simply remove the cycle sheets, and remove the bank directory from the model. This assumes that the cycle sheet only contains the cycle commands (Add and AddRecord commands for their cycle), not commands like 'type', 'account' and other generic commands.

3. Step 2

But that is not enough because what about the starting balances for all accounts? That means user has to come up with a set of initial values for the commnad 'setInitValue' for each accounts. Fortunately on the page Model of EatUi.exe there is an entry of 'create init commands', user can provide the Month, Date and Year as 'CutOffDate' for which the balance values are used to generate a set of commands of 'setInitValue'. This set of commands can replace the old ones. So by doing this 2 steps of task, user can reduce the number of cycles being considered in the accounting.

S. Back up

1. Purpose

All files reside on the same disk drive. If the disk drive is no longer functioning, all financial data files are lost. The solution is to backup the files to another USB or network drive.

2. Backup a Must

Purchase a portable USB drive for backup purpose. Plug the drive to a USB port. Backup after you have made changes to the system, usually at the end of day. Once the backup is finished, then proceed to shut down the PC.

3. How to

In Eat Manager, go to page Backup, click the bottom buttons to back up either to a drive or to a directory.

4. Method

This backup command only backs up the files that have the file dates newer than the ones on destination drive, avoiding waste of time on copying unnecessarily the files that have the same contents as that of the destination ones.

T. Update EAT

1. Download zip File

EAT update is free from charge. An owner of EAT can download the new version at www.excelaccountingtool.com/EatDownLoadV2Two/EatUpdate, provided the owner had logged in.

2. Unzip File

Unzip the downloaded zip file, put in the Installation Full Path (IFP) in 'This Folder' and choose 'Replace the files in the destination'.

3. License File

The new updated version works on the existing license file, which was untouched during the update and continues to work through out its term.

U. Definitions & Practices

1. Color Names

AliceBlue, AntiqueWhite, Aqua, Aquamarine, Azure, Beige, Bisque, Black, BlanchedAlmond, Blue, BlueViolet, Brown, BurlyWood, CadetBlue, Chartreuse, Chocolate, Coral, CornflowerBlue, Cornsilk, Crimson, Cyan, DarkBlue, DarkCyan, DarkGoldenrod, DarkGray, DarkGreen, DarkKhaki, DarkMagenta, DarkOliveGreen, DarkOrange, DarkOrchid, DarkRed, DarkSalmon, DarkSeaGreen, DarkSlateBlue, DarkSlateGray, DarkTurquoise, DarkViolet, DeepPink, DeepSkyBlue, DimGray, DodgerBlue, Firebrick, FloralWhite, ForestGreen, Fuchsia, Gainsboro, GhostWhite, Gold, Goldenrod, Gray, Green, GreenYellow, Honeydew, HotPink, IndianRed, Indigo, Ivory, Khaki, Lavender, LavenderBlush, LawnGreen, LemonChiffon, LightBlue, LightCoral, LightCyan, LightGoldenrodYellow, LightGray, LightGreen, LightPink, LightSalmon, LightSeaGreen, LightSkyBlue, LightSlateGray, LightSteelBlue, LightYellow, Lime, LimeGreen, Linen, Magenta, Maroon, MediumAquamarine, MediumBlue, MediumOrchid, MediumPurple, MediumSeaGreen, MediumSlateBlue, MediumSpringGreen, MediumTurquoise, MediumVioletRed, MidnightBlue, MintCream, MistyRose, Moccasin, NavajoWhite, Navy, OldLace, Olive, OliveDrab, Orange, OrangeRed, Orchid, PaleGoldenrod, PaleGreen, PaleTurquoise, PaleVioletRed, PapayaWhip, PeachPuff, Peru, Pink, Plum, PowderBlue, Purple, Red, RosyBrown, RoyalBlue, SaddleBrown, Salmon, SandyBrown, SeaGreen, SeaShell, Sienna, Silver, SkyBlue, SlateBlue, SlateGray, Snow, SpringGreen, SteelBlue, Tan, Teal, Thistle, Tomato, Transparent, Turquoise, Violet, Wheat, White, WhiteSmoke, Yellow, YellowGreen

2. Names Case

All names like sheet's, type's, account's, etc are case insensitive.

3. Word Search

If a word definition is not clear, try to search entire document for the word. It may exits somewhere else that could clear user's confusion.

V. History of changes

1. The changes

Date	Description
07/15/2021^v3.1	adjust User Manual.
07/20/2021^v3.1	ENV Commands: modified how to define the command strings for Excel and Text editors. The new way is simpler and the user just write out an entire string with none case-sensitive 'XXX' which is to be replaced with the target file name.
07/20/2021^v3.1	Trial Period: modified the trial term period to be 3 month.
08/13/2021^v3.1	Concatenate the Calculation strings with separator Comma instead of '/r' to avoid not being displayed in LibreOffice in sheet Main_MathMap.
08/14/2021^v3.2	Remove error warning bell sound.
08/14/2021^v3.2	log as an error when capacity limits are reached.
08/22/2021^v3.3	Add Excel Macro-enabled file extension XLSM file as input file.
08/23/2021^v3.3	Change command 'setKeyField' to set none-standard key in multiple fields.
08/28/2021^v3.3	Add a command 'CopyAccount' to copy records from one account to another.
09/07/2021^v3.3	Add a command 'CopyAccountOnFilter' to copy and also filter records from one account to another.
09/14/2021^v3.3	Add a default field 'Marker' for every account. This field holds the value 'good here' or 'reset\|FieldName1:0.0\|FieldName2:0.0'. See 'Marker' for more information.
09/15/2021^v3.3	Add a mode of entering header and values separately, the Compact Mode.
09/16/2021^v3.3	Add 2 default fields 'Description' and 'Status' for every account. These 2 fields are so useful and important that we might just add them as default for conveniences.
10/06/2021^v3.3	Allow calculation formula accepts constants like '3.0' in 'Amount\|c=Share*3.0'.
10/06/2021^v3.3	Since computer double calculation is not accurate and the near zero result is expressed in 'Natural Exponential Function', the value less than 0.03 is presented as 0 to avoid confusion.
10/08/2021^v3.3	change CopyAccountOnFilter to CopyAccountOnIncFilter and add CopyAccountOnExcFilter command.
10/12/2021^v3.3	change CopyAccount, CopyAccountOnIncFilter and CopyAccountOnExcFilter commands to have a 'Order Number' field which serves as an order in which the commands are executed.
10/19/2021^v3.3	Add Repeat and RepeatRecord commands. These 2 commands are primarily used for records that have a link field 'GetFrom' and its 'Year' field is 'Link' so that user don't have to enter them in each sheets. The 2 new commands are duplicated into sheets prefixed by 'Cycle' in name.
10/25/2021^v3.3	Add inclusion of 'a template file' for report. Refer to section 'Report templates' for more information.
10/26/2021^v3.3	Add few other formatting commands for report. Refer to section 'Report formatting commands' for more information.
11/10/2021^v3.3	Add process to create reports on Credit Card statements from 5 banks. More banks will be added in the future.
01/01/2022^v4.1	Add Capital and USBank Credit card PDF statement processing. Finished a better coding strategy for PDF Statement processing.
01/09/2022^v4.1	Made a minor revision for Command 'groupSubtotalForChart'. The revision is to allow the command to handle zero values for the totaling fields.
01/15/2022^v4.1	Added a Prelude file as Excel format that defined additional parameters. One parameter is the 'Scan' command which defines a directory in cell 2. User can define multiple 'Scan' command to define multiple directories. The other is a command called 'setDebugMode' which set the debug flag on and off. When it is on, many statistical data are written into the log file for analysis.
02/04/2022^v4.1	Enhanced the log report in Notepad++, which utilizes the collapsing #region #endregion region. Added a 'Debug mode' for log report.
02/08/2022^v4.1	Enhanced the field calculation formula to use left and right brackets '(' and ')' in the 'Type' definition. For example, user can use FieldName\|c=Field3*(field4+45)
03/07/2022^v3.1	Removed ENV Command ExcelEditor and TextEditor: We learned Windows provides default programs to open files. So those parameters are removed. User should go to Windows Default Program to assign desired programs to open Excel and Text files.
03/15/2022^v4.1	Completed the code logic to handle bank CSV files, and removed the code handling bank PDF files due to the license requirement.
04/25/2022^v4.1	Added a log entry for version limit controls.
04/28/2022^v4.1	Added a report formating commnad 'writeNavigationColumn'.
04/28/2022^v4.1	Changed CSV bank directory from signular and static to multiple and configurable in parameter file using the command 'scanBank'.
04/29/2022^v4.1	Added Dialog form key Enter and ESC responses.
04/30/2022^v4.1	Integrated the location limit for both manual and bank auto directories.
05/01/2022^v4.1	Adjusted source code to its optimum consolidated object structure.
07/18/2022^v4.1	Changed command 'CopyAccountOnExcFilter' to 'CopyAccountOnExcFilter'.
07/18/2022^v4.1	Changed command 'CopyAccountOnIncFilter' to 'CopyAccountOnIncFilter'.
08/15/2022^v4.3	Fixed a bug of Pointer error caused by missing description field in Command 'account'.
09/02/2022^v4.2	Added an 'Instructiona and notes' page in Eat Manager to allow user to enter self-guiding instructions and notes for each model.
09/02/2022^v4.3	Fixed a mistake that the Hyper Link was written to a record of zero value, which then was removed from report.
09/17/2022^v4.3	Added a function of removing the customer download zip files for the sake of saving disk space.
09/17/2022^v4.3	Added a few of table fields to store data about the customer download files.
10/25/2022^v4.4	Created auto ordering process on the math steps to eliminate the need of user manually specifying the math steps.
11/20/2022^v4.4	Integrated the hierarchy view of any dependencies.
02/04/2023^v5.0	Created a new Object Programming Framework, and applied the entire program source codes to the framework.
02/05/2023^v5.0	Finished moving the entire program source codes to WinForm GUI.
03/05/2023^v5.0	Finished deployment of the project separate from Teknewell CS OOP Framework product.
04/27/2023^v5.0	Examined the correctness of the math calculation algorithm.
02/27/2024^v5.1	Added Conditional Expression. Its purpose is to evaluate a record for further processing.
03/06/2024^v5.1	Completed log entries in entirety.
03/07/2024^v5.1	Revised help argument.
03/08/2024^v5.1	Added auot back up function.
03/08/2024^v5.2	Upgrated to version v5.2.
03/14/2024^v5.2	Optimized Excel read and write class family.
03/27/2024^v5.2	Optimized WinForm main and sub threads.
04/06/2024^v5.2	Revisited Epplus GNU LGDL. Decided to document the changes on Epplus. So far only 1 change was made.
04/16/2024^v5.2	Added function for the 4th field of command GetFrom. When this 4th field is present, it serves as the key to locate the source record from which the field value by the name of 3rd field is copied over.
04/30/2024^v5.2	Tuned and tested the 3 dll commands: eatdll, oopdll and oehdll.
06/07/2024^v5.2	Added account hierarchical charts for EAT.
06/17/2024^v5.2	Added 4th field as user key for formula PullFrom.
08/09/2024^v5.2	Added the command RepeatRecordX1 as a variation of command RepeatRecord. Its column B is an insert which represent the second prefix of the cycle sheet. Please refer to the commnad RepeatRecord for more detail.
08/09/2024^v5.2	Fixed OneFile bug which shows the cycle sheets are not written out.
08/09/2024^v5.2	Added a key word LastOf in math calculation. The format is LastOf:FieldName. This will retrieve the value from FieldName in last record. The field value is expected to be ready so the filed in the math formula does not participate the dependency sorting.
08/16/2024^v5.2	Revised to include the LastOf field in the dependency sorting.
08/19/2024^v5.2	Added a Case formula for GetFrom.
08/21/2024^v5.2	Revised and completed 2 Case formulas, one (MathCase) for calculation and the other (MoveCase) for data movement like GetFrom.
08/22/2024^v5.2	Tested MoveCase, and concluded that it only works when Conditions contain the user-entered fields, not the fields that are calculated and copied.
08/29/2024^v5.2	Optimized the Dependency Sorting process, and reduce memory size.
12/11/2024^v5.2	During the previous few months, changed the all command names so that they are more fitting in enginnering principles. For example, change 'type' to 'DfnType' so the command becomes more unique and grouped in same category of 'Dfn'. 'Dfn' means 'Define'.
12/12/2024^v5.2	Added a directive Round which instruct to round a field value in math. Please see the command 'DfnType'.
01/07/2025^v5.2	Added 2 commands: SetOrientation and SetCalculationPrint.
01/13/2025^v5.2	Removed MoveCase for simplicity of code maintenance. If a set of external fields is needed, use GetFrom to move them all over for calculation.
01/13/2025^v5.2	Modified the OneFile output that enhances analytical capabilities.
01/13/2025^v5.2	Restored the Save function that saves input files into Directory Save. A switch on Page Model can be used to turn off this function.
01/24/2025^v5.2	Added 3 directives to GetFrom formula. They are 'key:2024.12.13.1234', 'field:name:value1,value2,value3', 'logic:[taxable]lowValue'.
01/24/2025^v5.2	Tested and documented the 3 directives to GetFrom and PullFrom. Search for GetFrom for further information.
01/29/2025^v5.2	Completed the Excel Cell dependency hyper links. User can click a link that takes the user to the source cell.
01/29/2025^v5.2	Updated the Excel Cell dependency hyper links. User can click links that takes the user either up or down.
figure 8001

W. History of Epplus Changes

1. The changes

Date	File	Line	Description
04/01/2024^v5.1	na	na	sample line
04/05/2024	ExcelWorksheet.cs	4244	After a sheet was added to another book, the ConditionalFormatting was not aaded along with. So this 'set' method could allow to set it from source.
04/06/2024	ExcelComment.cs	92	fake entry

Excel Accounting Tool (EAT) - User Manual and Instructions

Version v5.2 - Target: Release (EAT) - Built on: 1/30/2025 3:47:15 PM - Released on: 1/30/2025 3:49:00 PM

Home

Table of Contents

Presentation of Contents

A. How to use the document

B. About EAT?

C. How to acquire EAT

D. Install EAT

E. Graphic user interface

F. Work flow chart

G. The model

H. The model commands

I. The input sheets

J. The input commands

K. The dll commands

L. Credit card accounts

M. Move Data Between Accounts

N. Analyze the reports

O. Analyze the data

P. Prepare next cycle

Q. Create one book

R. Shorten the cycles

S. Back up

T. Update EAT

U. Definitions & Practices

V. History of changes

W. History of Epplus Changes

Operator	Function
/	Division
*	Multiplication
-	Subtraction
+	Addition