1. Never link the memo table that way.  Use a sub-report instead.

2. It's probably your data source.  Make sure you use the exact same connection settings as the default.

Thank you Kevin,

It was the permissions in the SQL database that was preventing the connection.  I changed the permissions and was able to do a left outer join, and create a formula that specified the MEMO Type to return the MEMO TEXT.   Changing the SQL permissions also fixed and issue I was having with BI Explorer.   

You should never have to change SQL permissions for reports run through the Sage 100 program.  All that should be automatic with permissions coming from the Sage MAS_Reports connection (not the user's Windows credentials).

Thank you,,  We are running SQL on server 2019 along with sage MAS instillations,   Our users are connecting to sage through a serperate server 2019 terminal server using thin clients and rdp with workstation installed on the terminal server.  There are no seperate user permissions set up on SQL.  It was MAS_Reports that I changed the permissions of.  Set up did not give MAS_Reports sufficient permissions.  I found this fix in a Crystal Reports user group that I belong to and it fixed BI and my joined fields.   I appreciate your help.

Thank you,,  We are running SQL on server 2019 along with sage MAS instillations,   Our users are connecting to sage through a serperate server 2019 terminal server using thin clients and rdp with workstation installed on the terminal server.  There are no seperate user permissions set up on SQL.  It was MAS_Reports that I changed the permissions of.  Set up did not give MAS_Reports sufficient permissions.  I found this fix in a Crystal Reports user group that I belong to and it fixed BI and my joined fields.   I appreciate your help.

MAS_Reports should have db_datareader to all MAS_* databases.  Nothing more should be required.