1. Access and modify the dialogue box, which appears after completing a farming operation, so that errors can be corrected without having to remove a farming operation which may have included many fields. 2. What happens to diesel fuel when an operation is removed? The diesel seems to have been permanently removed from inventory yet does not show up in an expense report. Could the diesel be restored to inventory? 3. In getting a field history report, could the total acres be summed instead of just getting individual fields listed? 4. Let the program caculate diesel fuel use. How many farmers actually measure diesel used per field operation? Let users input a gallons used by a tractor per acre then let that fuel consumption rate be multiplied by a factor which is input by the user for each implement (which would be in terms of hours per acre). These tractor and implement rates can be obtained from state extension budgets and easily included in the setup of each tractor and implement. 5. To support Jim Hemminger, make the error detection, editing and reports features resemble QuickBooks more closely. 6. Sometimes editing the field notations (date, etc.) give a false impression that the user is editing something other than text - as if editing the notations actually changed something in the accounting or crop history. 7. How about numbering each farming operation so that it needs to be removed, the user does not have to go to each field and remove the operation individually--just get a list of farming operations and remove it as a whole.