Hello,
We use a software package where is implemented a communication driver to establish communication with any ODBC database. We need to use this software to connect to DBISAM Database Server and cyclically read out some data. We posess a ODBC library 4.37. When we try to establish the connection, we receive following message: "ODBC driver does not support dynasets".
I wanted just to know, whether maybe a newer version of the ODBC library would solve our issue.

Thank you for your reply in advance.

Best regards

On 3/19/2015 11:37 AM, tomaslipa wrote:
> We use a software package where is implemented a communication driver to establish communication with any ODBC database. We need to use this software to connect to DBISAM Database Server and cyclically read out some data. We posess a ODBC library 4.37. When we try to establish the connection, we receive following message: "ODBC driver does not support dynasets".
> I wanted just to know, whether maybe a newer version of the ODBC library would solve our issue.

Latest version of ODBC driver is 4.40 build 1 but i don't believe it
would fix it for you.

Dynasets are Microsoft specific term (not ODBC in general) and i suspect
it's the way you try to open the connection that's the problem.

We have number of customers using ODBC against our database without any
problems.

Can you be more specific on what app/tool you're using to try to open
the ODBC connection with ? It might be possible to disable dynasets
there instead.

Raul

Hello Raul,

Thank you for your reply. Basically we use the odbc library without any problem in .net.

Concerning the application where we face the problem - it is a SCADA system called zenon which implements a special SQL communication driver, where the only parameters we can define is the connectionstring and send + receive tables. So I have no chance to influence the inner behavior.

I wanted to know mainly whether somebody else has also faced similar problem already and found some solution. As I am also not very familiar with the available settings of the ODBC driver itself, maybe some settings in the driver configuration could solve the problem?

Anyway, I found on google that similar problems are also with odbc drivers from other databases (e.g. MySQL).

Best regards

Tomas

On 3/20/2015 3:56 AM, tomaslipa wrote:
> Concerning the application where we face the problem - it is a SCADA system called zenon which implements a special SQL communication driver, where the only parameters we can define is the connectionstring and send + receive tables. So I have no chance to influence the inner behavior.
> I wanted to know mainly whether somebody else has also faced similar problem already and found some solution. As I am also not very familiar with the available settings of the ODBC driver itself, maybe some settings in the driver configuration could solve the problem?


Tomas,

I would suggest you contact support direct (support@elevatesoft.com.) as
they would be able to give you a best answer on whether there might be a
workaround at driver level and/or of there are anything planned
regarding this.


Raul