Rdb ODBC 3.3.2.4 Driver

Hi,
I've found the release notes for the Rdb ODBC 3.3.2.4 driver, but I can't find the download link. The only Rdb ODBC driver I can find is 3.3.2.0 which was last updated in June of 2010. Can anyone point me towards the 3.3.2.4 driver?
Thanks,
Sean

Hi, the latest driver is released as a patch (19822870). The direct link is: https://support.oracle.com:443/epmos/faces/PatchSearchResults?searchdata=%3Ccontext+type%3D%22BASIC%22+search%3D%22%26lt…
It requires an oracle support account to access it.
Cheers,
Cameron

Similar Messages

Rdb ODBC

I am very new to working with Oracle systems from a developer standpoint. I am currently trying to connect (using VB.NET) to a RDB database. The items I've installed from the universal installer are:
Oracle9i Client 9.1.0.1.0
Oracle Data Provider for .NET 9.2.0.4.01
Oracle Provider for OLE DB 9.2.0.4.0
Oracle ODBC Driver 9.2.0.5.4
Oracle Objects for OLE 9.2.0.4.8
I have MSAccess working with the RDB ODBC Driver, but cannot seem to get connected in any other way. I am working on a contract for the state, and all they have provided me with is information to use in the RDB configuration. Is there more information that I need to request to make a direct connection through the Oracle Data Provider for .NET? I understand the connection strings, and am trying to 'find' the Data Source required. I have an attach statement/server/class for the RDB connection but can't seem to decipher the Data Source from that.
After about 6 hours of trying, I finally broke down and tried to get the RDB ODBC connection working in the application instead of fighting the .NET drivers. When I try to create a connection to the Microsoft OLEDB Provider for ODBC I can specify the Machine DSN that works in MS Access. When I 'test connection' the wizard responds that it works. But when I try to Save the Connection String I get this error message:
The .Net Data OLE DB Provider(System.Data.OleDb) does not support the MSDASQL Provider, Microsoft OLE DB Provider for ODBC Drivers.
I'm hoping that:
1. Someone can tell me what I need to do to get a connection string to work for the RDB ODBC driver in VB.NET
2. Find out if there is a way to decipher the data source from a RDB attach statement knowing the server name.
Thanks in advance, your time and help is appreciated.
Todd Frahm

First, the Oracle database and the RDB database (owned by Oracle Corp), are completely separate animals. Unfortunately for you, the folks around here, myself included, are vastly more familiar with the Oracle database than with RDB, so we may not be much help.
If you have access to Metalink, I'd start by looking at Document 225779.1 "Oracle ODBC for RDB FAQ".
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com/askDDBC

Where is Rdb ODBC v2.latest ?

I've searched online for the latest Rdb v2.x ODBC, and all I can
find is the download for the v3.x ODBC. I've tried the v3 ODBC,
but my application and it don't get along. I'm currently running
v2.10.13, and would like to get the latest (I've seen a
reference to v2.10.18).
Thanks.
Gary

Thanks for the links.
Some of them I had already tried.
I downloaded /installed the MDAC to the latest, 2.8.
There was no change.
My Oracle RDB ODBC driver was relatively recent but I decided to refresh it anyway. TaDa!
I believe IIS and Oracle RDB SQL/Services do not quite agree about client connections. I still see executors being created on the server when I think existing one's should be free to do the execution,... but I am not completely hanging my web server, and web clients are getting some response (data).
I'll take it. I can tune the lifetime of executors.

ORACLE RDB ODBC

Hi All,
I have a web application built using ASP.Net and communicates with a Web services which uses oracle rdb odbc driver to connect to RDB server, but after a while I started getting this error when executing simple statements like insert or update against the database:
Data : System.Collections.ListDictionaryInternal
Source : SQRDB3.DLL
Message : ERROR [08S01] [Oracle][ODBC][Rdb] send() Ret -1 Err#10038 WSAENOTSOCK File descriptor not a socket
InnerException :
Error: System.Data.Odbc.OdbcException: ERROR [08S01] [Oracle][ODBC][Rdb] send() Ret -1 Err#10038 WSAENOTSOCK File descriptor not a socket
at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader, Object[] methodArguments, SQL_API odbcApiMethod)
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader)
at System.Data.Odbc.OdbcCommand.ExecuteNonQuery()
Please Help Me,
Thanks in advance..

Hello,
Rdb ODBC questions are easily overseen in this forum. In general we recommend to post Rdb related questions in the communities at:
https://communities.oracle.com/portal/server.pt/community/rdb_product_family_on_openvms
There you are getting much faster a response because that site is watched by Oracle Rdb Engineering and Support.
In your special case: does this happen frequently, is that still a problem for you? In that case enable client logging and if the client log file contains a message like SQLSRV-E-IDLEUSERTIMEOUT then you might have just a too small idle user timeout for your SQL/Services service that you use for your ODBC connection. You can change that value easily:
SQLSRV> ALTER SERVICE <your service> IDLE_USER_TIMEOUT <new value in seconds>;
If that does not help then you can always log a Service Request with Oracle Support.
Regards
Wolfgang
Oracle Rdb Support

RDB ODBC V3.0.2.0 : Sqlstate 01004 upon DB-Connect: why ?

Hello !
I Tried to upgrade my RDB-ODBC Driver from V 2.10.17.00 to V 3.0.2.0
Prior to the installation I had working ODBC-Connections to 4 VMS Nodes, all of them running VMS V7.0, Oracle RDB V7.0-5. Two of these Nodes have SQLServices V7.0, two have SQLServices
V7.1. The PC-Client is an NT4.0 Box with SP6a.
After the installation of the V3 ODBC-Driver, I can connect to the nodes running SQLServices V7.0 but not to not to the nodes with SQLSRV 7.1. Upon __connecting__ to the latter nodes with odbctest V2.5.3.1.0, I get the following errormessages:
"SQLSTATE: 01004
Native Error Code:0
Driver Message:[Microsoft][ODBC Driver manager] Die Daten wurden abgeschnitten) (=Data was truncated)"
and subsequently:
"SQLSTATE: 01004
Native Error Code:0
Driver Message:[Oracle][ODBC]String data, right truncated"
After these messages, the Odbc-Test programme does NOT allow to execute any queries, since
obviously the Programme did not properly connect to the server Database.
When I Connect to the same Database with the old V2 Driver, the connect works fine.
Could somebody please check out where this error comes from ? suggestions are welcome !
I do not know wether this problem is due to an ODBC-Driver Error of some sort,
or rather an Sql-Services error, a dll mismatch or dodgy Registry entries.
Thanks in advance !
Rudi

First, the Oracle database and the RDB database (owned by Oracle Corp), are completely separate animals. Unfortunately for you, the folks around here, myself included, are vastly more familiar with the Oracle database than with RDB, so we may not be much help.
If you have access to Metalink, I'd start by looking at Document 225779.1 "Oracle ODBC for RDB FAQ".
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com/askDDBC

[[DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Column name or number of supplied values does not match table definition.]

Hii ..
need help on this ..
This what I am doing ..
I am using a DATAEXPORT function to export level0 data from my essbase 11.1.2.2 to Microsoft SQL 2008 tables.
So what I did first I exported the level0 data to a flat file using DATAEXPORT and the created the SQL columns by the same in that order only in my SQL table.
When I run it fails with this error:
ODBC Layer Error: [21S01] ==> [[DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Column name or number of supplied values does not match table definition.]
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1021014)
ODBC Layer Error: Native Error code [213]
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Error(1012085)
Unable to export data to SQL table [dataexp]. Check the Essbase server log and the system console to determine the cause of the problem.
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1021002)
SQL Connection is Freed
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Warning(1080014)
Transaction [ 0x1c50001( 0x51ee7d66.0x80342 ) ] aborted due to status [1012085].
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1012579)
Total Calc Elapsed Time for [test.csc] : [1.44] seconds
=============================================================
I did a simple test on my Sample.basic application then ..
loaded the calc data to it and then used the below script to export to a flat file
//ESS_LOCALE English_UnitedStates.Latin1@Binary
SET DATAEXPORTOPTIONS
                DataExportLevel "Level0";
                DataExportOverwriteFile ON;
                DataExportColFormat OFF;
                DataExportDimHeader OFF;
FIX(
            "Jan",
            "Sales",
            "Actual"
/*DATAEXPORT "File" "," "/home/hypadmin/samtest.txt";*/
DATAEXPORT "DSN" "Abhitest" "sample" "sa" "welcome1";
ENDFIX
out put as below:
"Sales"
"100-30","California"
"Jan","Actual",145
Now In sql I created only 3 columns with name Jan/Sales/Actual and when I run this script again with comments removed .. I get the same error as what I have got in my first test case with other application ..
but when I create the columns with same name as what its in export
Sales/100-30/Califirnia/Jan/Actual
It created the new rows successfully ..
So with this I think the error which I am getting with my other application might be because of the same column issue .. but then I have created all the columns by looking at the export file only as I did in sample ..
Any idea would be helpful ..
Thanks
Abhishek
I

First make sure you add
DataExportRelationalFile ON;
to your set commands it is missing
I alwats like to also add
DataExportColHeader dimensionName;
so I am sure what dimension is getting put into the columns.
Then count the number of dimensions in your outline (exclude attribute dimensions). You need at least that many columns in your table -1 + the number of members you will be returning as columns in the export
Taking your example Sample basic has 5 dimensions
Measures
Years
Scenario
Product
Market
Since you did not specify a dataexportcolheader it took the dense dimension Scenario as the columns. Your fix statement is limiting that to one member. Doing the math
5 -1 + 1 = 5 columns in your table which is what you found works. Suppose you fixed on bothe Actual and budget in scenario then you would need 6 columns 5 -1 +2

[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
Thanks

Hi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike

Need RDB ODBC driver version 2.10.17

I need this older release for Visual Foxpro 9.0 ODBC connections. This version is no longer available for download on your website. Or, alternatively, I need a way to transfer this working release from one PC to another. Version 3 works with some apps but not VFP 9.

here you should find what you are looking for:
http://www.oracle.com/technetwork/developer-tools/visual-studio/downloads/index.html

OpenOffice and Rdb ODBC

I have the Oracle Rdb Driver v3.0.2 installed on a Windows client and a User DSN connection established in the ODBC Data Source Administrator control panel applet. I can query successfully with clients like MSQuery, Excel (with the SQLREQUEST() array function), and my terminal emulator (SmarTerm 9) which comes with built-in SQL functions. However, with OpenOffice 1.0 and 1.0.1, which comes with a query builder similar to MSQuery, I cannot get a proper list of available tables once the connection is made to the remote database.
There are 3 log files on the client which offer some clues, but it is not clear (to me) whether the Oracle driver is faulty, or it's OpenOffice that's the problem. Buried in two of the logs are SELECT statements which appear to pass invalid SQL syntax to the database, causing it to return no table names.
The first log is generated by the ODBC Data Source Administrator itself when Tracing is enabled. It's name is SQL.LOG by default. The other two logs are CLIENT.LOG and RDBODBC.LOG, generated by SQL/Services and the driver, respectively. The first, SQL.LOG, contains the following lines at the point where OpenOffice is requesting the list of tables:
scalc fff01057-fff017d7     ENTER SQLTablesW
          HSTMT 0314028C
          WCHAR * 0x00000000
          SWORD 0
          WCHAR * 0x00000000
          SWORD 0
          WCHAR * 0x0323FFE8 [      -3] "%"
          SWORD -3
          WCHAR * 0x0314067C [      -3] "VIEW,TA"
          SWORD -3
scalc fff01057-fff017d7     EXIT SQLTablesW with return code 0 (SQL_SUCCESS)
          HSTMT 0314028C
          WCHAR * 0x00000000
          SWORD 0
          WCHAR * 0x00000000
          SWORD 0
          WCHAR * 0x0323FFE8 [      -3] "%"
          SWORD -3
          WCHAR * 0x0314067C [      -3] "VIEW,TA"
          SWORD -3
The second log, produced by SQL/Services on the client, shows that the '%' wildcard has been changed to '% '. Here's the SQLTablesW call in that log:
ROUTINE LEVEL LOG at 11:19:43 on 07-Sep-2002
----SQLSRV_PREPARE
--------SQL STATEMENT
------------len: 233, value: SELECT '',rdb$flags,rdb$relation_name,rdb$system_fl
------------ag,'' FROM rdb$relations WHERE rdb$system_flag=0 AND rdb$relation_na
------------me LIKE '% ' ESCAPE '&' ORDER BY rdb$sy
------------stem_flag DESC,rdb$flags ASC,rdb$relation_name
PROTOCOL LEVEL LOG CLIENT: write (logonly) at 11:19:43 on 07-Sep-2002
----PACKET LENGTH: 245
PROTOCOL LEVEL LOG CLIENT: write (logonly) at 11:19:43 on 07-Sep-2002
----PACKET ID: 3, PACKET SEQUENCE: 0
--------SQLSRV_PREPARE
------------SQL STATEMENT
----------------SQLSRV_COUNTED_BYTES, len: 233
--------------------len: 233, value: SELECT '',rdb$flags,rdb$relation_name,rdb$s
--------------------ystem_flag,'' FROM rdb$relations WHERE rdb$system_flag=0 AND
-------------------- rdb$relation_name LIKE '% ' ES
--------------------CAPE '&' ORDER BY rdb$system_flag DESC,rdb$flags ASC,rdb$rel
--------------------ation_name
--------END OF MESSAGE
Finally, the RDBODBC.LOG driver log shows a similar change to the LIKE clause of the SELECT statement:
.0X00700138: SELECT '',rdb$flags,rdb$relation_name,rdb$system_flag,'' F
.ROM rdb$relations WHERE rdb$system_flag=0 AND rdb$relation_name LIKE '
.% ' ESCAPE '&' ORDER BY rdb$system_flag D
.ESC,rdb$flags ASC,rdb$relation_name
I'm no ODBC developer, but perhaps someone can suggest why the spaces are being added?
Thanks,
Alder

Unfortunately RDB and Oracle are two completely different animals, so I'm really out of my element.
My wild, uninformed, shot-in-the-dark guess is that this has something to do with Unicode. When Unicode data is encoded as UCS-2 (Windows default encoding), ASCII characters are stored in two bytes, [ACSII value][00]. The ODBC Driver Manager is supposed to know whether a driver supports Unicode and to translate Unicode data passed through it to ASCII if that's what the driver needs. Perhaps the translation isn't happening properly here...
If you look at the SQL.log file for the applications that work, I'm going to guess that you see the function SQLTablesA (ASCII version) being called, rather than SQLTablesW.
Justin

RDB Odbc drivers and Visual Express 2005 !!!

hi,
i'm having troubles with MS Web Developper Express 2005 and RDB database ODBC driver 3102.
When i try to declare a link to a dsn previously delared in ODBC manager (win xp sp2), i click the "test connection" then it's succesfull, but when i want to browse thru the tables within the rdb db, i receive the error : [HYC00][Oracle][ODBC] Optional feature not implemented...
I tried to use the same dsn with MS Access and it works correctly.
Any idea ?
Thanks

hi,
i'm having troubles with MS Web Developper Express 2005 and RDB database ODBC driver 3102.
When i try to declare a link to a dsn previously delared in ODBC manager (win xp sp2), i click the "test connection" then it's succesfull, but when i want to browse thru the tables within the rdb db, i receive the error : [HYC00][Oracle][ODBC] Optional feature not implemented...
I tried to use the same dsn with MS Access and it works correctly.
Any idea ?
Thanks

Heap Corruption in ODBC 10.2.0.3 driver

Howdy,
I'm writing a piece of middleware that takes incoming requests and translates them connects to one of several back-ends: MSSQL, DB2, and Oracle. I've had a tremendous amount of diffficulty with the Oracle ODBC drivers.
I am using the 10g instant client, but have had the same problem with the full client install. (I have installed Oracle pieces many, many times now.)
I am developing in C++ using VC2K5 talking straight ODBC. The current problem is that calling SQLDriverConnect in a debug build always brings up a dialog box that says:
Windows has triggered a breakpoint in OracleBindProblem.exe.
This may be due to a corruption of the heap, and indicates a bug in OracleBindProblem.exe or any of the DLLs it has loaded.
The output window may have more diagnostic information
Boundschecker reports that this comes from a free that is not at the top of the alloc'd block coming from OraOCIEI10.dll (which VC debug runtime sees as a heap corruption, since the block headers aren't correct in the free).
Is anyone else having this problem? Is there a fix? The app seems to continue correctly after this, but this is concerning for 2 reasons:
1) Every time I connect, my debug run stops, which means I can't automate anything in debug, makes debugging really tough, and also makes handing the debug off to QA impossible. Since I use ASSERT's all over, being able to run the debug in test is pretty important.
2) It's a HEAP CORRUPTION. Even if this is intentional ("clever" pointer math), it's pretty dangerous. And since it doesn't happen with previous drivers, I suspect it is not intentional.
I've narrowed the problem down through a very small test app. I'd be happy to post the code if anyone is interested.
I had to move to 10.2.0.3 because of a bug with bound parameters and keyset cursors in 10.1. I had to move to 10.1 because of an issue regarding DSN-less connections.
Which brings me to another question I'd really appreciate insight on. Are the Oracle ODBC drivers a lost cause? I truly have never had a more negative initial experience with a piece of software as I have had over the last 2 weeks with these Oracle drivers. (Keep in mind that the MSSQL & DB2 stuff is working fine.) I have spent 100% of my time for two weeks trying to work around defects. Does Oracle not care, or are they incompetent when it comes to ODBC, or am I just having a run of bad luck? I'm really not trying to flame; I just really would appreciate insight. I'm new to Oracle, so I don't want to spend the next month finding out that I have to go with a 3rd party. (BTW, I tested a very famous third-party driver, and everything worked fine; the problem is that I'm sure my contracting employer will not pay the licensing fees unless there simply is no other alternative.)
Unfortunately, since I'm just a developer trying to allow folks to use Oracle when they purchase our software (which is very popular in Europe), I don't have a support contract, which I understand is required to see the list of known defects. Have I misunderstood this? Is there a way to get current known defect info outside of metalink?
Thanks,
Ken

Update for future reference:
Finally got a metalink account and ran with the latest instantclient patch. This seemed to stop the heap corruption problem.

Hadoop ODBC linked server error: Specified driver could not be loaded due to system error 182

Hi,
I am trying to connect to a Hadoop server through a linked server in SQL Server. I downloaded and installed the Microsoft Hive ODBC driver - HiveODBC64.msi. But while I am trying to create the Linked server using this ODBC driver I am getting below error.
" Specified driver could not be loaded due to system error 182 (Microsoft Hive ODBC driver, D:\....\HiveODBC64.dll). (Microsoft SQL Server, Error: 7303)"
When I tested it locally and in another server, it is working properly. I am getting this error only in this server. looks like a dll error. But cannot identify where/what is the error. Could someone help me fix this issue.
Server info:
OS Name: Microsoft Windows Server 2008 R2 Enterprise Version 6.1.7601 Service Pack 1 Build 7601
SQL SERVER: Microsoft SQL Server 2008 R2(SP1)

Hi LinkedServer,
According to your description, you want to create linked server to connect to a Hadoop server in SQL Server, and you have created it successfully in the test server, the problem is that you get the issue in the production environment, right?
Based on the error message, as you said it seems that the issue is related to the HiveOBDC64.dll assembly. Since you have done it on the test server, you can copy and replace HiveODBC64.dll to production server in the C:\Program Files\Microsoft Hive ODBC
Driver\lib directory. Or you can reinstall the Microsoft Hive ODBC driver. Here is a blog which describe how to create a SQL Server Linked Server to HDInsight HIVE using Microsoft Hive ODBC Driver step by step, please refer to the link below to double check
if your steps are correct.
http://blogs.msdn.com/b/igorpag/archive/2013/11/12/how-to-create-a-sql-server-linked-server-to-hdinsight-hive-using-microsoft-hive-odbc-driver.aspx
Regards,
Charlie Liao
TechNet Community Support

ODBC error using ORACLE MERANT DRIVER

Hi,
OS-windows 7 64bit
Oracle Database 11g-64 bit
Oracle Merant Driver 32 is installed(SysWOW64) when install DAC. so can't connect using Oracle merant driver 32 with Oracle Database 64bit. it's showing the below error.
How can connect Oracle Merant Driver 32 bit with Oracle database 64 bit. kindly check how to resolve this.
Error:
Specified driver could not be loaded due to system error 193:
\DataDirectODBC\seor820.dll)

You may also try Oracle's odbc drivers available free from OTN
see also http://support.microsoft.com/support/kb/articles/Q159/6/57.asp
Oracle procedure is:
CREATE OR REPLACE PROCEDURE test(
a OUT integer,
b out integer)
AS
BEGIN
a:=100;
b:=200;
END;
I have verified output values with oracle odbc 8.1.6 and OLEDB 8.1.6
Turloch

2003 R2 ODBC Administrator not showing mapped drives

When i try to create a new ODBC, and then try to select the database file, the ODBC Administrator not show the mapped network drives.
Can Anyone help me?

Hi Gonzalo G,
What type of data source you are trying to add, did you installed the data source driver and configured the linked server in SQL DB? For File DSN, a data source stored in a file that can be shared among all users who have the same ODBC drivers installed.
These data sources need not be dedicated to a specific user or local to a computer.
Configuring ODBC Data Sources
http://msdn.microsoft.com/en-us/library/ee265698(v=bts.10).aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

ERROR [HY000] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Invalid date string (7497) (pgoe1022.dll)

I am selecting data from a Progress database using the Data Direct Open Edge 10.1.B driver. The target table stores the date values as varchar in this format "22-OCT-14" In the select statement I can use Progress statements or T-SQL to transform
the varchar to a date - but cannot do the same in the WHERE clause
Select po_number, cast(po_date as date) as [po_date] from [po_table]
(no problem - the [po_date] field stored as "22-OCT-14" is returned as "2014-10-22 00:00:00"
but when I include the cast in the where clause I get the error described in the title
Select [po_number], [po_date] from [po_table WHERE cast([po_date] as date)<= '10/22/2014' - NO GOOD
I have tried very many combinations of the date string format , different functions and sub-queries but cannot find an answer

The sql strings I posted are working examples - I've tried the ISO format you included - any number of date formats will work when the target field is a "Date" field - but trying any kind of transform statment to processa date stored
as a varchar in the WHERE CLAUSE throws the erro
Storing dates in a varchar column is a bad idea on any platform. Apparently there are strings in that column which cannot be converted to dates.
On SQL Server you could have found this with
SELECT po_date FROM po_table WHERE isdate(po_date) = 1
What you should use on Progress, I have no idea.
Erland Sommarskog, SQL Server MVP, [email protected]

Rdb ODBC 3.3.2.4 Driver

Similar Messages

Maybe you are looking for