For access to a database any application must use a client, OS or database vendor. So if your application runs in 64 bits the client should be 64 bits as well.The solution is to install the Oracle driver for 64 bits.[EDIT]It seems that there is a way for you to distribute an Oracle with your application. See this link http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html . There are some restrictions. The module size reaches 120 Mb and a package must be distributed for each 32/64 bit platform.

O Option= receives a value that identifies the sum of flags that will specify how your ODBC should work, the default value is 0.You can check an old version of the documentation in http://web.archive.org/web/20120120203736/http://dev.mysql.com/doc/refman/5.0/en/connector-odbc-configuration-connection-parameters.html , where:Option=3; is corresponding to FLAG_FIELD_LENGTH (1) FLAG_FOUND_ROWS (2)Information obtained from Stack Overflow https://stackoverflow.com/questions/4407841/whats-the-option-n-in-the-mysql-odbc-connection-string/4407898#4407898 .

The "prefix b" indicates that the object you have at hand is not a text string - and yes, a set of bytes - In Python 3 the two things are fundamentally different, why you always need to know how the text is coded in the bytes so you can turn them into characters. Nowadays it is increasingly common that the text is in the "utf-8" encoding, but some legacy systems and Windows use the "latin-1" encoding - which allows all the characters of the Portuguese language to be in a single byte.The objects of the type "bytes" in Python have a "decode" method - just call it and the result will be the string in text (which is indicated in Python without the prefix 'b'). but beyond the "decode" method, the call str(xml, 'utf-8') would also make this transformation - the error message changes. Since it is not the error of Python saying that there is an invalid utf-8 sequence, the chance is that its XML is yes in utf-8 - only that the ODBC claims an invalid character: the utf-8 supports universal characters - other encodings, such as latin1, no - if there are characters in tongues with Greek, Russian, Hebrew, or even signs of latin-1 punctuation.The remedy would be to force an escaping encoding to pass the data to the driver - only, there is another problem: the function does not accept bytes (the text already encoded). Result: you will have to mutilation the text in Python, replacing all the characters outside the "latin1" with "?", turn it back into text and then make your call. Then, if there is no other error in XML it should work. I would recommend contacting whoever designed the bank you are feeding to accept a universal encoding.To understand more about these processes, stop now everything you're doing and read http://local.joelonsoftware.com/wiki/O_M%C3%ADnimo_Absoluto_Que_Todos_os_Programadores_de_Software_Precisam,_Absolutamente,_Positivamente_de_Saber_Sobre_Unicode_e_Conjuntos_de_Caracteres_(Sem_Desculpas!) To sort your problem and remove the problematic characters from the text:An error equivalent to this is what is now occurring within the ODBC code - if you send a text with Cyrillic characters, for example:In [119]: a = "texto inválido: Ут пауло интерессет темпорибус пер" In [120]: a.encode("latin-1") UnicodeEncodeError Traceback (most recent call last) So - you should: decode your data using utf-8, encode back to latin-1, changing the unknown characters by "?", and decode back to text - there will have data that can be sent to your bank:In [122]: dados Out[122]: b'texto inv\xc3\xa1lido: \xd0\xa3\xd1\x82' In [123]: dados_str = dados.decode("utf-8").encode("latin1", errors="replace").decode("latin1") In [124]: dados_str Out[124]: 'texto inválido: ??' (The "data" variable in this example is equivalent to what you have there at first: a bytes object representing utf-8 coded text, with invalid characters in latin-1). If you continue to have the same error não é possível alternar a codificação, expriemer filter out all non ASCII characters - use "ASCII" instead of "latin-1" in the above code.

No, a bank cannot access the other. What you can do is, build an application that will serve as a bridge between these two servers and use a dataset to feed each other with the information of the view in question.

Try changing the permissions your Windows Service performs, by the way it seems that the service is not allowed to access the ODBC data sources, you can do this through the Windows service manager (press WinKey + R, type services.msc and press enter). In the service list, look for your service, right-click on the second tab (Log On), set another account to perform this service preferably with administrative permissions to make sure the problem is solved if it is permission. After that, just restart the service.

I can install the odbc plugin by following these steps:inside the uncompressed folder of the postgresql odbc:./configure make sudo make install

I guess you don't have the driver ODBC of the Postgres installed on your system.You can do this by using the package manager apt-get:$ sudo apt-get install odbc-postgresql Or manually download the package .deb containing driver For Ubuntu 17.04 (Zesty Zapus):$ wget http://archive.ubuntu.com/ubuntu/pool/universe/p/psqlodbc/odbc-postgresql_09.05.0400-2_amd64.deb And then install the package .deb manually:$ sudo dpkg -i odbc-postgresql_09.05.0400-2_amd64.deb

Based on the comment I did some research and managed to find the solution and I let it respond to those who have the same problem.I told you about the clausula query with(index(nome_do_indice)) more or less like this:SELECT CAMPO FROM TABELA T WITH (INDEX(UM_INDICE)) INNER JOIN OUTRA_TABELA OT WITH (INDEX(OUTRO_INDICE)) ON OT.ID = T.ID Referencia: https://pt.stackoverflow.com/questions/524/como-utilizar-um-%C3%ADndice-espec%C3%ADfico-numa-consulta-em-sql-server

I solved the problem by installing Delphi 10 (Seatle), it worked smoothly. As my needs were to migrate to a more current version to use some FastReport functions that in the example I saw was in Delphi Seatle, so for me it solved.

It seems a question of language definition (language) in the presentation. For example, in the English language the decimal house separator is the point and in Portuguese is the comma. Rate isql behavior with the use of the option -l (locale), defining the English language.At ODBC.ini, check how LOCALE is configured. Also check the LC_NUMERIC configuration on Cent OS.Regarding value 22.40 appear as 23.999..., this usually occurs with expressions of https://pt.wikipedia.org/wiki/Ponto_flutuante ; for example, when the column is declared as float in the database. Depending on how the value is rounded to display, this difference can occur as described in the document https://technet.microsoft.com/en-us/library/ms187912.aspx : The IEEE 754 specification provides four rounding modes: round to nearest, round up, round down, and round to zero. Microsoft SQL Server uses round up. All are accurate to the guaranteed precision but can result in slightly different floating-point values. Because the binary representation of a floating-point number may use one of many legal rounding schemes, it is impossible to reliably quantify a floating-point value.AMPLIATION:(1) In isql it is possible to set locale, using the option -l. Details in https://www.mankier.com/1/isql .(2) For information about Microsoft ODBC driver for CentOS (RHEL clone): https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server (3) UnixODBC installation instructions, to act as driver manager in conjunction with MS ODBC Driver: https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-driver-manager (4) Site definition documentation in PHP: http://php.net/manual/pt_BR/function.setlocale.php

In my case as use Xampp it by default limits the amount of query data, then in the file php.ini in line odbc.defaultlrl = 4092 changed its value to 10mb that corresponds to 10485760 bytes. After testing again with header header("Content-Type: application/pdf" ); the pdf was displayed normal.

ADO.NETA https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ado-net-architecture?WT.mc_id=DOP-MVP-5002397 Say what it is. I'll just summarize it.They are components to give access to data from a given source, probably a database. There are common operations that these providers must provide. ADO.NET treats them abstractly and providers implement them concretely according to the specifics of the data source.The idea is that access to any data source is made transparently. It seems that everything comes from something common, that it is not necessary to understand the specific functioning of the source. This even simplifies the exchange of one source for another.These providers work as if they were the drivers ODBC and OleDB but implement a more suitable way for .NET.If you understand how dbf works, maybe understand what the RDD is ( https://pt.wikipedia.org/wiki/Harbour_(compilador)#Suporte_a_banco_de_dados ). It's basically the same thing.Some https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/data-providers?WT.mc_id=DOP-MVP-5002397 . Anyone can set their own providers. There are specialized companies in this and some market databases provide providers for ADO.NET. https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ado-net-overview?WT.mc_id=DOP-MVP-5002397 .OleDBHow do you see your own drivers https://en.wikipedia.org/wiki/Open_Database_Connectivity and https://en.wikipedia.org/wiki/OLE_DB are ADO providers. Net.The OleDB provider can only access data sources that can communicate with this technology. Microsoft itself is abandoning its support in some of its products.ODBCODBC is a more universal form of access to data sources.Both should be avoided because it is an extra layer, it has an extra processing cost, although the OleDB avoids a little this. More specific providers for a database or another source is always more advantageous. Their implementation is more efficient by knowing how to access the data in the best way. More generic providers, such as the two examples mentioned, are used when there is no more specific provider.The formal settings can be obtained in the links up.

I was able to release the button Parameter in Connection properties changing my SQL command to this:SELECT customer_id FROM `otrs`.`ticket` where (tn = ?) Thus when trying to run the command a window is opened to request the parameter that will be used in QueryI found that tip in that https://social.technet.microsoft.com/Forums/pt-BR/332d3169-2011-47af-8164-2667ae8287dc/consulta-sql-com-clula-excel-de-parmetro?forum=officept

Access Server as rootmysql -u root -p -h localhost And grant the user privilegeGRANT ALL PRIVILEGES ON *.* TO 'reports'@'localhost' IDENTIFIED BY 'sua senha'; FLUSH PRIVILEGES; https://dev.mysql.com/doc/mysql/en/grant.html Best practicesTry not to grant ALL privileges in all banks, root already has this function. Specify what this user may have access to. Example: GRANT INSERT, SELECT, UPDATE ON <seu_banco>.* TO 'reports'@'localhost' IDENTIFIED BY 'sua_senha';

You are not returning the file in the function. .Add a line at the end of the function return(arquivo).When calling the function use dados <- importa.sql()

I did.The solution was to actually download a 64bit drive (my machine architecture) and set up a new connection, more or less how it is done in this https://www.youtube.com/watch?v=z5lH3y_mPCI .

R. Santos to use connection ODBC is necessary to use the ADO components, with it it is possible to perform the connection through the postgreSQL lib odbc. To get started download the postgresql lib odbc https://odbc.postgresql.org/ Then add an ADOConnection component to your project and configure the ConnectionString property by selecting the PostgreSQL OLE Provider provider and filling in the other options available for database connection. Enable ADOConnection and place an ADODataSet, specify the SQL command, and you can use it alone or in conjunction with the dataset provider + clientdataset.

Have you ever tried using the ODBC PostgreSQL driver itself?Product psqlODBC Description psqlODBC is the official PostgreSQL ODBC Driver.Licence Open source Publisher PostgreSQL Global Development GroupYou can download it in: https://www.postgresql.org/download/products/2-drivers-and-interfaces/ The setup is very quiet if you try to make and give some mistake please post so you can try to help yourself.

1) First, take a look at the nolibsqlncli-11.0.so.1790.0 permissions, to see if the apache can write and read.2) It is necessary to see the dependencies of the lib and see if there is no missing one.ldd /opt/microsoft/sqlncli/lib64/libsqlncli-11.0.so.1790.0(3) If you are using CENTos try to disable SELinux.

You could put a confirmation without being in the field using this code but with a condition, that it would only show when the submit had been clicked:if($_POST['submit']) { $sqlConfirma = "SELECT * FROM dba.km WHERE dba.km.id = $id"; mysqli_query((coneccao), $sqlConfirma; echo 'Adicionado com sucesso á base de dados: ' . $inf_km . ', ' . $km . '.'; )But if you prefer this way you can make it by introducing this code into the value or even the placeholder to not have q delete to introduce a new one.Another way would be at the end of the data being saved, generate a GET link to another page (or to the same) with the data entered. If you choose to do this just create a header at the end of php like this:header(Location:'(nome_do_ficheiro)?inf_km=' . '$(inf_km)' . '&amp;km=' . $(km) . '&amp;id=' . $id'); Between kinships q did not know already that they are variable and q vc files would have to create.I hope I helped, MDC