Adding My Own Option In Combo

[DMT Dave]

Hi gGuy's unsure if this is possible



I have a combo set to table/query listing a fields from a table

There are various combos throughout the database using the same option

There is one particular combo where i was thinking of adding a sporadic option (just as if it was a value list)

If i were to do this, i don't want other combos having this chosen option

Otherwise the easiest way i guess is top add a record to the bound table

I have thought of adding a yes/no field called ListDisplay but this means updating the list per combo before update or on got focus

Is there a method of adding a unique option to just 1 x combo ?

I don't think there is but you guys on here may confirm

[DMT Dave]

After thought unless any advice beforehand

i guess, copy my table and rename and add the unique option to table2 and set the desired combo to table2 and leave all other combos as table one

is this efficient to my question ?

[Welshgasman]

For that one errant combo, turn it into a value list combo instead, and populate from your table plus your extra entry.

[moke123]

There is one particular combo where i was thinking of adding a sporadic option (just as if it was a value list)

What do you mean by sporadic? Is it that this 1 combo will only sometimes have the extra option and sometimes not? How many columns are in the combo?
Do you also need a primary key for this added option?

One way I limit what's in a combo is to add a where clause with either an "ID <> somevalue" or I use a "Where ID not in( 1,3,4,7)" to limit what's returned.

[DMT Dave]

Hi WGM and Moke123, i meant by adding a unique value to a combo that is bound to table

I don't have a primary key in this particular table but that is probably best based on Moke123 suggestion

Add a new auto number field and add a clause where the combo is populated where ID Not(number of record)

I will give that a try

Thank you

[Welshgasman]

Well how many combos do you have already?, as you will need to modify all of them except the errant one.?

[DMT Dave]

There are only about 6 or 7 using the same data from the same table, this table is only updated quite occasional as its storing brands of products and not daily updating

[Welshgasman]

Thinking a bit more about this Dave.

I would go for a new field in that table that states whether the entry is regular or not.?
Then in most of your combos only select those that are regular, and for the errant one select everything. You could even have a date field that says whether they are still in use or not.
That way if you have yet another errant entry, you do not have to change the code, whereas with IN() you would?

Make sense?

[DMT Dave]

Thanks WGM, yes all makes sense, sorry had to dash last night so back to it now:

Totally makes sense to me, I could have something a text field called Display, update all to Yes (the word Yes) then remove the word Yes out of specific records, i guess this would do the trick

Then tell the combo Where Is NULL(Display) from tbl etc....

Thanks again WGM............

By the way i must confess from a previous post, I NOW PRESS SAVE EVERYTIME I WORK ON ANY DATABASES

[Welshgasman]

Well I honestly would make the field boolean.

Then I could just have

Select field1, field 2 from table where Display is True for all the standard combos

[DMT Dave]

Yes i think in one of my earlier posts of have a yes/no field

Thanks for your input

Kindest

[moke123]

I wouldn't rely on doing updates to a boolean field. Why have more moving parts than what is needed.

I would just add the value to the table and adjust the rowsource to include or exclude the unwanted values.

For instance you have a table with 5 records and only want 4 in the combo. Just add <>5 in the criteria to exclude the record with a pk of 5.