SQL Views are company specific.  So (for example) if you added a view to your test company, and try to run the report from a Live company, that won't work until you add the view to that Live company code.

I am aware they are company specific.  I developed the views in their production company and is the company I am logged into when experiencing the issues.  I have created other reports for the same company using views and did not have this issue.  

What tables are you using in your new view that is not functioning? 

If your View references an external database (or linked server), at least read permission needs to be given to MAS_Reports.

Also, check the data source... don't use a DSN for reports run from within Sage 100.

Sorry did not get response sooner.  I thought responding to email posted automatically.

I am using IM_ItemCost, IM_ItemWarehouse, CI_Item and Scanforce added tables, MB_ItemBin and MB_LotSerial

Should I create a unique DSN.  I have used both the SQL server name for DSN and a SQL Server DSN named MAS_DCI, linked directly to database.  Neither work.

Should I create a unique DSN.  I have used both the SQL server name for DSN and a SQL Server DSN named MAS_DCI, linked directly to database.  Neither work.

Don't use a DSN.  That hard codes the company database, and requires all workstations have that DSN to run the report. 

Using trusted authentication also has been known to cause us problems with custom reports / forms.  Take a functional custom report, do a Verify Database, then use that connection to Set Datasource Location in the new report.

I checked and am using the same, the SQL server name.  MAS_REPORTS user, production database is selected.  

If you use SSMS with MAS_Reports credentials, does the view run?

Yes sir.  The report can be run outside of Sage using the MAS_Reports user and password.

I'm out of ideas then. 

What is the exact error (with screen shot)?