I've tried everything - deleted and recreated the databases in Database setup.  Deleted and recreated the database connections in Crystal.  Commented out the .dll lines in the ini file (although I don't think this was the issue as we have other companies using the same types of forms and they work with no prompt for SQL credentials) but I tried it anyway.  Copied over the report from the old server and started over, still the same result.  I am still wondering why in the properties of the two database connections one shows a database property (this one works with no issues) but the other does not (this one prompts for SQL credentials).  The ODBC DSN's are identical in setup other than the database they are pointing to on the SQL server.  As are the database setup in Sage.  Don't know what else to try....  Thanks everyone for the suggestions.

Can you use the DSN created by Sage 300? (Update it in the Crystal report by going to Database > Set Database Location.) I think "old school" idea of having a DSN per company is what is creating the issue for you.

The DSN created by Sage 300 should be the name of the SQL server... possibly with a "32" at the end if you are using Sage 300 v2016 or earlier.

Can you use the DSN created by Sage 300? (Update it in the Crystal report by going to Database > Set Database Location.) I think "old school" idea of having a DSN per company is what is creating the issue for you.

The DSN created by Sage 300 should be the name of the SQL server... possibly with a "32" at the end if you are using Sage 300 v2016 or earlier.

Thanks, I did try this but with the same result - prompting for SQL credentials.

All these reports work on the current live server using Sage 300 2017.  We migrated them to a new Sage App server with Sage 300 2018.  Only some of the migrated reports are working without prompting for credentials

You could always try setting the ODBC connection to use Windows Authentication, then give the required windows users READ access to the database (by creating them within Security/Logins in SQL).