KMVCD

Details of this Project

- Product Summary
- Main Screen
- List View of a Data File
- Record Entry/Edit View
- Reports Preparation Screen

Project Summary:

Client: Kern Mosquito and Vector Control District

Business: Eradication/Control of Mosquitoes, rats, and other disease vectors

Project Objective: Develop and maintain their specialized operations database

Product Summary (NOTE: the software described is a Win95 application requiring SVGA 800 x 600 resolution. The screens may not display correctly for those of you using a VGA display)

Kern Mosquito and Vector Control District (KMVCD) is a special assessment district located in Kern County, California. Their mission is to eradicate/control mosquitoes, rats, and other disease-carrying vectors. I have been associated with KMVCD since 1985. I programmed their first databases in compiled dBASE III code using the Clipper compiler. I also modified SBT's accounting package for their use.

The current version of their data base is a Visual FoxPro application. It incorporates both the operations database and their assets database. They have just switched to Peachtree Accounting for Windows for Y2K compliancy.

Figure 1 is the main screen display of the Operations database. The operations file entry/edit pad is opened to indicate how many files are involved. The assets section includes another six datafiles. All datafiles are associated with multiple indexes.

Figure 1 - Display of main menu screen - dropdown indicates the number of files in the database

Figure 2 is a display of one datafile in the "list" view. This view is read-only but allows a quick look at the entire file. Clicking the "GoTo" button (near screen top) allows the user to jump around in the file.

Figure 2 - "List" view of a datafile- navigation buttons near screen top allow the user to jump around in the file

Figure 3 is the same data file in the "record" view. This display is used for record entry/edit. Data validations occur at both the field and the record level. Pressing the Revert button brings data that was in place before the current edit session started.

Figure 3 - "Record" view of a datafile- this display provides entry/edit of any one record. Note that data validation occurs at both the field and record level

Figure 4 is a typical reports preparation screen. The user is prompted for certain reporting criteria, then can choose whether to display or print the report. Note also that printers can be changed.

Figure 4 - Typical report preparation display- note report criteria section, printer selection, and whether to display or print the report