Sage 100

 View Only
  • 1.  Sage 100 ERP upgrading 4.30 to 2014 -- when I go i

    Posted 04-27-2015 07:57
    Sage 100 ERP upgrading 4.30 to 2014 -- when I go into the VI and try to look at the existing jobs it errors out with a message about a missing FL.ACCOUNT table. I'm able to get by the error by setting VI_Options.M4T to be the current version. However now when I try to create a fresh new VI job in 2014 it only shows about 4 FL tables -- as if the conversion of data somehow stalled/stopped and while I was able to get into the tables it's not going to let me create anything unless it's based on one of the FL tables it managed to convert in the dictionary. 1. I've been searching Sage and Evernote on the way to manually rebuild this data dictionary -- and have come up with nothing. Anyone have a document at hand or is this one of the weak ""reinstall everything"" workarounds which seem to pervade dictionary related issues? 2. Anyone else run into this and have suggestions on how to get around it other than a fresh install?


  • 2.  RE: Sage 100 ERP upgrading 4.30 to 2014 -- when I go i

    Posted 04-27-2015 07:58
    Stumbled upon this: 110-500846 - How to replace embedded IO files Entry Type: Informational Product: Sage MAS 90 ERP, Sage MAS 200 ERP Application: N/A Version Reported: 4.10 and later Subject: How to replace embedded IO files Possible Resolution: On the File menu, click Run. In the Program field, enter SYZCON Click OK. At the prompt, enter O=NEW(""SY_ACTIVATION_BUS"",%SYS_SS) Press ENTER. At the prompt, enter PRINT O'ACTIVATE(""y/y"",""xxx"") Notes: y/y = module (for example: S/0, C/I, I/M, and so on) xxx = company code 1 is returned if the last command was successful At the prompt, enter bye Press ENTER.


  • 3.  RE: Sage 100 ERP upgrading 4.30 to 2014 -- when I go i

    Posted 04-27-2015 08:07
    This appears to have worked - and I only ""rebuilt"" AR and AP before checking in VI to see if the tables were there. When I check in VI all of the tables appear to have been rebuilt --- so it does not appear as if you need to go through each module one by one. Rebuilding only one seems to kick off a rebuild for all the tables. I know this has been shared before online - and is not news to most. Just closing the loop on how I resolved.