QUickbooks and IE7

I see QB 2006 Enterprise listed, but not QB Pro 2006. Pro 2006 does indeed work with IE7 and Vista. It had problems downloading transactions with release 6, but R7 & R8 work flawlessly.

John

The other info (Pro Advisor newsletter) indicates that all versions of 2006 will work with IE7 when updated to version 8. As you said, it worked flawlessy when you updated to version 8.

|Microsoft will be releasing IE7 shortly through their automatic updates. |Before you upgrade to IE7 check this site to see if your version of QB will |work with IE7:

I'm using Pro 2004 in Vista RC2 and IE7 with no problems. One can only wonder if it's yet another way for Intuit to force users to upgrade to their latest buggy code.

Thanks... Brian

I can be reached via e-mail at cisco_dot_news_at_comcept_dot_net.

Hi Brian,

It's hard to say if older versions of a product will work with a beta Operating System or not. It's possible in some instances it won't and some it will. But for IE7, Intuit has found some problems with QuickBooks 2005 and earlier and is currently working on a patch to help these versions work with IE7.

Like all software, nothing is 100% because all computers are different. So what may work on your computer, may not work on anothers. Intuit wants to make sure no-one upgrades thinking it will absolutely work and they end up being that one-in-a-thousand that doesn't.

Hope I made some sense :)

Thanks! Amy

The fact that version 2004 has been sunset by Intuit, it is reasonable to assume that they have not and will not test that version with IE7.

QB 2004 will not be sunsetted until May 31, 2007.

Never mind.

You are correct. On the page that I posted here is what they say about 2004 or earlier:

"QuickBooks 2004 (Enterprise 4.0) or earlier: Requires Internet Explorer 6 and is not compatible with Internet Explorer 7. To continue to use these older versions of QuickBooks without interruption, do not install Internet Explorer 7. If you have already upgraded, we recommend that you revert to Internet Explorer 6."

So even though it won't be sunsetted until May 2007, Intuit has no plans to release a patch that will allow 2004 to work with IE7. So if you have clients that are still on 2004 or below you will need to forgo installing IE7.

Is this Intuit's sneaky way of getting us to force our clients to upgrade to a more current version???

This is the last straw. If Intuit thinks that users of older versions will forego upgrading to IE7 or be bullied into buying newer versions of QB, I say beware. Some - perhaps many - won't.

Intuit is less than informative about what the areas are in which the older versions of QB are incompatible with IE7. This is a material issue because, as far as I know, in most countries - eg South Africa where I am - QB only uses IE for downloads of updates. I could find no mention of IE7 on Quickbooks' UK or South African websites.

I have QB 2003 Pro UK and I had no plans to update it because I do not use payroll and am therefore not forced to update by the sunset policy. Improvements in later versions are either cancelled out by other retrograde changes or are of too little significance to me to justify the cost and hassle of upgrading.

If my version will be unable to download updates under IE7 and QB are not going to bother to issue a patch to make the upgrade utility compatible with IE7, I have a choice:

• accept being bullied into buying a more recent version;

• stay with IE6 indefinitely with its security flaws and limited features;

• live with my present version of QB as it stands without any further updates (of which there aren't likely to be too many anyway); or

• read the writing on the wall and switch to Microsoft Office Accounting.

QB is a competent accounting program and does what I need, but I have never felt any warmth or loyalty to it because of its user-unfriendliness in just too many respects and because I am antagonised by Intuit's arrogance in not listening to users' suggestions to make it more user-friendly and the blatant manner in which Intuit forces users to buy newer versions.

The last option - switching to MS Office Accounting - is therefore becoming more attractive by the day despite the huge hassle it will involve. At least I will have my pride intact for not allowing myself to be bullied any more. As far as I know, MS hasn't brought out a VAT module yet but when they do, I will give serious consideration to making the move.

Ken

This is the last straw. If Intuit thinks that users of older versions will forego upgrading to IE7 or be bullied into buying newer versions of QB, I say beware. Some - perhaps many - won't.

Intuit is less than informative about what the areas are in which the older versions of QB are incompatible with IE7. This is a material issue because, as far as I know, in most countries - eg South Africa where I am - QB only uses IE for downloads of updates. I could find no mention of IE7 on Quickbooks' UK or South African websites.

I have QB 2003 Pro UK and I had no plans to update it because I do not use payroll and am therefore not forced to update by the sunset policy. Improvements in later versions are either cancelled out by other retrograde changes or are of too little significance to me to justify the cost and hassle of upgrading.

If my version will be unable to download updates under IE7 and QB are not going to bother to issue a patch to make the upgrade utility compatible with IE7, I have a choice:

• accept being bullied into buying a more recent version;

• stay with IE6 indefinitely with its security flaws and limited features;

• live with my present version of QB as it stands without any further updates (of which there aren't likely to be too many anyway); or

• read the writing on the wall and switch to Microsoft Office Accounting.

QB is a competent accounting program and does what I need, but I have never felt any warmth or loyalty to it because of its user-unfriendliness in just too many respects and because I am antagonised by Intuit's arrogance in not listening to users' suggestions to make it more user-friendly and the blatant manner in which Intuit forces users to buy newer versions.

The last option - switching to MS Office Accounting - is therefore becoming more attractive by the day despite the huge hassle it will involve. At least I will have my pride intact for not allowing myself to be bullied any more. As far as I know, MS hasn't brought out a VAT module yet but when they do, I will give serious consideration to making the move.

Ken

I think the above is your best option. From what I can tell the problem will affect downloads and online activity (ie online banking) from within QB. I don't see how there'd be a problem doing manual downloads of statements or patches.

-- Tara

Thank God you didn't threaten to hold your breath. I guess your saving that for the release of Vista..

Just switch to a more secure browser like Firefox or SeaMonkey and having IE6 on your machine is no longer a real issue. I only use IE6 for Windows updates.

If your version of QB works for you and you can live with IE6 on your machine then this is your best option.

| |You are correct. On the page that I posted here is what they say about 2004 |or earlier: | |"QuickBooks 2004 (Enterprise 4.0) or earlier: Requires Internet Explorer 6 |and is not compatible with Internet Explorer 7. To continue to use these |older versions of QuickBooks without interruption, do not install Internet |Explorer 7. If you have already upgraded, we recommend that you revert to |Internet Explorer 6." | |So even though it won't be sunsetted until May 2007, Intuit has no plans to |release a patch that will allow 2004 to work with IE7. So if you have |clients that are still on 2004 or below you will need to forgo installing |IE7. | |Is this Intuit's sneaky way of getting us to force our clients to upgrade to |a more current version???

Again sorry to say that QB 2004 Pro works just fine with IE7. I've had no problems on any of our test systems (running either Beta 2 or RTM versions of IE7) XP Pro SP2 or Vista RC2. I seriously believe that Intuit is just trying to get folks to upgrade. Notice how they don't tell you what is wrong with IE7 only that it's not compatible. My 'Oliver Stone' attitude is all about Intuit's constant insistence on us 'upgrading' to new products that have no features I want or need and yet every 3 years I'm forced to upgrade. There's no technical reason why they can't sell their payroll upgrades for previous years, but they want that extra $200 from me and I guess I have to pay it. Anyway I'm running IE7 and QBW Pro and have yet to have problems. I do have my QBP 2007 disc here but haven't had the chance to install it.

You say there is no technical reason. Can we assume your are well versed in the engineering of the product? The fact that you are still on version 2004 tells me your not exactly on the cutting edge of technology. I personally am in favor of sun setting of software. It frees up resourses that can be better used to facilate new imporvements and support current customers.

Anyway I'm running

Modest correction: There is no "Explorer 7." There IS an "Internet Explorer

7." Explorer is part of the OS (like Control Panel or Device Manager).

As for problem determination, it is usually insufficient to describe what the program WON'T do. Please tell us what it DOES do when you attempt access.

Did a format and new install of Windows XP, from Win 98.

During reinstall of QB2004 pro, a message came up to downgrade from IE7 to IE6. Some gall, imo. Keep all the old stuff for the sake of intuit, or upgrade for $200.00 so I can use IE7. I ignored the warning and am use qb2004 anyway.

I do notice that I get script errors when accessing the help menus, but that's a small nuisance 'cause I can click and go on.

I experienced the same in quicken 2007, btw, but the last release fixed that.

I agree. Intuit should have designed QB 2004 to work with IE7. I don't care if that was impossible because it did not exist yet. Like you, I consider myself the center of the univerise.

Perhaps Microsoft should have spent more time developing IE7 so it would work with all legacy programs. Microsoft could have charged 200.00 for the upgrade to make up for the extra time spent. I'm sure a big spender like you would be more than willing to fork out the money.