You would be correct in this. If you look at the SQL that is generated, it attempts to do an and on the same copy of the table, instead of doing a join on different copies of the table. This would be a good enhancement request to submit to LANDesk, if the same attribute is used for a one to many component, then do a join instead of using the instance of the table. Of course there would be instances where poeple would want this precise effect. This one of the difficulties in trying to convert something that is more user readable into SQL statements, there are ambiguities.