odbc

问题 I have an MS-Access database, which I am connecting to in Java using the JDBC (I think the JDBC-ODBC bridge). My access database has some values which are in hebrew. When I try to read these values using String str = rs.getString(1) (rs is a RowSet), the string I get is just a string of question marks. I have other strings in hebrew, which I set in the Java code using string literals, and they work fine. So I'm pretty sure the problem is specifically with reading from the db. I'm very new to

问题 So, I'm trying to use ODBC to execute a stored procedure in an SQL database, but it returns the error odbc_fetch_array() [function.odbc-fetch-array]: SQL error: [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index, SQL state S1002 in SQLGetData Here's the PHP part, pretty standard ... $id = 240 $user = "user"; $password = "password"; $server = "server"; $database = "database"; $con = odbc_connect("SERVER=$server; DRIVER=SQL Server; DATABASE=$database", $user, $password); $res = odbc

问题 One of our employees created a Microsoft Access Database and has built a Joomla! module around it. It is currently running on a WAMP server, with an ODBC connection to the accdb file. How can I create an ODBC connection on Ubuntu for the Access database? At this point, I'm open to having the DB live locally on my Ubuntu server, or on an SMB share somewhere. Moving it from Access to MySql has already been proposed. It may come down to that, but I'm really being pressured to find another option

问题 I'm having problem with ODBC and an application written with Visual Basic 6 (so it's 32-bit). It seems that the ODBC library of VB6 is not compatible with the 64-bit ODBC of Windows 7. The error code returned is -2147220992 and it's rambling about incompatible architectures. Can I install a 32-bit version of ODBC? Or any other alternatives? 回答1: use the 32-bit odbc manager to add your DSN: C:\Windows\SysWOW64\odbcad32.exe that should be able to see the 32-bit odbc driver. 回答2: You need to use

问题 I have a Crystal report where the data source has originally been set to use ODBC connections. Now I want to modify the data source to instead use OLE DB instead of using ODBC. How do I replace the data source connection without breaking the database fields which I have originally set up for my report? If I try to delete the original data source, the fields which I have already set up are also deleted. Is there a way to map the report to use OLE DB instead of the ODBC connection? Thanks. 回答1:

问题 I have seen both Option=3 and Option=4 in connection string samples for MySQL ODBC but no explanation or documentation. What do those numbers mean? 回答1: The Option= value is the sum of the numeric values for various flags that specify how Connector/ODBC should work. Its default value is 0. From an older version of the Connector/ODBC documentation at web.archive.org: Option=3; corresponded to FLAG_FIELD_LENGTH (1) + FLAG_FOUND_ROWS (2) Option=4; was FLAG_DEBUG According to the current list of

问题 We are doing some performance tests on our website and we are getting the following error a lot: *** 'C:\inetpub\foo.plex' log message at: 2008/10/07 13:19:58 DBD::ODBC::st execute failed: [Microsoft][SQL Native Client]String data, right truncation (SQL-22001) at C:\inetpub\foo.plex line 25. Line 25 is the following: SELECT DISTINCT top 20 ZIP_CODE, CITY, STATE FROM Zipcodes WHERE (ZIP_CODE like ?) OR (CITY like ?) ORDER BY ZIP_CODE And lastly, this is perl code. Any ideas? EDIT : the issue

问题 On choosing Data Source under ODBC (64-Bit) on Windows, i get two available options of MySQL Database: MySQL ODBC 5.3 ANSI Driver MySQL ODBC 5.3 Unicode Driver What are the difference between these two? 回答1: Firstly I should say that I don't use MySQL but I do know about ODBC Drivers. In ODBC there are different APIs for unicode and ansi. The ansi APIs end in A and the unicode APIs end in W (e.g., SQLPrepareA and SQLPrepareW). The ansi APIs accept bytes/octets for character strings and hence

问题 On choosing Data Source under ODBC (64-Bit) on Windows, i get two available options of MySQL Database: MySQL ODBC 5.3 ANSI Driver MySQL ODBC 5.3 Unicode Driver What are the difference between these two? 回答1: Firstly I should say that I don't use MySQL but I do know about ODBC Drivers. In ODBC there are different APIs for unicode and ansi. The ansi APIs end in A and the unicode APIs end in W (e.g., SQLPrepareA and SQLPrepareW). The ansi APIs accept bytes/octets for character strings and hence

问题 I am getting this error when I try to insert record in db. Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified my connection is : Application("Db_ConnectionString")= "DSN=dsnname;UID=xxx;PWD=xxx;" please help me asap. thanks in advance. 回答1: thanks for your answers. I myself fixed the error. Assigned wrong dsn name in my code. I changed it and now its working fine 回答2: I got this error on