Skip to main content

[archive] .NET access to Vision data via AcuXDBC & ODBC

  • October 22, 2009
  • 2 replies
  • 0 views
D

[Migrated content. Thread originally posted on 20 October 2009]

A customer is running our application, with many Vision files on a Windows Server. They have AcuXDBC. They want to access the Vision data via .NET programs, using ADO. It seems pretty straightforward.

But, the AcuXDBC documentation does not provide the "connection string" parameters. It seems to me we would need to specify:
- Data source name
- user ID
- password (blank)
- server (localhost)
- config file name (acuxdbc.cfg)

Some of these I can guess at: DSN, UID, PWD, Server. But the config filename?

Has anyone here done this? It seems like a very useful construct, and I would like to help the customer do it, and have this approach available to our other customers.

BTW we are in the process of converting our appliction to support an MS-SQL database, using Acu4GL. But that solution won't be right for everyone.

Thanks.

    2 replies

    D

    [Migrated content. Thread originally posted on 20 October 2009]

    A customer is running our application, with many Vision files on a Windows Server. They have AcuXDBC. They want to access the Vision data via .NET programs, using ADO. It seems pretty straightforward.

    But, the AcuXDBC documentation does not provide the "connection string" parameters. It seems to me we would need to specify:
    - Data source name
    - user ID
    - password (blank)
    - server (localhost)
    - config file name (acuxdbc.cfg)

    Some of these I can guess at: DSN, UID, PWD, Server. But the config filename?

    Has anyone here done this? It seems like a very useful construct, and I would like to help the customer do it, and have this approach available to our other customers.

    BTW we are in the process of converting our appliction to support an MS-SQL database, using Acu4GL. But that solution won't be right for everyone.

    Thanks.
    This was resolved (by Acucorp tech support). In case others are interested:

    Since the DNS has already been set up, it specifies the user ID, password, configuration file, etc, the ADO connection string can simply specify the DSN.
    The following connection string works:

    DSN=lsdata;UID=username;PWD=password;Server=localhost

    Per Acucorp, the following should also work (but I have not tested):

    DSN=lsdata
    D

    [Migrated content. Thread originally posted on 20 October 2009]

    A customer is running our application, with many Vision files on a Windows Server. They have AcuXDBC. They want to access the Vision data via .NET programs, using ADO. It seems pretty straightforward.

    But, the AcuXDBC documentation does not provide the "connection string" parameters. It seems to me we would need to specify:
    - Data source name
    - user ID
    - password (blank)
    - server (localhost)
    - config file name (acuxdbc.cfg)

    Some of these I can guess at: DSN, UID, PWD, Server. But the config filename?

    Has anyone here done this? It seems like a very useful construct, and I would like to help the customer do it, and have this approach available to our other customers.

    BTW we are in the process of converting our appliction to support an MS-SQL database, using Acu4GL. But that solution won't be right for everyone.

    Thanks.
    This was resolved (by Acucorp tech support). In case others are interested:

    Since the DNS has already been set up, it specifies the user ID, password, configuration file, etc, the ADO connection string can simply specify the DSN.
    The following connection string works:

    DSN=lsdata;UID=username;PWD=password;Server=localhost

    Per Acucorp, the following should also work (but I have not tested):

    DSN=lsdata

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement