Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I like Ratslinger's answer, but also wanted to add how I normally take care of this situation, because I encounter a lot and I don't like having two fields in my table that really are about the same thing. For me this occurs most often when a record status becomes "obsolete". I want to keep the obsolete selections (records), but I don't want them as my normal selection choices.

Here is an example. What I do is use the status to do two things: 1) sort the obsolete records to the end (bottom), and 2) flag them with their status, in this case I often attach the word " --Obsolite" to their name.

image description

I like Ratslinger's answer, but also wanted to add how I normally take care of this situation, because I encounter it a lot lot, and I don't like having two fields in my table that really are about the same thing.

For me this occurs most often when a record status becomes "obsolete". I want to keep the obsolete selections (records), but I don't want them as my normal selection choices.

Here is an example. What I do is use the status to do two things: 1) sort the obsolete records to the end (bottom), and 2) flag them with their status, in this case I often attach the word " --Obsolite" to their name.

image description

I like Ratslinger's answer, but also wanted to add how I normally take care of this situation, because I encounter it a lot, and I don't like having two fields in my table that really are about the same thing.

For me this occurs most often when a record status becomes "obsolete". I want to keep the obsolete selections (records), but I don't want them as my normal selection choices.

Here is an example. What I do is use the status to do two things: 1) sort the obsolete records to the end (bottom), and 2) flag them with their status, in this case I often attach the word " --Obsolite" to their name.

image description

NOTE: I think it would also be possible to write a macro that would dynamically populate the pull down list with only the items with a given status, but there may be a gotcha along the way, and I'd rather keep things simple if at all possible. (I hesitate because I recently ran into another event bug in LO and I wasted a day because of it. So somethings that might be possible, need to be proved to work, before I will believe they will really work.)

I like Ratslinger's answer, but also wanted to add how I normally take care of this situation, because I encounter it a lot, and I don't like having two fields in my table (Table Control) that really are about the same thing.

For me this occurs most often when a record status becomes "obsolete". I want to keep the obsolete selections (records), but I don't want them as my normal selection choices.

Here is an example. What I do is use the status to do two things: 1) sort the obsolete records to the end (bottom), and 2) flag them with their status, in this case I often attach the word " --Obsolite" to their name.

image description

NOTE: I think it would also be possible to write a macro that would dynamically populate the pull down list with only the items with a given status, but there may be a gotcha along the way, and I'd rather keep things simple if at all possible. (I hesitate because I recently ran into another event bug in LO and I wasted a day because of it. So somethings that might be possible, need to be proved to work, before I will believe they will really work.)

I like Ratslinger's answer, but also wanted to add how I normally take care of this situation, because I encounter it a lot, and I don't like having two fields in my table (Table Control) Table Control that really are about the same thing.

For me this occurs most often when a record status becomes "obsolete". I want to keep the obsolete selections (records), but I don't want them as my normal selection choices.

Here is an example. What I do is use the status to do two things: 1) sort the obsolete records to the end (bottom), and 2) flag them with their status, in this case I often attach the word " --Obsolite" to their name.

image description

NOTE: I think it would also be possible to write a macro that would dynamically populate the pull down list with only the items with a given status, but there may be a gotcha along the way, and I'd rather keep things simple if at all possible. (I hesitate because I recently ran into another event bug in LO and I wasted a day because of it. So somethings that might be possible, need to be proved to work, before I will believe they will really work.)

I like Ratslinger's answer, but also wanted to add how I normally take care of this situation, because I encounter it a lot, and I don't like having two fields in my Table Control that really are about the same thing.

For me this occurs most often when a record status becomes "obsolete". I want to keep the obsolete selections (records), but I don't want them as my normal selection choices.

Here is an example. What I do is use the status to do two things: 1) sort the obsolete records to the end (bottom), and 2) flag them with their status, in this case I often attach the word " --Obsolite" to their name.

image description

NOTE: I think it would also be possible to write a macro that would dynamically populate the pull down list with only the items with a given status, but there may be a gotcha along the way, and I'd rather keep things simple if at all possible. (I hesitate because I recently ran into another event bug in LO and I wasted a day because of it. So somethings that might be possible, need to be proved to work, before I will believe they will really work.)