Sage 100

 View Only
  • 1.  V2016 Premium. When I add a UDF to any table, one

    Posted 09-08-2017 05:53
    V2016 Premium. When I add a UDF to any table, one company (the main one, of course) does not get updated with the UDF. Custom Office looks OK when I do this (no errors), but when I go to the table, it doesn't contain the UDF. Yes, something happened a few weeks ago and we've been trying to fix since. We brought back the data dictionary files from before the issue. We're making sure all pvxwin32.exe and anything linked to that company isn't running. Has anyone every seen this or have some insight? We're making a development environment today, so we can look at this during the workday. Thanks.


  • 2.  RE: V2016 Premium. When I add a UDF to any table, one

    Posted 09-08-2017 06:26
    What SQL permissions does the MAS_User account have against that company's database? It sounds like it's missing the ALTER SCHEMA permission. Or you can cheat and give it dbowner to see if that makes a difference...


  • 3.  RE: V2016 Premium. When I add a UDF to any table, one

    Posted 09-08-2017 06:26
    What does this look like inside SQL Studio? Is the UDF added to the appropriate table? If not, you could try to refresh the table to see if that helps.


  • 4.  RE: V2016 Premium. When I add a UDF to any table, one

    Posted 09-08-2017 06:29
    The DBO should be MAS_User.


  • 5.  RE: V2016 Premium. When I add a UDF to any table, one

    Posted 09-08-2017 06:39
    Thanks so far. In SQL Studio, it's added to all companies but the main company. I'll look into the other info. I'm just learning SQL, so this is becoming a crash course for me!


  • 6.  RE: V2016 Premium. When I add a UDF to any table, one

    Posted 09-08-2017 07:29
    use MAS_###; exec sp_changedbowner 'MAS_User';


  • 7.  RE: V2016 Premium. When I add a UDF to any table, one

    Posted 09-18-2017 08:22
    Thanks everyone for your input! I write my results here, in case anyone else has the same issue, it's nice to see a resolution. It ended up that we needed to turn off SQL replication in two places. First for MAS_XXX and for MAS_System, in SQL studio, chose View Log Read Agent Status and changed to Stop. Then, went into Properties--Articles and unchecked every table for MAS_XXX and MAS_System.