This project has moved and is read-only. For the latest updates, please go here.

Beware: Browser Chooser freezes MS Excel Web Queries

Aug 1, 2011 at 5:07 PM

I'm a web analyst and I love using Browser Chooser. 

But I have come across an issue with MS Excel recently that racked my brains for days. 

I was pulling data via a web query using external data sources into Excel.  After installing Browser Chooser, Excel froze on me.  This was because when Excel was going to fetch the URL, Browser Chooser intercepted the call and prevented the query to be fetched as it was waiting for the user to make a selection. But the strange this in, Browser Chooser's UI was not being displayed, hence Excel got stuck in limbo and just froze.  Once I killed BrowserChooser, the Excel Web Queries ran fine.

Hence a work around would be for Browser Chooser to check what Application is making the call and if possible allow exceptions.  So for example if a query is coming from Excel, just pass through to Internet Explorer and do not prompt user for a selection.

Are other people experienced a similar kind of issue?

Aug 26, 2011 at 3:08 AM

Could it be because BC has been made the default app for all things http:// related?

How is the query obtaining data, and do you think it is possible to remove the app association between BC and the query method so that the query doesn't get intercepted by BC?

Aug 26, 2011 at 7:32 PM
Hi Johnlgalt,

Yes, the reason why Excel freezes is because it's trying to access
data located a http://
hence BC takes over and because BC is waiting for a human response
before it can fetch the webquery, and so it gets stuck.

Does anyone know of a way inside Win7 to tell me to only open a
http:// requests in Internet Explorer when inside Excel, and not the
system default being BC?



On 8/26/11, johnlgalt <notifications@codeplex.com> wrote:
> From: johnlgalt
>
> Could it be because BC has been made the default app for all things http://
> related?How is the query obtaining data, and do you think it is possible to
> remove the app association between BC and the query method so that the query
> doesn't get intercepted by BC?
>
>