Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2021
    Posts
    4

    Excel connection to Access not returning correct data (ID rather than lookup value)

    Hi all,



    Complete newbie with access and trying to simply keep a database of all of our products to be sold and updating our master excel worksheet/proposal generator as needed.

    I have a table with a few fields with lookup values as the data type.

    When I connect to excel and refresh the connection, excel shows the ID value associated with the record, NOT the actual lookup value.

    Any ideas on what I am doing incorrectly?

    Any help is greatly appreciated!


    /mike

  2. #2
    Micron is offline Very Inert Person
    Windows 10 Access 2016
    Join Date
    Jun 2014
    Location
    Ontario, Canada
    Posts
    13,423
    Cross posted https://www.mrexcel.com/board/thread...shing.1175016/

    You should declare wherever you cross post that you did so, even if you got no answers. Maybe read Cross Posting Message

    Maybe your issue is that you're using lookup fields in Access tables - don't. The value you see is actually stored somewhere else and is not viewable in tables. The real value in the record is an ID number. You might get away with using .Value in your query field name; e.g. Orders.Value Memory fuzzy on that because I don't use them.
    The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
    Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
    About calculated table fields - http://allenbrowne.com/casu-14.html
    About Multi Value Fields - http://www.mendipdatasystems.co.uk/m...lds/4594468763
    The more we hear silence, the more we begin to think about our value in this universe.
    Paraphrase of Professor Brian Cox.

  3. #3
    Join Date
    Jun 2021
    Posts
    4
    my apologies. didn't realize i had to notify of a cross post between 2 sites. thanks for the recs.


    Quote Originally Posted by Micron View Post
    Cross posted https://www.mrexcel.com/board/thread...shing.1175016/

    You should declare wherever you cross post that you did so, even if you got no answers. Maybe read Cross Posting Message

    Maybe your issue is that you're using lookup fields in Access tables - don't. The value you see is actually stored somewhere else and is not viewable in tables. The real value in the record is an ID number. You might get away with using .Value in your query field name; e.g. Orders.Value Memory fuzzy on that because I don't use them.
    The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
    Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
    About calculated table fields - http://allenbrowne.com/casu-14.html
    About Multi Value Fields - http://www.mendipdatasystems.co.uk/m...lds/4594468763

  4. #4
    pbaldy's Avatar
    pbaldy is offline Who is John Galt?
    Windows XP Access 2007
    Join Date
    Feb 2010
    Location
    Nevada, USA
    Posts
    22,652
    Post 3 was moderated, I'm posting to trigger email notifications.
    Paul (wino moderator)
    MS Access MVP 2007-2019
    www.BaldyWeb.com

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 5
    Last Post: 10-20-2015, 06:43 PM
  2. IIf function Not Returning Correct Calculation
    By MAFuser in forum Database Design
    Replies: 7
    Last Post: 08-13-2015, 06:46 PM
  3. VBA Lookup Function to Access Returning #value
    By troygeri in forum Queries
    Replies: 2
    Last Post: 05-26-2013, 08:50 PM
  4. Replies: 9
    Last Post: 06-26-2011, 09:14 PM
  5. Import to Excel from Access column of LOOKUP data type
    By Derek in forum Import/Export Data
    Replies: 1
    Last Post: 12-06-2010, 06:27 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums