Status History

[jimpres]

I have a field with a popup value list of 5 items.

I want to archive the information as the list changes.

I tried to create a script but I could not get it to work in that field.

I either got the script or the list depending on which was forward.

The status value field is the status of software trouble reports. I want to keep track of the trouble report status as it moves from open, work in progress, assigned through closed. So I need to somehow save the status as it changes.

My current approach is to have another file where the status for a given trouble report is stored. Then in the parent file I can display all the status history using a global.

So to make this short I want to save a change in status from the value list in another file.

[LiveOak]

If you are entering status in another file, it should be saved. I guess I'm assuming that you make a new entry in the related file for each status change. I have a membership database where I do exactly that, for each change in status I make a new entry with a "Status", "Date", and "Comments".

Another approach is to use a text field in the same file and just keep adding status entries separated by carriage returns. For example:

Created - 5/5/01

Completed - 6/15/01

Closed - 7/6/01

For display, use a calculation field:

StatusDisplay (calculation, text) =

Case(

PatternCount(Status, "Closed"), "Closed",

PatternCount(Status, "Completed"), "Completed",

PatternCount(Status, "Created"), "Created",

"")

-bd

[jimpres]

Not sure I understand.

What is the trigger to save a change in a field?

When I click in the status field I get the value list and select one.

What I want is to save the old one for history.

How can I save the old one in a single field like you say in a text field with carriage returns.

Would you show me the steps please.

[LiveOak]

You status change will still be done with a script. Whether you use a field in the same file or records in a related file is your choice. If you need to build reports based upon this the changes in status, use a separate related file. I'll give you an example script for a field in the same file, the scripting for a related file is more complex.

Say you have the fields:

StatusEntry (text)

Status (text) <--- This is the field with the dates and carriage returns.

The script triggered upon exit of StatusEntry might look like

Allow User Abort (off)

Set Error Capture (on)

Set Field(Status, Status & "

[jimpres]

I liked your same record solution and implemented it.

I do have several statu's related to specific Trouble Reports in another file that I imported form FoxPro.

Currently I display them in the TR file via a global.

So with the global for historical FoxPro data

and the Same field with current staus's I think that will work out great.

I had considered reading in all the old FoxPro statu's intothe same current field but have not tried that yet.

Thanks a bunch,

[jimpres]

So far I have a script running on exiting the status field. It stores the status change in another field.

My initial thought was to create a record of this change related to a specific trouble report.

You mentioned I could but it in a test field separated by returns, How do you keep adding the changes to the text field? That would be easier then creating another record in a different file.