Sage 100

What tricks, if any, do I need to change a connection string from SOTAMAS90 to a newly created SQL connection for a premium user ? In this case an end user is upgrading 2014 Standard to 2018 Premium and they have a treasure chest of Crystal, Excel, Access reporting connected via traditional SOTAMAS90 and since we need to create a new ODBC to point to SQL I'm pretty sure the connection string is going to change.

We use a DSN, and with SQL it is one DSN = one company code. (Nothing dynamic like SOTAMAS90). SQL accounts are not as good as Windows domain accounts, because SQL DSN's don't save the password. With things like Excel, create one query with the new DSN and copy the connection string over to existing spreadsheets.

I'm creating a DSN Sage_XXX where XXX is the company code. Hopefully I can swap out the SOTAMAS90 for SAGE_XXX without having to relink tables, etc.

There may be some oddities with data type, when converting tables with date fields (which are date/time in SQL).

Is there a way to create a DSN-less connection for Excel instead of having to go workstation to workstation and creating an ODBC to the SQL?

I never use it because it puts the settings (server, instance, database name...) in each spreadsheet (instead of one DSN), but you might try the direct SQL Server type connection, instead of MS Query / DSN.