I think I would work on the data model, then the input form, then the report. It sounds to me like the table could use some normalization. How about:

*** Main table

pkAction (primary key)
fkManager (foreign key to Manager table)
fkStatus (foreign key to status table)
start
ssp

*** Manager
pkManager (primary key)
ManagerName

*** Status
pkStatus (primary key)
Status

Now for the input form, you have all three tables in the Dataenvironment and use comboboxes to select a manager and a status. You use text boxes for the other stuff.

For the report, you use a SQL statement:

SELECT maintable.*,manager.managername,status.status FROM maintable,manager,status WHERE maintable.fkmanager=manager.pkmanager AND
maintable.fkstatus = status.pkstatus


>I have a table that consist of a status field that can have three or more variables such as working, planning, or complete.
>
>My plan is to develop a form for the user so he or she can input working or planning or complete. This input is passed to the report program for processing. These reports will look like this base on form input by user.
>
>manager status start ssp
>Dean working 08/10/99 99-521
>Dean working 08/02/99 99-528
>
>------------------------------------------
>Manager Status Start Ssp
>Hutch complete 09/01/98 98-520
>Hutch complete 08/15/98 98-023
>
>-------------------------------------------
>Manager Status Start Ssp
>Johnson Planning 07/15/98 99-529
>Johnson Planning 06/20/99 99-201
>
>
>1. Should i develop report first and develop user input
>form second?
>
>2. My input form will have these fields.
>
> TxtStatus - Text box containing working or complete or planning.
>
> CmdRunReport - button use to fire the form.
>
>**** Could I get some help on this???????? Have a nice day.