Is this a cascading combo issue?

[Chaz]

Hi,

I have a form that uses combos and looks up via a query.

When I use the lookedup value for a 2nd time in another form, I only see the number, not the name.

All my forms are being based on queries - maybe making it hard on myself, not sure.

I have a relationship built between the source table and the next table. I then lookup to this 2nd table - do I need a relationship between the 3rd form / table and the first or second table?

Thanks

 

[pbaldy]

In your other form, I'd probably use a another combo box to add/display/edit the data. That combo would get its choices from the appropriate table. The ID column would be the bound column, but the text column would be the one displayed. I don't think you need the lookup table in the source of the form.

 

[SOS]

Sounds also like you might be using lookups at table level. I would remove those if you are.

 

[Chaz]

Sounds also like you might be using lookups at table level. I would remove those if you are.

Mmmmm. I have them to see data in tables (to check detail) but the lookups are all created by me, not auto anything.

I use queries to find and populate teh data. Should I therefore have no lookups at all on table level? Happy to remove them ...

 

[SOS]

Mmmmm. I have them to see data in tables (to check detail) but the lookups are all created by me, not auto anything.

I use queries to find and populate teh data. Should I therefore have no lookups at all on table level? Happy to remove them ...

If you look at the link I gave you will see that the behavior you describe occurs because of the lookups at table level. You are fine to use them initially to create your forms (I don't do it but I know several who do) and then you remove them. If you don't remove them, then they wreak havoc on various things that NORMALLY work well.

 

[Chaz]

What I wanted to add, is that I use numbers only to store lookedup values in tables. I use referencial integrity which, if I understand correctly, quickly shows issues (numbers only).

Does the query to show the lookedup value in the table view (my use, not for users) create problems?

 

[SOS]

Does the query to show the lookedup value in the table view (my use, not for users) create problems?

Yes, it does. You can use a regular query to display the values, just not using a lookup to do it in the table.

 

[Chaz]

Yes, it does. You can use a regular query to display the values, just not using a lookup to do it in the table.

OK, so just to confirm (sorry Im labouring on this - want to get it right), for my tables I should not have any form of lookup, even if I manually created them and are searched by queries (and not the select gunk that MS puts in when you 'auto create' these), I should not have them and should therefore ALWAYS only see numbers in my table views (own use, not users) to check things etc?

 

[SOS]

OK, so just to confirm (sorry Im labouring on this - want to get it right), for my tables I should not have any form of lookup, even if I manually created them and are searched by queries (and not the select gunk that MS puts in when you 'auto create' these), I should not have them and should therefore ALWAYS only see numbers in my table views (own use, not users) to check things etc?

The answer is -

If you want to view the data that the numbers represent, build a query, from the query window, to view when you want to see it. The LOOKUP tab on the field in the table should say TEXT BOX and not Combo Box or List Box.

Also, make a copy of your database before making changes so you can revert if necessary, but you should not have a problem after going to the fields that have COMBO BOX or LIST BOX shown on the LOOKUP tab in the table and changing it to TEXT BOX.