Sage 100

WTF, I am trying to trouble shoot VI from the server console and have run into this road block. The solution is to install Office 2000 or 2003???? Like the client is really going to burn a license on that. Does anyone know what the REAL solution is??? Resolution Details - Resolution ID 516791 TITLE : ""The object VI_ImportJobMaintenance_ui does not exist"" when opening Import Job Maintenance for Business Framework modules DETAILS : INFORMATIONAL ** THIS INFORMATION HAS NOT BEEN VERIFIED ** ""The object VI_ImportJobMaintenance_ui does not exist"" when opening Import Job Maintenance for Business Framework modules Entry Type: Informational Product: Sage MAS 90 ERP Sage MAS 200 ERP Application: Visual Integrator Version Reported: 4.30 Subject: ""The object VI_ImportJobMaintenance_ui does not exist"" when opening Import Job Maintenance for Business Framework modules Possible Resolution: Verify that Office 2000 (preferably Office 2003) or later is installed on that workstation

What type of file are you importing? If it is an excel file can you import a CSV (I know it changes the vi). :)

Either a CSV or a txt file. I hate xls files. I can't even get to the job itself (or create a new one) as this error blows before that step.

http://community.90minds.com/2010/02/20/mas90-vi__importjobmaintenance_ui-error-after-microsoft-patch/ HA HA HA @Harold already dealt with this in February of this year and it is on 90 Minds website! ;) Hope this saves you from hours of diagnostic work! Sorry Harold Had to say it. Harold was there a workaround other than upgrading to office 2007?

Wow, Harold had it first........... Personally, I can't believe that it is an MSFT issue. MAS should be able to run WITHOUT Office installed............

Install a trial version. Dumb solution, but it obvoiusly doesn't require RUNNING Office so expiration shouldn't be an issue. Better yet, ask them exactly what object comes w/Office that addresses the issue and how? Maybe it can be addressed w/o an install.

Ask Sage regarding the object ???

Yea, just go deeper. Why does Office solve the problem? Obviously Office has little directly to do with the VI UI.

You're joking right? Ask Sage to clarify one of their resolutions? If they can't figure out on a PR.dataent import to delete the JC validations so it will open in v4.4, you really think they can tell us what the real issue is? Maybe I'll post it on the community.

I guess if you attack the problem with every tool in your belt - that would include sarcasism :-)