Ok. I've been pondering on this one for a while, and while I'm not sure how to do this yet, here's what I have come up with:
In the connector, create a container that is based on a SQL statement, but put a pass-through variable name in the statement. Here's what I did:
SELECT * FROM @TABLENAME@
Next, add the PTV (in my case @TABLENAME@) as an expression. Then, do the data column selection, and when SMI asks you to operate in the "Default Value Mode" (my words, not theirs), say no, and then you'll be prompted for the Table Name. Use the work table name, and then it will let you choose the columns from the table for your container.
As far as getting the right table name to SMI at run time, I'd start exploring with the Scheduler command, because that will let you send parameters through a command line. I believe you can even create a hyperlink in the Crystal report that will run an EXE, so that you could run the Crystal Report in preview mode, and then click the hyperlink to run the SMI report. The problem I'm running into is determining which table the Crystal Report is based on. Perhaps there's a Crystal Expert who can tell us how to do that.
Here's the command line that SMI generated for my report:
"C:\Program Files (x86)\Sage Software\SMI\BICore.exe" -RU129 -P{PARAM:TableName}{/PARAM:TableName}[_]INSERT_TABLE_HERE[_]TableName -INO_USER -E -J{TENANT_CODE=ABC}{DBTYPE=115}{_privateDBSERVER=C:\Sage Software\MAS 90\Version4.4\MAS90}{_privateDBCATALOG=ABC}{_privateDBUSER=ajclark}{_privateDBPASSWORD=B_L_A_N_K_P_A_S_S_W_O_R_D}{_publicLANGCODE=en}Assuming that your report was the same as mine, the only thing you'd have to change is the INSERT_TABLE_HERE.
I hope that helps. Good luck!
