Sage 100

Sage 100 Advanced v2013- Trying to run a custom report that queries a SQL database from the custom reports menu within Sage. Appararently this is no longer supported in v2013 as I understand from Brian in Tools. He said he knows people that have come up with a workaround but wasn't sure what it is- I was wondering if anyone on here had that workaround?

@KelseyLeerkes can you provide a little more detail regarding the SQL database you are accessing and how you are connecting? If the database is a Sage 100 company database, I'm assuming you are using the SOTAMAS90 DSN and have allowed external access to the database through Sage 100 company maintenance. Also, if you have enabled ODBC Security via System Configuration, you have granted the Sage 100 user access to the necessary table and column objects through Roll Maintenance. If you are accessing the SQL database directly using SQL connector rather than ODBC, has the user's AD account been defined with a login in SQL? Have they been mapped to the database in question and been given db_datareader roll membership for the database? Inquiring minds want to know ;-)

I would think that as long as the MAS Service Account had query rights to the SQL database, it should still work.

I run reports off the custom report menu all the time using Access pass through queries. If the SQL database is a standalone, then having Crystal pull from it shouldn't be an issue. Does it work from standalone Crystal? Do you have the ""Converted to v5.x"" verbiage in the summary field? Does the report name end with ""Custom""?

The reason you could traditionally run Access or SQL reports from Custom Reports is because the report itself did not connect through ODBC - the only ODBC DSN allowed is SOTAMAS90 (unless it's a subreport I believe). If you create the report with the Crystal Reports designer and connect to SQL through OLE DB and can see data that way, presumably it should work under Custom Reports as well.