Results 1 to 5 of 5
  1. #1
    Join Date
    Sep 2006
    Posts
    28

    Unanswered: Simple?!Creating a query with multiple tables

    I have 5 tables with the same primary key (valve description) defined in each and an enforced referential integrity relationship between each one.

    When I try and create a query to combine each table the query will not run and states

    Caanot join on Memo, OLE, or Hyperlink Object ([tb:Automaticdates].[Valve description]=[tb:Buying].[Valve description])

    I know I muct be doing something stupid but I'm new to this so any help would be very much appreciated!

  2. #2
    Join Date
    Sep 2003
    Location
    MI
    Posts
    3,713
    Stupid only in that trying to join on a Memo which Access does not allow ... Try modding your tables to add a different type for your PK ... You do know why Memo's can't be keys dontcha????
    Back to Access ... ADO is not the way to go for speed ...

  3. #3
    Join Date
    Sep 2006
    Posts
    28
    Ok thanks that makes sense!
    Why can't memos be PK's?!

  4. #4
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926

    Memos not being Primary keys

    I was going to respond on this but this one's all yours M Owen (sorry I forgot your first name).
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  5. #5
    Join Date
    Sep 2003
    Location
    MI
    Posts
    3,713
    Quote Originally Posted by pkstormy
    I was going to respond on this but this one's all yours M Owen (sorry I forgot your first name).
    It's Mike ...


    But back to the story ...

    PK's can't be empty or null. You can block this in a memo too.
    PK's MUST be indexed. Memo's cannot be ... AH HA!
    PK's are sortable. Memo's cannot be ... AH HA!
    PK's Sort/Index on the value in the column. Memo's have an OFFSET ADDRESS as a value for the column (hence, when you get the dreaded ######### showing you know what it means ... The address to the actual data is lost) ... OOPS!

    Need I go further?
    Back to Access ... ADO is not the way to go for speed ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •