Unfortunately, I don't know of any workarounds for the bad ERC because the problem is in the back end (i.e., the estimatedResultCount comes straight from the server). And Google has been characteristically quiet on the matter. There are, however, a number of threads in the issue tracker relating to the matter (links below).
http://code.google.com/p/google-ajax-apis/issues/detail?id=32 http://code.google.com/p/google-ajax-apis/issues/detail?id=4 Jeremy R. Geerdes Effective website design & development Des Moines, IA For more information or a project quote: http://jgeerdes.home.mchsi.com [EMAIL PROTECTED] Unless otherwise noted, any price quotes contained within this communication are given in US dollars. If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Oct 18, 2008, at 4:44 PM, Stealth wrote: > > From reading other discussions it appears that there is a bug in the > estimatedResultCount when using this API. I'm designing a site where > this number is extremely important, but it often gets the wrong > result. It is just inconsistent! > > I'd like to direct this to someone working at Google. Is there any > ETA? Is there a work around? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google AJAX API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-AJAX-Search-API?hl=en -~----------~----~----~----~------~----~------~--~---
