Sage 100

I'm going to create a number of Crystal reports that will ultimately be the source for Visual CUT burst and email. I'd like to avoid creating a silent ODBC connection (but could). The goal is to run these scheduled reports external to Sage and perhaps also on the Custom Reports menus. Where can I define the login credentials if I use the SOTAMAS dsn or do I need another?

At the risk of sounding like a broken record....... Pssst, try **Pass Through Queries via an Access DB**.... There is a sample one posted here. https://90minds-com.socialcast.com/messages/39189824?ref=stream Copy and past the PTQ to create new ones (for each table needed), rename the query then modify the select statement in design view to pull from the desired table.....

VC can have override the data source using a batch file / command line parameter, but you need silent DSN's for that (so there is no prompting as the VC report runs). (So, a VC report can be set to SOTAMAS90... but we find maintaining VC reports in the Sage folders to be more of a pain than just making a copy of the .rpt for both purposes).

@JeffSchwenk at the risk of sounding like a complete moron, I'm missing a key step here. I know how to write a PTQ but how does one use that as the source of a Crystal report?

Ah, dipping your toe in the water........ Point the database location to an Access db instead of the sotamas90 odbc

A batch file similar to this might work: ""C:\Program Files (x86)\Visual CUT 11\Visual CUT.exe"" -e ""C:\sage\v54\reports\NoActivity60.rpt"" ""Email_Mode:Whole"" ""Email_From:doug@mcsresults.com"" ""Email_Subject:No Sales Activity Report"" ""Email_To:doug@mcsresults.com"" ""Email_Attach:C:\Company ABC\CrystalReports\NoActivity60.pdf"" ""Email_SMTP_Server:smtpout.secureserver.net"" ""ODBC_DSN:SOTAMAS90

SOTAMAS90 won't work with VC unless you are running VC interactively, or hard code a company code / username / password into the DSN.

The installations I have are on the Sage 100 server so hard coding SOTAMAS90 with the logon credentials doesn't affect the users.

We install only on servers too, but find using named DSN's per company code (leaving SOTAMAS90 alone) to be the most clear. Added benefit: use the DSN in your output path to separate results by company code: