Sage 100

Custom Crystal Reports issue on 4.5 SQL. I can run a report fine outside of MAS. Add the report to the MAS customer reports menu using Report Manager, manually add the version number in the summary info (because I guess MAS can't properly convert SQL reports), run verify database, everything looks good. When I go to generate the report i get: ""The following error occurred while connecting to the SQL server: The table GL_Account could not be found."" If I open up through report manager and preview it works fine. Is this a rights issue to the SQL tables? Shouldn't it be using the MAS_Reports user when running this? Or can you just not run custom reports through the SQL version of MAS? Any ideas?

In Crystal check Database, Set Datasource Location. It should be: SOTAMAS90. Make sure you have a SOTAMAS90 32-bit System DSN configured for your SQL server. Double check your Summary info. It should be: Converted to version 4.50

thanks Doug - I'll take a look at the datasource and report back.

So here's my scenario: a 4.4 (non-SQL) SOTAMAS90 workstation and 4.5 (SQL) SOTAMAS90 workstation - on the same term server - plus Unified Logon for both installs (Oh Joy!)... anyway, when I change from the SQL datasource to SOTAMAS90 for this report I still get the same error and I think it's looking at 4.4. I found out that the report is not as urgent as I thought, so we may put it on the back burner (or just run it externally) and wait until I get this last company over to SQL. Then I can uninstall the 4.4 workstation, reinstall 4.5 SQL and see if that helps.

I have had an issue with running Crystal reports when using the unified logon. It was all reports though, not just the custom ones. The user code in Sage 100 cannot have a password. Make sure there isn't a Sage 100 password (in user maintenance) associated with the logon. Make sure the associated Windows logon has full control of the mas90 folder structure (as usual). You may test a Windows / Sage 100 user that has Windows administrator privileges to rule out a permissions issue. Also, check your 32 bit ODBC System DSN. Navigate to Windows\SysWow64 and double click odbcad32.exe. click on the System DSN tab, highlight SOTAMAS90 then click Configure. Make sure the ""Server"" field contains the name of your SQL database.

It could be that your 4.4 non SQL and 4.5 SQL installations are both trying to use the 4.4 ODBC data source. You may need to create a new System DSN, and change the data source on your 4.5 custom reports. Alternatively as a test you could create a custom report, create a new connection and use OLEDB instead of ODBC for the SQL db data source. The only issue when using OLEDB is that Alerts and Workflows isn't compatible. You won't be able to schedule Crystal reports in A&W if necessary.

I think that's what is happening. With OLEDB (outside of MAS) the custom report works fine. But once placed inside of MAS it bombs. Right now, they only have this one custom report they are worried about, so I think the work around will be to run it outside of MAS using OLDEDB. Then after I shut down the 4.4 installation and uninstall the workstation I can troubleshoot a little more with the SOTAMAS90 driver. Thanks for your help and suggestions Doug!