Sage 100

ODBC Connection error .. I just came across this fix to resolve and thought I would pass it on When the below screen displays. Click the Back Button Select Data Source Select SOTAMAS90 DSN Click Finish Once the report is run from within Sage 100 it will store off a valid connection string. *Note: Starting with the 2013 (5.0) a connection string is passed to Crystal Reports at runtime to retrieve Sage 100 data and render the report. The SOTAMAS90 DSN is no longer used, but maintained for backward compatibility.

Thanks for sharing, Jim. Good to know.

That explains why we periodically have issues if we edited a report using Crystal on a client. During upgrades, we added this step of using a UNC path in the Crystal Reports conversion wizard. This may have implications with the C/S odbc driver too.

I've seen this too as a symptom of permissions issues. If the user isn't set up properly in the domain, this ODBC connection error will occur.