MAV direct ODBC

[dEraCh2000]

Hi,
I'm trying to use this MAV direct ODBC driver and haven't had much luck with it. So I'v got a cuple o questions. Is it posible to use this driver on an older application, like just including the dictionary support and changing some of the table properties in the dictionary, or do i have to rewrite the whole application and use MAV's browse, forms and everything else. Another question is more of plea then a question, does anyone know of a help or a tutorial on how to use this MAV driver and template.
Kind regards

 

[ShankarJ]

Hi!

Don't you have the Help, Documentation and examples to study?

Help & Documentation - \Clarion6\3rdParty\Docs\MAV Direct ODBC
Examples - \Clarion6\3rdParty\Examples\MAV Direct ODBC

And, it is NOT a driver but a Library to access data using ODBC drivers for databases.

What are you trying to achieve?

Regards

 

[dEraCh2000]

Hi,
I'v seen the documentatio and the examples. And after some reading we have decided not to use it right now, maybe in the future. We want to make apllication independent of a driver. We curently use mssql servers, but there are some potential clients that already have oracle, or are going to purchase oracle database.
We thought we could use this library on our apllications, but since we would need to rewrite most of it, we have decided not to go with this library for now.
Do you know is this library going to go gold, becouse it's been in a beta faze for some time now.
Thanks

 

[ShankarJ]

Hi!

Have you tried the ODBC database driver. I have had good response timings using the default Microsoft SQL Server & Microsoft Oracle+Oracle Client drivers.

Regards

 

[dEraCh2000]

Hi,

Yes we have tried the ODBC database driver. And we are very pleased with it. There is just one thing. When I started the application for the first time it took a while untill we got the results back. It worked fine after that, we starde rhe application from four computers simultaneously, and it worked fine. Do you have an idea why should it work slower for the firs time

KInd regards

 

[ShankarJ]

Hi!

There are certain driver strings for the driver which you can check in the help and modify accordingly. For example ::

VERIFYVIASELECT lets the SQL Driver use an alternative, sometimes faster, method to validate fields when opening a table. By default (VERIFYVIASELECT=FALSE), the SQL Driver uses the SQLColumns function to validate fields. However, some backends (particularly SQL Anywhere) can validate fields faster using a SELECT statement. To verify fields using the SELECT statement, set VERIFYVIASELECT to TRUE.

VERIFYVIASELECT defaults to TRUE for SQL Anywhere backends.

Regards