Thanks David. I didn't think object_id was it then tried package_id and no difference.
Spot on Simon! the ea_guid as CLASSGUID worked a treat!. the ea
_guid is suppressed on output (even better). The help implied it was used to link an object so properties dialog can be displayed. I should have tried it anyway...
To help our community, here is the useful little SQL search for finding any duplicate objects with a stereotype of "application". Omit the search term and it will find all.
I've also found some "#ifdef" type directives you can use in your SQL query searches that allow you to code different syntaxes if using the same search against say a local EAP and central RDBMS. I'll post these in due course. Them Sparx boys have thought of everything

select name, alias, note, object_type, stereotype, ea_guid as CLASSGUID
from t_object
where name + object_type in
(select name + object_type
from t_object
where stereotype = 'application'
and lcase(name) like lcase('*<Search Term>*')
group by name + object_type
having count(*) > 1)
order by t_object.name
Cheers