Sage 100

 View Only
  • 1.  Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 08:17
    Error 90 SWQUERY at line 29020 using ALE to export any lookup to Excel 2007. Client is using MAS 90 v4.05 I've suggested to the client that this is an Excel issue to which they claim to have downgraded to 1997 and continue to receive the message. A brief review of Sage online seems to indicate that Excel 2007 isn't supported -- and my experience with Excel is that it's very problematic to get a clean import/export to differing versions. There always seems to be one particular version that Sage integrates with.


  • 2.  RE: Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 08:21
    I don't think Excel 2007 was supported until V4.3


  • 3.  RE: Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 08:21
    BTW, I did receive a email notification on this one. did you fix something?


  • 4.  RE: Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 08:25
    Me too -- now the notifications seem to be working. With respect to this issue I'm stuck in that ""can you support my hardware guy who is trying to .... "" no mans land. The hardware guy is telling the client that I'm full of shit and that it can't possible be the Excel version. I've learned these are no win battles but I want to be sure there's not something I'm overlooking. Both AP and AR give the exact same error message. I've no idea what they did to remove the old Excel and install the new but I also offered several workarounds to them. Unfortunately this client is on the hunt to get rid of us after they've pretty much lost all their staff --and in those instances you get these really aggressive inquiries that they expect you to follow the error message all the way to engineering at Sage and bring home an answer about why Sage has a problem.


  • 5.  RE: Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 10:30
    Sage claims no idea on this one. Setup for a callback and more dog and pony show. Ultimately I'm being asked to support ""the IT guy"" which royally pisses me off to no end


  • 6.  RE: Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 13:40
    I have had issues in the past with an error exporting the ALE to Excel. It was always bothersome as I couldn't replicate it. Never bothered calling Sage for the ""yes, we charged you a case, but we don't have a clue"" response. Then one day I noticed that I had modified the ALE after it returned data (usually just by resorting a column), I got the error. If I didn't modify the lookup, it exported. Have them try exporting the ALE IMMEDIATELY after it returns data. Don't touch anything in the lookup! Just export it to Excel.


  • 7.  RE: Error 90 SWQUERY at line 29020 using ALE to expor

    Posted 10-13-2010 13:43
    Thanks I tried that and it didn't work. I also tried using the standard lookup and a different company code, different modules. All are producing the same error. Client has an acceptable workaround but pressed for a case so I registered the case with Sage.