Thanks Sergey, I thought that was the case but I haven't mastered reading the results to the sys(3054) yet. Do you know if there is something more user friendly/understandable available?

Many thanks
Caroline

>Hi Caroline,
>
>Your query is fully optimized because WHERE clause is optimized ("Using index tag Id to rushmore optimize table address") and JOIN is optimized ("Joining table address and table country using index tag Id").
>
>>Sorry to keep asking almost the same thing - but I think I'm finally understanding.
>>
>>If I have a view with 2 tables with Address indexed on iCounrty and iID.
>>

>>SELECT Address.iid, Address.maddress, Address.mstreet, Address.ccity,;
>>  Address.ccounty, Address.cpostcode, Address.nssc, Address.llondon,;
>>  Country.cname, Address.icountry;
>> FROM  ash!address LEFT OUTER JOIN ash!country ;
>>   ON  Address.icountry = Country.iid;
>> WHERE Address.iid = ?ThisForm.Address
>>
>>Using index tag Id to rushmore optimize table address
>>Rushmore optimization level for table address: full
>>Rushmore optimization level for table country: none
>>Joining table address and table country using index tag Id

>>
>>This is reporting the Address table is fully optimised while the Country is not optimised. Could this view be better optimise or is this all I should be aiming to achieve?
>>
>>Many thanks for any explanations.
>>Caroline