Ok, I tried with new dirver, and happens the same.

I created another DSN for an Access database, and tried, and works as expected. This means, I think, the problem should be something specific to Valentina ODBC driver.

Hello Giuseppe!

Can you provide trace log for VODBC?
This should help us to figure out the problem in the particular case.
Can you try your queries in the Valentina Studio? Whether a difference in result between Valentina Studio and your application?

BTW: you can catch crash in Valentina Studio on executing query with many columns in result. It was fixed in version 6.3.6 (not released yet). So try query with one field in result.

You mean from studio but connected by odbc? I cant, due to architecture error AFAIR (odbc is just available as 32b and server is 64b)

how can I trace vodbc?

About connecting to VODBC via Valentina Studio:
I have tested the VODBC (x32) on Windows8 (x64) and Valentina Studio (x32).
The Valentina Server placed on remote Mac OS machine (both x64).
So I think you should be able to connect via VStudio without problems too, If not - please tell me your environment configuration.

About ODBC Tracing:
https://support.microsoft.com/en-us/kb/274551
I need a trace for your application on executing query.

i will try again the connection from studio amd post exactly the error I got.

About trace, this is what i did and log was not created. I will try again and post results.

And tell me please the text of error message on connecting via VStudio.

Probably you use VStudio x64, and have got an error for architecture mismatch for VStudio and ODBC Manager (that is x32 for x32 Driver).
If you have some time, you can install x32 version of Valentina studio and try your queries. If no - no problem)

Seems like the tool is using AdoDB, for this reason I didn't get any result in log before.

Yes, this is the error I got. With Valentina 32 I can connect and returns rows correctly.

What tool do you use? (If this is not a secret)

AdoDB in PHP or this is .NET ?

Is not a secret of course. Tool is scriptcase.net a PHP IDE/generator

Thanks, we will try it.

I'm talking with them to try to get a "connection driver", but don't know if will be done, or when.

I have figure out that scripcase uses outdated function SQLExtendedFetch

From docs:

In ODBC 3.x, SQLExtendedFetch has been replaced by SQLFetchScroll. ODBC 3.x applications should not call SQLExtendedFetch; instead they should call SQLFetchScroll.

VODBC designed for ODBC 3.5 so not all functions for earlier standards are supported.

Here an request in our bug tracker to implement this function.

So, Giuseppe, this is very important for you to use VODBC via scripcase?

Hi Yuriy,

Well, I would like to use Valentina as database, and, although I don't have confirmation, seems like a driver will not created by them in short term. This means, if I want to use Valentina as database, I'm forced to use ODBC.
About ODBC problem, they answered and told me there is a problem on scriptcase side marked as bug, but don't know exactly what. Maybe is the same you are talking about.

Said that, the ball is on their roof. And is complicated all this situation for me, because we work with RPI too, and not sure if VODBC will work on it. Probably I will have to use only reports, and not DB capabilities sadly

Hello, Giuseppe

As for the Raspberry Pi support - would you like to use VODBC with ScriptCase on RPI, too?
Or what usage scenario?

If we don't use Valentina as database I don't need VODBC working on RPI, because I created a PHP library to communicate easily with REST interface and ask for reports. If Netmake solves the ODBC issues, and we migrate our app from mysql to valentina then, obvioulys, as ODBC would be the only way for us to connect to vdatabase, then vodbc on rpi would be needed too, but it's too soon to speak on this until issues are solved correctly.

Yuriy Velichko wrote:

I have figure out that scripcase uses outdated function SQLExtendedFetch

From docs:

In ODBC 3.x, SQLExtendedFetch has been replaced by SQLFetchScroll. ODBC 3.x applications should not call SQLExtendedFetch; instead they should call SQLFetchScroll.

VODBC designed for ODBC 3.5 so not all functions for earlier standards are supported.

Here an request in our bug tracker to implement this function.

Because this people are almost "ignoring" me, and because there are "full compatibility" with mysql functions, there is something I can do to change "valentina_*" methods in API to "mysql_*" and work with MySQL connection of SC as if a MySQL is? Don't know if I explained. I know it's an stupid question, but well, I don't loose anything for asking.

I know this wasn't work, but I just tried to tell SC to connect to Valentina as a MySQL database and obivously I got an:
Connection Error

Connection attempt failed: SQLSTATE[HY000] [2006] MySQL server has gone away

PDO::__construct(): Error while reading greeting packet. PID=16284