Access 2007 View raw table with ID columns


In Access 2007 I am looking at the Northwind database at the table Orders.
At the moment I can see eg Employee rather than Employee ID. How do I view
the table with the IDs in certain columns?
Murray BrownHead DeveloperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

John TsioumprisSoftware & Systems EngineerCommented:
The table column uses a Lookup ...go to Table design (lookup tab) to change it from combobox to text box and you see the underlying value

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
No points please.  Yet another reason that table level lookups are bad.  They obfuscate the actual value of a column so if two customers have the same name - John Jones but are actually different customers, you would never know it..
Murray BrownHead DeveloperAuthor Commented:
Thanks John and thank you Pat. I allocated no points as I think you wanted
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

John TsioumprisSoftware & Systems EngineerCommented:
I don't think Lookup is bad...its just not end tries to present human readable data on table data but probably it should include the info that what you see is not what it's stored...probably a simple switch when viewing the table would be most helpful
You're welcome Murry.
John, So you're quite OK with two customers named John Tsioumpris, one good one bad both being reported as paying late?  That's the kind of stuff that happens when you obfuscate data.  Lookup fields are bad.  They are a crutch for people too lazy or too unknowledgeable to write a query.  Lookups belong on Forms (or reports) not on tables.  And for the same reason, I never format fields at the table level when that formatting could hide data.  For example, formatting a date field to show only the date and not the time could easily impede problem resolution if someone made the mistake of using Now() rather than Date() to put a date into the field.  If your query uses "=", that date with the time will never compare equal and unless you remember you formatted the table, you'll spin your wheels looking for the bug because you won't know that some, but not all, records include a time component.
Murray BrownHead DeveloperAuthor Commented:
Pat that makes a lot of sense.  Lookups surely should not be used at table level. John I also see the point in making it more readable but as you say it would be nice to see both pieces of data
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.