Sage 100

Upgraded a client system to Sage100 2014 SQL, from mas200 4.40. saved report names are not visible in Sage100 2014 SQL (you only see STANDARD). Even if you create a new saved report setting, you cannot see it in the lookup, and therefore you cannot select it. Saved forms settings are also not visible but work if you manually enter the form code. Sage reports it has something to do with SY_ReportSetting.M4T, but is unclear on exactly how to resolve this - has anyone seen/ experienced this, and do you know what the resolution is... Thanks

I had something similar to this, though not a SQL installation. It was corrected by restoring the Providex.* files found in the root MAS90 folder, but I'm not sure if that would apply for a premium system.

Jeff, I'm having this exact same issue on a Sage 100 2013 SQL installation right now. Do you recall what the fix was? Was it actually the Providex.dde and Providex.ddf files?

I will check and get back to you - it was a ""super hassle""..... but once you fix it, the reports will magically show up !

the issue has to do with the position of the workstation name within sy_report setting.... [Found the problem: the WorkstationName field is out of order in the dictionary. How it came to be out of order? Not sure but adjusting the order will fix the issue. See below for how the table looks when in the correct order.]

Thanks, Jeff! That is an interesting issue that would have taken me a LONG time to identify. Is it possible for me to access Data Dictionary Maintenance without being a master developer? I've never done this before.

This is a tough problem - Sage said it was not their issue, and that it was caused by a Master Developer - do you have or have you had any enhancements on the old or new system ?

There are no enhancements now. They used to have an add-on for Trucking back when they were on v4.3. They used v4.5 for ~2 years without issue before upgrading to v5.0 SQL where this has likely been a continuous problem, but only recently got escalated to my attention.

You may need to contact Sage or possibly the MD - this was a ""bear"" for us to resolve.....