Pure Krome
Thanks heaps John for the prompt reply
Thank link definately does help. It's what i thought someone was going to say -> parset he VE results, as opposed to some really simple and clean XML schema result.
I was also hoping it might return the break up of the address, very similar to MWS and Googles REST service. (eg. addressLine, primaryCity, SecondaryCity, Subdivision, CountryRegion).
You suggested to use MWS (which is an excellent service btw .. i should know .. we use it .. yep, a paying MWS customer) but i've found that it doesn't work very well at all for a SINGLE search line, while VE handles a single search argument really well.
For example.
In VE, if i search for Victoria St, Richmond, Australia (http://dev.virtualearth.net/legacyservice/search.ashx a=&b=600%20victoria%20st,%20richmond,%20vic,%20australia&c=0.0&d=0.0&e=0.0&f=0.0&g=&i=&r=0) ... i get the lat long and the fully formatted address.
If i search for Richmond, Australia (http://dev.virtualearth.net/legacyservice/search.ashx a=&b=richmond,%20vic,%20australia&c=0.0&d=0.0&e=0.0&f=0.0&g=&i=&r=0) ... i also get the lat long + formattedAddress.
Kewl!
In MWS, if i search for a non-street using a single formatted address property to search for that address, i get street related results. It's like VE has the smarts to figure out that the thing u're searching for might not be an address .. and if that's the case .. it correctly finds it (eg. Melbourne, Australia .. as described above). But MWS, using the single address proprty for searching .. always looks for street level results
Very frustrating at times 
I also used FIDDLER to see what code the VE Javascript does to 'call home' when i do a VE search .. 
why can't things be so simple