Sage 100

Error 90 SWQUERY Line 29020 -- client is getting this message when clicking the on the Excel icon and trying to export the ALE lookup. I've yet to observe but they claim it's happening on all workstations. The one I'm logged into has both Excel 97 and Excel 2003 remnants in the add/remove programs. I'm in the middle of no mans land where the IT staff have had their hands on the wheel and now that the car is inches from the guardrail they're asking me to quickly take the wheel... Sage thinks this SWQUERY message is an indication of corrupt ALE. They sent a pack of default lookup data files (SY1,SY2,SY3,SY3 and SYQDD). However since the client has enhancements I think the SYQDD couldn't be used -- and when we added it caused an error. So I've fixed everything except the damn ERROR 90 SWQUERY. Thoughts or dumb looks:?

Have you tried restoring the SOA\SWQuery files from backup?

The non business framework files were SY1Q01.SOA, SY1Q02.SOA, SY1Q03.SOA, SY1Q04.SOA and SY1QDD.SOA. I don't see any Business Framework files for ALE. You could try restoring those from backup tape as well. Error 90 seems to be related to corrupted files. I cannot look at SWQUERY, since it is a Sage protected program. Did Sage say what the line was doing at 29020?

Unfortunately Sage was pretty useless. My last call to them they suggested that I pickup a copy of the MAS_xxx folder and try it on my computer. I don't think that would work since the customer has enhancements which likely modify the dictionary for ALE. Sage sent generic files noted above for v4.05 and those seemed to bomb out any attempt to make a custom ALE which the client was not pleased with. The Error 90 persisted as well. I get the Error 90 across different modules -- so if it's corruption it's likely some type of common file.

Am I completely wrong thinking this could be an Excel version issue? On this customer I can see they have MS Office 97 and Excel 2003 installed. My next session tomorrow will be to try and access a computer with only one version of Excel showing in add/remove. Unfortunately the client has self supported to their detriment. Now all their IT folks are gone. They're bringing in third party support (IT People for hardware) and I don't know what's been mucked with. In the interim they likely had someone in ""cleaning up some data files"" -- again throwing more fun in the mix. Of course they play dumb and claim it's all support....

I love being sandbagged by clients. I'm not sure why they think omitting or being evasive to questions really helps them to solve problems. After further conversation the client casually adds -- oh yeah this happened right after we installed Office 2010. Not it's not definitive that the upgrade is causing this -- but I'd like to have known about when it started (they were very evasive) and what might have caused it.

I have recently encountered some compatibility issues with the MS Query component of Office 2010. Although the MS Query program appears identical to previous versions, the interface to Excel has changed and causes rejection of the embedded SQL - yet works with 2003.

They don't want to accept responsibility or that anything they've done could have caused the problem. Or the blame.

My WAG is that some component(s) of 2010 were left behind when they uninstalled and might be causing conflicts.

What version of MAS are they on?