E
Edwin Knoppert
I have a field in a table (TABLE2) with commaseperated keywordes for
example: "AA,BB"
Another table (TABLE1) has multiple (user)records field only having "AA" or
only having "BB" etc..
I would like to use a join on these fields like:
SELECT Table1.*
FROM Table2 INNER JOIN Table1 ON Table2.Field1 = Table1.Field1
WHERE (((Table2.Field1) Like ",NH,"));
However, i need fix the join instead, the WHERE was for testing purposes
only (and does not work obviously).
Pseudocode:
SELECT * TABLE1.*
JOIN TABLE1 WITH TABLE2 WHERE INSTR( TABLE2.FIELD1, TABLE1.FIELD1 ) >0
(Where TABLE2.FIELD1 = "AA,BB" and TABLE1.FIELD1 = "AA" or "BB" etc..)
Also problematic might be the lack of first and last comma.
The TABLE1.FIELD1 will be joined with the actual text these keys refer to.
I'm using ASP.NET v2 with OLEDB (MDB)
example: "AA,BB"
Another table (TABLE1) has multiple (user)records field only having "AA" or
only having "BB" etc..
I would like to use a join on these fields like:
SELECT Table1.*
FROM Table2 INNER JOIN Table1 ON Table2.Field1 = Table1.Field1
WHERE (((Table2.Field1) Like ",NH,"));
However, i need fix the join instead, the WHERE was for testing purposes
only (and does not work obviously).
Pseudocode:
SELECT * TABLE1.*
JOIN TABLE1 WITH TABLE2 WHERE INSTR( TABLE2.FIELD1, TABLE1.FIELD1 ) >0
(Where TABLE2.FIELD1 = "AA,BB" and TABLE1.FIELD1 = "AA" or "BB" etc..)
Also problematic might be the lack of first and last comma.
The TABLE1.FIELD1 will be joined with the actual text these keys refer to.
I'm using ASP.NET v2 with OLEDB (MDB)