if you build the report with SQL ODBC Driver 16, and the client only has SQL ODBC Driver 14, this kind of thing can happen.

Mike peat started a thread the other day that had some of these issues, basically pull the cDRReportMSSQL class out of Plato and use that. It *should* pull the entire connection string used by an open table in the application to build the correct connection string on the fly.