Sage 100

we have a client that had a server crash (or something similar) now we keep running into issues where lookups are showing incorrect data in the columns - we called Sage and they suggested adding a UDF to the table - that forces the data dictionary to be recompiled. That works but we have now added udf's to 4 tables. I don't know how many more times the client is going to call and tell me there is another lookup with an issue. Does anyone know if the old SVCMPL legacy code will recompile all tables? Is there a new way to force a recompile of all tables?

I think this still works: 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.

SVCMPL allows you select the business framework modules, so if it doesn't work it's very deceiving. But I recently had a case with Sage where Steffan at Sage recomplied the SO module using a different method. I was going to follow up with him to see exactly what he did, but maybe someone else knows - actually Wayne just posted it - I would probably use that method to be safe because it tells you it was successful.

Thanks to Wayne. (and Eric) Sage should give us a tool instead of popping out to Providex commands.

You may have already done this, but if not I'd strongly suggest you guys 'kick the crap' out of the system and run every important report and test every function. You don't want to find out 3 weeks from now when they say run a sales tax report or Commission report that the data files are beyond repair and now you can't fallback to a backup. If this file got corrupted, there is a reasonable chance something may have also.

they've been testing all day before putting ANY data in just for that reason - I do appreciate the thought. in fact those are two they may not have thought of yet.