Search results

  1. Q

    Query too complex - Acces 2007 (SP3)

    He is using this query on 2 different sets of tables. On the first set is a NULL value, on the second set there isn't a NULL value. Hmm...
  2. Q

    Query too complex - Acces 2007 (SP3)

    Ok, thank you very much. I'm going to try this ASAP.
  3. Q

    Query too complex - Acces 2007 (SP3)

    What is the best way to check this? Thank you very much
  4. Q

    Query too complex - Acces 2007 (SP3)

    Not that I am aware of, sorry. TABLE [table1] UNION ALL TALBE [table2] SELECT * FROM table1 UNIOAN ALL SELECT * FROM table2 Are those 2 query's the same?
  5. Q

    Query too complex - Acces 2007 (SP3)

    Yes, they are. (Also, worked before SP3, so the query must be right?)
  6. Q

    Query too complex - Acces 2007 (SP3)

    Re: Query too complex - Access 2007 (SP3) But it worked in previous versions of Access (without SP3). TABLE [table1] UNION ALL TALBE [table2] < Doesn't work. TABLE [table1] UNION TALBE [table2] < Works. SELECT * FROM table1 UNIOAN ALL SELECT * FROM table2 < Works, but I doesn't know this...
  7. Q

    Query too complex - Acces 2007 (SP3)

    A client is getting this error when he is trying to execute this query: TABLE [table1] UNION ALL TALBE [table2] I'm not sure if this query is right. If we use UNION (without all) the query works just fine. SELECT * FROM table1 UNIOAN ALL SELECT * FROM table2 the same as the previous querty...
Back
Top Bottom