in clause - MS Access IN operator not returning rows -

Using an MS Access database (I know), the question below

  SELECT * FROM page image (page image.) ('1'); 'Page Image Single values ​​in the 'Room' column, such as 1  
 only 'page image. The actual data stored in the 'rums' column is a comma when only  

returns the row, a separate list such as 1,2,3 stored in the string, but when this is the case No data is given.

From the above query & amp; Referring to the picture below, only 342 rows are returned, when I have to return 341,342,343

Given that PageImage.Rooms is an actual comma- Store a delimited list as you specify in a comment (i.e. this is not an Access 2007+ multi-value field), you actually make a bit of a disturbance Or is this a table with a column that is not fully normalized for that reason (the first not in general). Queries and data stability issues have to be expected.

The usual way to model multiple-to-many relationships such as you will have with a separate table in this case, however, because the page image unit has no data other than its ID, You can do it in the same table. Either way, whatever table model relationship each should have a separate row for each (PageImage.Id, Cell) pair, and those pairs should have a composite key for the table.

You are now with the structure, the question you want can be implemented in this way:

Select the image from the page Page Page Image.Rooms = '1' Or PageImage.Rooms '1, * or' Page Image Like '*, 1' or PageImage.Rooms Like rooms '*, 1, *'; As the

was observed by Lord Thompson, which can be expressed more strictly, and perhaps more efficiently, select the page from

page ( ',' & Amp; Page image. Room & amp; & # 39;; & # 39;), like '*, 1, *';

As you can tell, if you want to compare multiple room numbers against the same query in the same query, then it gets worse.

Bottom line: Strings with comma-delimited lists As far as the database is concerned, the wire.