Sage 100

 View Only
  • 1.  Perhaps I've overlooked this or there is something

    Posted 05-09-2018 10:54
    Perhaps I've overlooked this or there is something I am missing. I did a Sage 100 Advanced 2014 to 2017 Premium upgrade a few years back. I seem to remember those users could continue to make use of their SOTAMAS90 ODBC which meant I didn't need to make changes to reports for a new ODBC source. I'm doing a 2014 STANDARD to 2018 PREMIUM. And on workstations where there **never was Sage installed before** the SOTAMAS90 is not present. When I try to create it manually I get a login failed. I can create a SQL connection but think that means I'll need to get to every standalone report and swap the SOTAMAS90 for the new connection to SQL. Is there a way to continue using SOTAMAS90 for those users who don't need an immediate connection to SQL tables. I had originally thought that I'd keep them on SOTAMAS90 and gradually migrate them.


  • 2.  RE: Perhaps I've overlooked this or there is something

    Posted 05-09-2018 12:07
    The SOTAMAS90 ODBC connection is to the Providex DB. It will be useless for the Premium install. In the past, I had to set up the SQL ODBC for users that needed to connect to the MAS database tables from outside MAS. If they are inside MAS, there is no need obviously but from outside MAS, my experience is that a new ODBC has to be created.


  • 3.  RE: Perhaps I've overlooked this or there is something

    Posted 05-10-2018 03:31
    Thanks - on my previous Premium UG the customer had a lot of external reports. I didn't remember going through extra effort to convert them and I think that's because they they handled those conversions themselves. The Premium install doesn't require replacing SOTAMAS90 for forms and/or custom reports that have been added directly to the Sage menu. For external data connections a new SQL based source needs to be created.


  • 4.  RE: Perhaps I've overlooked this or there is something

    Posted 05-10-2018 16:44
    If you set a SQL Client connection in the report then you don't need to set up a DSN on each computer. You do need to know the password for the MAS_Reports user in SQL.


  • 5.  RE: Perhaps I've overlooked this or there is something

    Posted 05-11-2018 12:35
    It uses a SQL OLE DB connection, not SOTAMAS90 ODBC.