Sage 100

Paperless office issue - v4.5.4 on a WIn XP SP2 machine. No 100% hits on the KB. I suspect that it is a CDintf.dll issue. The one that keeps appearing in the system32 folder appears to be the 64 OS version. For the life of me, I can get the 32 bit version to stick. Help......

What's the initial error before you hit Info?

Reader launches then it throws a message that the file is corrupt

What version of Adobe? http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=508867

Or this: http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=503023 Or this: https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Gated%20Customers/Warr_Svc_Support%20Plan/524104.html I'd go with the second one first....

Thanks, I personally think it is the Adobe 6 issue. Will report back...

Error 15 means ODBC error which is strange here. Not sure it would help but if you click Info then Debug this command would show the actual ODBC error ? MSG(-1)

I ended up punting to Sage. Let the client use one of their ""free"" cases......

First round response from Sage. When client uninstall Reader 6, they install Reader 11. Sage said to uninstal Reader 11 and install Reader 10. I'm thinking WTF. Client did as instructed and now they are calling Sage for round two. Still doesn't work with Reader 10.

@JeffSchwenk - suggestion: have them uninstall all Adobe products and install Nitro Reader (free)

At this point, they've opened case with Sage. It is Sage's to fix now. Will report back with the solution.

Reader 10 (x) sometimes that has a similar problem to those that Adobe Reader 11. I usually go back to Adobe Reader 8.

For these problems I like Reader 8 and Nitro Reader too. But what I like even more so is Foxit Reader.

A little scary (or like Atlas) that the user is forced to stay several releases behind just to make it work. How do you explain this to the end user with a straight face? Sorry you have to stay on Windows XP because Sage hasn't taken the time to make the product work with later releases of mainstream software. And oh by the way, you are being asked to pony up an adiditional 17% for business care just so the product continues to work with XP. Don't look behind that curtain! We are the great and Powerful OZ.... I mean Sage!!!!!!! Toto, we're not in Kansas any more.

Well, Sage punted on this issue. Spent some time looking bit end didn't want to spend any time truly fixing it. Back to square one.