Skip to main content

[archive] AcuSQL

  • November 15, 2007
  • 5 replies
  • 0 views

[Migrated content. Thread originally posted on 13 November 2007]

We are trying to see if AcuSQL 7.2 will work for us. I can't seem to find a sample program that uses a Microsoft SQL Server. Am I missing it somewhere? I see ones for Access, DB2 and Oracle only. We're currently using AcuBench 7.2. Are there any out there? Thanks!

5 replies

[Migrated content. Thread originally posted on 13 November 2007]

We are trying to see if AcuSQL 7.2 will work for us. I can't seem to find a sample program that uses a Microsoft SQL Server. Am I missing it somewhere? I see ones for Access, DB2 and Oracle only. We're currently using AcuBench 7.2. Are there any out there? Thanks!
Many of the AcuSQL sample program are very similar in nature. To establish a connection to the database you'll have a COBOL statement similar to this:

EXEC SQL CONNECT TO :dsn-name as C1
USER :userid USING :passwd
END-EXEC
It is the dsn-name (A MSSQL data source name) pointing to your MSSQL database using the permision that userid (and appropriate password) have to connect to that database. You should be able to use the Access sample programs once you've set up the MSSQL database an client side data source name.

[Migrated content. Thread originally posted on 13 November 2007]

We are trying to see if AcuSQL 7.2 will work for us. I can't seem to find a sample program that uses a Microsoft SQL Server. Am I missing it somewhere? I see ones for Access, DB2 and Oracle only. We're currently using AcuBench 7.2. Are there any out there? Thanks!
Many of the AcuSQL sample program are very similar in nature. To establish a connection to the database you'll have a COBOL statement similar to this:

EXEC SQL CONNECT TO :dsn-name as C1
USER :userid USING :passwd
END-EXEC
It is the dsn-name (A MSSQL data source name) pointing to your MSSQL database using the permision that userid (and appropriate password) have to connect to that database. You should be able to use the Access sample programs once you've set up the MSSQL database an client side data source name.

[Migrated content. Thread originally posted on 13 November 2007]

We are trying to see if AcuSQL 7.2 will work for us. I can't seem to find a sample program that uses a Microsoft SQL Server. Am I missing it somewhere? I see ones for Access, DB2 and Oracle only. We're currently using AcuBench 7.2. Are there any out there? Thanks!
I was able to get this going. Thanks!

Another question though: We'll have multiple tables in the same database and would like to point them depending on what client's data we're accessing. Is there any way to use a variable for the table name in the SQL statements? I'd hate to have to set up a different database for each client and reconnect to it on the fly. Any alternatives.

[Migrated content. Thread originally posted on 13 November 2007]

We are trying to see if AcuSQL 7.2 will work for us. I can't seem to find a sample program that uses a Microsoft SQL Server. Am I missing it somewhere? I see ones for Access, DB2 and Oracle only. We're currently using AcuBench 7.2. Are there any out there? Thanks!
I was able to get this going. Thanks!

Another question though: We'll have multiple tables in the same database and would like to point them depending on what client's data we're accessing. Is there any way to use a variable for the table name in the SQL statements? I'd hate to have to set up a different database for each client and reconnect to it on the fly. Any alternatives.

[Migrated content. Thread originally posted on 13 November 2007]

We are trying to see if AcuSQL 7.2 will work for us. I can't seem to find a sample program that uses a Microsoft SQL Server. Am I missing it somewhere? I see ones for Access, DB2 and Oracle only. We're currently using AcuBench 7.2. Are there any out there? Thanks!
I was able to get this going. Thanks!

Another question though: We'll have multiple tables in the same database and would like to point them depending on what client's data we're accessing. Is there any way to use a variable for the table name in the SQL statements? I'd hate to have to set up a different database for each client and reconnect to it on the fly. Any alternatives.