Working with SQL7 and Access 2k, I can't set the unique table property 

except for very simple select statements. Once I simplify the stored 

procedure enough I can set the unique table property and 

then "recomplicate" the stored procedure and have the unique table 

property remain. Is there a reason for this and/or and easier workaround? 

The procedure utilizes several outer joins, and WHERE statements filled by 

input parameters.