Sage 100

Have a payroll processing client wanting to automate the printing of a custom Crystal Report (no, it can't be done via VI) for 30+ companies.  I'm thinking I would need 30+ hard-coded ODBC drivers.  Does VisualCut have any ability to select the company as well as user/password when printing a report?

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625
------------------------------

Yes.  Looks like you can do that.



------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.


------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625
------------------------------

Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

A couple of thoughts: 
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc: 
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625
------------------------------


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625
------------------------------

Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.


------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625
------------------------------


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

VC requires silent DSN's for automation... there can't be a prompt for company code. 
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

According to Doug's screenshot, you can specify the user and password which means you can use the shorthand method of specifying the company code by separating the user and company with a vertical pipe like this, "user|ABC".

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 11-10-2020 09:48
From: Kevin Moyes
Subject: VIsualCut

VC requires silent DSN's for automation... there can't be a prompt for company code.
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I believe it needs to be a system dsn.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

Original Message:
Sent: 11-10-2020 17:22
From: David Speck II
Subject: VIsualCut

According to Doug's screenshot, you can specify the user and password which means you can use the shorthand method of specifying the company code by separating the user and company with a vertical pipe like this, "user|ABC".

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 11-10-2020 09:48
From: Kevin Moyes
Subject: VIsualCut

VC requires silent DSN's for automation... there can't be a prompt for company code.
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Then in theory (i don't use VC much), you could just set up a system DSN without credentials and company and optionally make it silent and then just use the user|company method.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 11-10-2020 17:32
From: Doug Higgs
Subject: VIsualCut

I believe it needs to be a system dsn.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------


Original Message:
Sent: 11-10-2020 17:22
From: David Speck II
Subject: VIsualCut

According to Doug's screenshot, you can specify the user and password which means you can use the shorthand method of specifying the company code by separating the user and company with a vertical pipe like this, "user|ABC".

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-10-2020 09:48
From: Kevin Moyes
Subject: VIsualCut

VC requires silent DSN's for automation... there can't be a prompt for company code.
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

OK, you made me look... I've never tried the User_ID parameter the way you suggest.  Interesting.  I'll have to test that someday.  Of course the password would be plain text in the batch file (not encrypted like if you enter it through the dialog)..


------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 11-10-2020 17:36
From: David Speck II
Subject: VIsualCut

Then in theory (i don't use VC much), you could just set up a system DSN without credentials and company and optionally make it silent and then just use the user|company method.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 11-10-2020 17:32
From: Doug Higgs
Subject: VIsualCut

I believe it needs to be a system dsn.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-10-2020 17:22
From: David Speck II
Subject: VIsualCut

According to Doug's screenshot, you can specify the user and password which means you can use the shorthand method of specifying the company code by separating the user and company with a vertical pipe like this, "user|ABC".

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-10-2020 09:48
From: Kevin Moyes
Subject: VIsualCut

VC requires silent DSN's for automation... there can't be a prompt for company code.
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

You get to do that once per data source.  The command line functions allow a lot of things to be edited runtime, but not those stored settings (encrypted).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 11-10-2020 17:22
From: David Speck II
Subject: VIsualCut

According to Doug's screenshot, you can specify the user and password which means you can use the shorthand method of specifying the company code by separating the user and company with a vertical pipe like this, "user|ABC".

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 11-10-2020 09:48
From: Kevin Moyes
Subject: VIsualCut

VC requires silent DSN's for automation... there can't be a prompt for company code.
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Thank you to @David Speck II.  I tried running the reports from a command line in a batch file and was able to specify "User_ID" and "Password" on each line.  I used David's trick of putting the company code after the pipe symbol in the User_ID, so it looked like "User_ID:beth|ABC" on one line, then "User_ID:beth|XYZ" on another line and it created 2 exported reports, using 2 different companies, with only 1 ODBC driver.

AWESOME!​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625
------------------------------

Original Message:
Sent: 11-10-2020 18:32
From: Kevin Moyes
Subject: VIsualCut

You get to do that once per data source.  The command line functions allow a lot of things to be edited runtime, but not those stored settings (encrypted).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 11-10-2020 17:22
From: David Speck II
Subject: VIsualCut

According to Doug's screenshot, you can specify the user and password which means you can use the shorthand method of specifying the company code by separating the user and company with a vertical pipe like this, "user|ABC".

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-10-2020 09:48
From: Kevin Moyes
Subject: VIsualCut

VC requires silent DSN's for automation... there can't be a prompt for company code.
For SQL, VC can store username / password (encrypted) but that is it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-10-2020 02:01
From: David Speck II
Subject: VIsualCut

Is there any reason you can't use the default SOTAMAS90 DSN with additional parameters specified in the connection string for the uid, pwd, and company or does VC require system level DSNs?

I have some bat files somewhere that I use for setting up system DSNs for Sage Alerts, it copies the important details from the SOTAMAS90 DSN but has the user and password contained. It uses a space delimited list of company codes to loop through to create each DSN.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 11-09-2020 19:50
From: Wayne Schulz
Subject: VIsualCut

What Kevin said. This type of REG export/import is what I saw one of my very smart IT desktop guys use. He was able to set them up very quickly and IIRC he started by exporting out the key from the Registry of a working workstation then would bring it in to the other desktops.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990


Original Message:
Sent: 11-09-2020 16:25
From: Kevin Moyes
Subject: VIsualCut

I haven't done it myself, but you could probably create a REG file to create multiple DSN's at once... create one, export the reg, edit it to copy multiple times, editing the bits you need to within each copy, then import to the registry.

32-bit DSN's are here:

We use ODBC overrides with Visual Cut all the time, and the one time setup to create DSN's is worth it.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 11-09-2020 16:14
From: Beth Bowers
Subject: VIsualCut

So I'm really glad they have a 30 day trial - I will test it out and see what I can come up with.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:40
From: Doug Higgs
Subject: VIsualCut

A couple of thoughts:
1.  You could create multiple reports and assign the system dsn to each report.  It may be easier to copy reports than to create DSNs.  Per page 81 of the VC doc:  "each report stores connection properties for only one default data source".

2. Per page 83 of the VC doc:
Overriding the Database Specified in the Report or ODBC DSN
For ODBC data sources, you can enter a database name into the login dialog if you wish to override the database specified in the ODBC data source or in the report itself. This is useful for situations where the same database (e.g., MS SQL Server) contains multiple databases each with the same table structure. If the number of such databases is large, creating a dedicated ODBC DSN for each and using the select ODBC DSN functionality may be too tedious. Instead, you can directly type in the database name in the login dialog. To enable database name input into the database field in the login dialog, you need to set the Override_ODBC_DSN_Database entry under the [Options] section in the DataLink_Viewer.ini file to TRUE, like this:
[Options] Override_ODBC_DSN_Database=TRUE
Note that if that option is set to TRUE, the database specified in the ODBC DSN can no longer override the database specified in the report (if the user doesn't type in a Database, the specified Database remains the one used in the report. Note: This functionality is not available in the Crystal 8.5 version of Visual CUT.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary


Original Message:
Sent: 11-09-2020 14:19
From: Beth Bowers
Subject: VIsualCut

SOOOOO that still means I would have to setup 30+ DSNs.  UGH.

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Tennessee Software Solutions
269-445-1625


Original Message:
Sent: 11-09-2020 14:14
From: Kevin Moyes
Subject: VIsualCut

For batch files, use the ODBC_DSN command line parameter to point the report at different silent DSN's that you have configured.

You cannot use SOTAMAS90 for scheduled batches.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON