Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help re. calculated field

Status
Not open for further replies.

Blackshark

Programmer
May 7, 2002
48
GB
Gents,

I am not sure if this should in one of the other forums, but here we go:

I have a table of jobs and want to generate a 'status' code for each job. The status code will depend how far a long an agreed procedure each job is at. This depends on whether certian fields have been filled, what their values are and overall I would say there might be 12 different values I want the job status to be.

Should I:

A) Calculate the status by building it in to the recordsource's of the forms and reports

B) Create a field in the database and have code behind the forms that alter the job code as the jobs are updated

Usually I would go with A however the function needed to calculate the job code is big and I will be pushing the limits of the SQL length on quite a few of the forms.

Hmm, thinking about it could I:

C) Build a query that just calculates the job status for every job and then link this query with the job number to each of the forms reports.


I think I have answered my own question. Any input though still gratefully recieved.

Regards Tim

 
If the status is always changing, you don't need to store it, and you know how to easliy re-create it via a query, I'd go with C.

Can't tell which way made you think you answered your own question, but I'm thinking you're leaning towards C yourself.

Hope this helps.

Jim "Get it right the first time, that's the main thing..." [wavey]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top