cupsched TCL Application

cupsched is a Tcl/Tk graphical GPL application that will keep track of your schedule of events including budget. You will be able to view your planned and actual expenses and balance for each day. The schedule data is stored in Bbuuzzb tables.

This application is the graphical version of the sched application. cupsched uses the Tk toolkit along with Future Lab graphical library modules. The program is run using the graphical wish shell. Before attempting to run this program, edit the main program file (cupsched.tcl) and set the Tcl directory structure so that the program can locate the required Future Lab library files.

The cupsched application is designed for single user use. The Bbuuzzb database engine is part of the included files. Before you can run the cupsched application, you must set up a database configuration file called dbeng.cfg with a minimum of the tmp_path, log and catalog entries.

All configuration files must be located in the same directory as the source program. The cupsched application must be executed within its current directory so the program can locate the configuration files.

When running this program, it should be run with the bbuuzzb catalog active. In the following detailed description all table names are logical.

# Detailed Description

Cupsched will store and calculate your schedule of events. Events include budgetary and reminder's. Events are tracked on a day to day basis. This program makes it possible to see your bank account balance for every day there is an event.

All data is stored in bbuuzzb tables. Each table is a year's worth of data and this program allows you to see the data one month at a time.

As yearend approaches, you need to manually create next year's bbuuzzb table. The table names have the convention of:

       schedule.nnnn

Where nnnn is the year.

The column headings in the main event listing are:

    Date - event date in the form mmdd.n (month, day and event sequence)
    Description - a description of the event
    Category - the category or type of event
    Planned - the planned expense
    PBal - the running planned balance
    Actual - the actual expense
    ABal - the running actual balance

The balances are as at after the event has taken place.

This program depends on a category table which you need to set up. Every event will belong to one of these categories. The name of the category table must be schedule.category.

Each category entry has a type which tells this program what to do with all the events that belong to this type. The category types are:

    credit - a account deposit for example
    debit - a payment from account for example
    NA - an event that has no financial effect, a reminder for example

This program also uses its own temporary table called schedule.tmp. This table must also already exist.

At least one category must represent the opening balance for that month. Each schedule month must contain one open balance record. At the moment, the open balance category number is hard-coded at six(6). When you create your category table, make sure that the open balance record is category number six(6). In a future version of this program, I will make the open balance and it's category number more flexible.

Goto Top | Future Lab Home | Contact Webmaster | Feedback

Copyright © 2008 Future Lab, Last Aug 31, 2008