Hello,
we have a web application that imports client files into a sybase 12 database.
We are migrating the database to version 17, but the application can no longer read client file.
What changed from 12 to 17 version?
Thanks,
Simona
At the end we decided to call directly the read_file_client() from whe web application, and so it works.
But we don't understand what is different in the version17.
Thank you very much for the support
We also tried on the web server, it is the same. The result is the same if we run the stored procedure from web server, from DBISQL on the same machine as the web server, from DBISQL on the databases machine, from DBISQL on a client pc.
The 2 databases are on the same server, the v12 runs with dbsrv12 and the v17 runs with dbsrv17. The database v17's structure is the same of v12, we migrated it.
The ODBC drivers on the web server are differnt in version SQLAnywhere 12 and SQLAnywher...
The read_client_file() function is called from a stored procedure. If we run the stored procedure from ISQL appears a pop-up with the same message, but if we choose 'allow' it works.
But we have only migrated the database from the v12 to v17.
The read_file_client() is called from a stored procedure. We don't remember using the SA_REGISTER_VALIDATE_FILE_TRANSFER_CALLBACK ODBC extended attribute. How can I control if we used the SA_REGISTER_VALIDATE_FILE_TRANSFER_CALLBACK on the v12?
It's q...
