Dbcovert() replacement in ODBC

Hello,
What is the replacement(api) of dbconvert (dblibrary api) in odbc native client?
If there isn't one.......how do we convert from datetime string (yyyymmdd hh:mm:ss.sss) to DBDATETIME?
Thanks

What is the replacement(api) of dbconvert (dblibrary api) in odbc native client?
If there isn't one.......how do we convert from datetime string (yyyymmdd hh:mm:ss.sss) to DBDATETIME?
I don't know if there is an exact replacement for dbconvert but a standard ODBC format for timestamp literals is yyyy-mm-dd hh:mm:ss.sss. You might try simply adding the dashs to the date.
Dan Guzman, SQL Server MVP, http://weblogs.sqlteam.com/dang/

Similar Messages

RecordsetObject faster than ODBC ?

Hi there
We have some DataBase accesses where we use ADO-ODBC Connection. We want to replace ADO-ODBC Connection using SBO's recordset.
Therefore I'm asking you if someboy knows if SBO's recordset object is making DBAccess in a more efficient way than ADO-ODBC is doing and if the recordset object is therefore faster then ADO-ODBC Connection.
regards
Kurt

Hi Kurt,
I don´t think Recordset will be faster than the ADO-ODBC connection, becouse that should be the technology used within Recordset.
The good point on the Recordset is that you should not provide any SQL Server password, as you can use it with the single sign-on.
Anyone can point any other PRO for the recordset?
But of course, it is your choice which one to use.
PD: We usually use ADO with large amount of data.
Regards,
Ibai Peñ

OracleXE- PostgreSQL database link problem

I have set up a database link between Oracle XE and PostgreSQL using unixODBC, but I seem to be having trouble with certain data types.
Here's what I mean...
First I execute the following DDL in postgres:
create table "TEST1" (
"TEST1ID" integer,
"TESTDATE" timestamp,
"TESTVC" varchar(20)
create table "TEST2" (
"A" varchar(125),
"B" varchar(126),
"C" varchar(127),
"D" varchar(128),
"E" varchar(129),
"F" varchar(130),
"G" varchar(200)
The tables look fine when I check them using unixODBC's isql tool.
But here's what SQLPlus tells me...
SQL> desc test1@prism
Name Null? Type
TEST1ID NUMBER(10)
TESTDATE DATE
TESTVC VARCHAR2(20)
SQL> desc test2@prism
Name Null? Type
A VARCHAR2(125)
B VARCHAR2(126)
C VARCHAR2(127)
D VARCHAR2(128 CHAR)
E VARCHAR2(256 CHAR)
F VARCHAR2(512 CHAR)
G VARCHAR2(18432 CHAR)
The "TEST1" table looks fine, but, as you can see from the "TEST2" table, varchar columns longer than 128 characters are really screwy.
Any ideas about how to fix this?
If it helps, here's the trace from the above SQLPlus session:
HOAUTIL.C (1259): ; ------ hoadtab (hoat) -------:
HOAUTIL.C (1262): ; hoatnam: TEST1, hoatnml: 5, hoatnrw: -1, hoatarl: 30
HOAUTIL.C (1273): ; ------ hoadtab (hoai) -------:
HOAUTIL.C (1274): ; n_index_stat: 0
HOAUTIL.C (1224): ; -------- hoadtab for table TEST1---------:
HOAUTIL.C (1225): ; hoadamsz: 3, hoadasiz: 3, hoadambr: 1, hoadabrc: 0
HOAUTIL.C (1228): ; row 0 - hoadambl: 4, hoadadty: 8, hoadaprc: 10, hoadacst: 0
HOAUTIL.C (1232): ; row 0 - hoadascl: 0, hoadanul: 1, hoadanml: 7, hoadanam:
TEST1ID, hoadabfl: 4, hoadamod: 0
HOAUTIL.C (1228): ; row 1 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst:
0
HOAUTIL.C (1232): ; row 1 - hoadascl: 0, hoadanul: 1, hoadanml: 8, hoadanam:
TESTDATE, hoadabfl: 7, hoadamod: 0
HOAUTIL.C (1228): ; row 2 - hoadambl: 20, hoadadty: 108, hoadaprc: 20,
hoadacst: 0
HOAUTIL.C (1232): ; row 2 - hoadascl: 0, hoadanul: 1, hoadanml: 6, hoadanam:
TESTVC, hoadabfl: 20, hoadamod: 0
hoadtab (26): ; hoadtab Exited with retcode = 0.
hoadafr (23): ; hoadafr Entered. id = 0.
hoadafr (23): ; hoadafr Exited with retcode = 0.
hoadtab (26): ; hoadtab Entered. count = 1
hoadtab (26): ; schema_name = , table_name = TEST2
odbc_rec: select * from "TEST2"
r: 165od 0 SQLAllocStmt:- hdbc=8266C78,pst=FF93C95C
r: 188od 0 SQLPrepare:- hst=829D848, css=-7091304
sss = select * from "TEST2"
r:1067od 0 SQLNumResultCols:- hst=829D848,pcol=7
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=1,scn=A,cnm=64,pcn=1,pst=12,
pcd=125,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=1,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=2,scn=B,cnm=64,pcn=1,pst=12,
pcd=126,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=2,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=3,scn=C,cnm=64,pcn=1,pst=12,
pcd=127,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=3,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=4,scn=D,cnm=64,pcn=1,pst=12,
pcd=128,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=4,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=5,scn=E,cnm=64,pcn=1,pst=12,
pcd=129,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=5,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=6,scn=F,cnm=64,pcn=1,pst=12,
pcd=130,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=6,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r:1090od 0 SQLDescribeCol:- hst=829D848,icol=7,scn=G,cnm=64,pcn=1,pst=12,
pcd=200,psc=0,pnul=1
r:1118od 0 SQLColAttributes:- hst=829D848,icol=7,fdt=10,rgbd=0,cbdm=0,pcb
d=FF93C822,pfd=FF93C824
r: 225od 0 SQLFreeStmt:- hst=829D848, fop=1
r:1473od 0 SQLAllocStmt:- hdbc=8266C78,pst=FF93C5A4
r:1486od 0 SQLStatistics:- hst=829D848,scn=0,ccn=0,ssn=0,csn=0,stn=FF93C6
38,ctn=-3,funq=1,fcc=0
scn=, ssn=, stn=TEST2
r:1493od 0 SQLBindCol:- hst=829D848,icl=2,fct=1,rgv=FF93CB88,cbvm=129,pcv
=-7092832
r:1494od 0 SQLBindCol:- hst=829D848,icl=4,fct=5,rgv=FF93C59A,cbvm=0,pcv=-
7092836
r:1495od 0 SQLBindCol:- hst=829D848,icl=6,fct=1,rgv=FF93CAF8,cbvm=129,pcv
=-7092844
r:1496od 0 SQLBindCol:- hst=829D848,icl=7,fct=5,rgv=FF93C58E,cbvm=0,pcv=-
7092848
r:1497od 0 SQLBindCol:- hst=829D848,icl=9,fct=1,rgv=FF93CA68,cbvm=129,pcv
=-7092856
r:1498od 0 SQLBindCol:- hst=829D848,icl=10,fct=1,rgv=FF93C582,cbvm=2,pcv=
-7092860
r:1499od 0 SQLBindCol:- hst=829D848,icl=11,fct=4,rgv=FF93C578,cbvm=0,pcv=
-7092868
r:1500od 0 SQLBindCol:- hst=829D848,icl=12,fct=4,rgv=FF93C570,cbvm=0,pcv=
-7092876
r:1507od 100 SQLFetch:- hst=829D848
r:1589od 0 SQLFreeStmt:- hst=829D848, fop=1
nvOUT (qp_sqtxt.c 55): select NON_UNIQUE, INDEX_NAME, TYPE, SEQ_IN_INDEX,
COLLATION, CARDINALITY, COLUMN_NAME from NAV_PROC:SP_STATISTICS('prism', '%',
'TEST2', 1, 0, 0) order by 3, 1, 2, 4
<<<<<<<<<<<<<<<<<<< Execution Strategy Begin <<<<<<<<<<<<<<<<<<<<<<<<<<<<
Original SQL:
select NON_UNIQUE , INDEX_NAME , TYPE , SEQ_IN_INDEX , COLLATION , CARDINALITY , COLUMN_NAME from NAV_PROC : SP_STATISTICS ( 'prism' , '%' , 'TEST2' , 1 , 0 , 0 ) order by 3 , 1 , 2 , 4
Accessing saved query spec SP_STATISTICS()
from NAV_PROC DB
Execution Strategy End >>>>>>>>>>>>>>>>>>>>>>>>>>>>HOAUTIL.C (1259): ; ------ hoadtab (hoat) -------:
HOAUTIL.C (1262): ; hoatnam: TEST2, hoatnml: 5, hoatnrw: -1, hoatarl: 484
HOAUTIL.C (1273): ; ------ hoadtab (hoai) -------:
HOAUTIL.C (1274): ; n_index_stat: 0
HOAUTIL.C (1224): ; -------- hoadtab for table TEST2---------:
HOAUTIL.C (1225): ; hoadamsz: 7, hoadasiz: 7, hoadambr: 1, hoadabrc: 0
HOAUTIL.C (1228): ; row 0 - hoadambl: 125, hoadadty: 108, hoadaprc: 125,
hoadacst: 0
HOAUTIL.C (1232): ; row 0 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
A, hoadabfl: 125, hoadamod: 0
HOAUTIL.C (1228): ; row 1 - hoadambl: 126, hoadadty: 108, hoadaprc: 126,
hoadacst: 0
HOAUTIL.C (1232): ; row 1 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
B, hoadabfl: 126, hoadamod: 0
HOAUTIL.C (1228): ; row 2 - hoadambl: 127, hoadadty: 108, hoadaprc: 127,
hoadacst: 0
HOAUTIL.C (1232): ; row 2 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
C, hoadabfl: 127, hoadamod: 0
HOAUTIL.C (1228): ; row 3 - hoadambl: 128, hoadadty: 108, hoadaprc: 128,
hoadacst: 0
HOAUTIL.C (1232): ; row 3 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
D, hoadabfl: 128, hoadamod: 0
HOAUTIL.C (1228): ; row 4 - hoadambl: 129, hoadadty: 108, hoadaprc: 129,
hoadacst: 0
HOAUTIL.C (1232): ; row 4 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
E, hoadabfl: 129, hoadamod: 0
HOAUTIL.C (1228): ; row 5 - hoadambl: 130, hoadadty: 108, hoadaprc: 130,
hoadacst: 0
HOAUTIL.C (1232): ; row 5 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
F, hoadabfl: 130, hoadamod: 0
HOAUTIL.C (1228): ; row 6 - hoadambl: 200, hoadadty: 108, hoadaprc: 200,
hoadacst: 0
HOAUTIL.C (1232): ; row 6 - hoadascl: 0, hoadanul: 1, hoadanml: 1, hoadanam:
G, hoadabfl: 200, hoadamod: 0
hoadtab (26): ; hoadtab Exited with retcode = 0.
hoadafr (23): ; hoadafr Entered. id = 0.
hoadafr (23): ; hoadafr Exited with retcode = 0.
hoacomm (11): ; hoacomm Entered. keepinfo = FALSE, tflag = 1.
e:1328od 0 SQLTransact:- henv=0,hdbc=8266C78, ftp=0
e:1334od 0 SQLSetConnectOption:- hdbc=8266C78, fop=102 , vprm=1
hoacomm (11): ; hoacomm Exited with retcode = 0.
hoalgof (8): ; hoalgof Entered. tflag = 1.
nvRETURN (drviunwn.c 779): -1210
i:1231od 0 SQLDisconnect:- hdbc=8266C78
i:1238od 0 SQLFreeConnect:- hdbc=8266C78
(Last message occurred 2 times)
hoalgof (8): ; hoalgof Exited with retcode = 0.
hoaexit (6): ; hoaexit Entered.
hoaexit (6): ; hoaexit Exited with retcode = 0.

user7566651 wrote:
I have set up a database link between Oracle XE and PostgreSQL using unixODBC, but I seem to be having trouble with certain data types.Interesting... Oracle uses standard ODBC API calls to describe the table contents and data types. You will see these as calls "+SQLDescribeCol+" and "+SQLColAttributes+" in your log listing.
This returns the data type of the column. I assume Oracle then maps this to its own data types - for example a string datatype will be mapped to varchar2.
One problem is that Oracle only support string sizes of up to 4000 bytes (including multi-byte charsets). Anything larger than that needs to be a CLOB. Thus the mapping is not a simple 1:1 map - it's a tad more complex than that.
But your foreign table does not touch on these complexities. It uses string data types that should be straight forward to map.
As this (complex mapping) is not the case, one of two possible issues comes to mind.
Oracle has a bug in the way it maps the remote column's data type to an equivalent Oracle SQL data type.
Or, the ODBC driver is returning funky and incorrect data types that Oracle then also maps incorrectly as a result.
I'm more inclined to think the latter - as the ODBC API is a standard and Oracle's Heterogeneous Agent interface that uses it, has been thoroughly tested. So while there can be bugs in the agent's use of the ODBC call interface, I rather think it could be the driver.
The driver needs to provide an interface (govern by ODBC call interface standards) to the client - and map these to the call interface supported by that database (e.g. OCI for Oracle, dblib for SQL-Server, etc). This can be complex - and as I doubt that Postgres's ODBC driver is that widely used and undergo the same amount of intensive testing.
You can confirm/reject this as the error by replacing the ODBC driver (if there are other versions/sources available) and testing Oracle with that.
Or you can use another ODBC client (e.g. isql command line executable) and check what it sees when dealing with this specific ODBC driver against that Postgres database and tables.
An alternative option is to actually debug the ODBC calls made - as the log file includes the parameters passed and responses (with full verbose logging enabled). This will tell you exactly how the Oracle HS agent is using the ODBC call interface, parameters passed and what it sees in return.

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

Replace square brackets in SQL queries against ODBC

We use PowerPivot to access an ODBC provider. PowerPivot generates queries with square brackets, which is not ANSI compliant and incompatible with this ODBC provider. In Office 2010, we had a workaround by modifying this file:
C:\Program Files\Microsoft Analysis Services\AS OLEDB\110\sql2000.xsl
and replace the '[' and ']' with double quotes.
!-- SQL Server 2000 pluggable cartridge -->

<xsl:param name="in_CanUseParams">yes</xsl:param>
<xsl:param name="in_IdentStartQuotingCharacter">[</xsl:param>
<xsl:param name="in_IdentEndQuotingCharacter">]</xsl:param>
However, this workaround does not seem to work after we upgraded to Office 2013. PowerPivot doesn't appear to read this cartridge file anymore. We are familiar with the option to manually write queries to bypass this issue, but we still like to use the generated
queries. Is there another way to replace the square brackets?

I think you could do this:
Code Snippet
SELECT
OUTSIDE
.OUTSIDE_SALES,
INSIDE.INSIDE_SALES,
CUST.CUST_NAME,
SOE.CUSTOMER_NO,
SOE.SALE_ORDER_NO,
SOE.INVOICED_DATE,
PICKUP.PICKUP,
(SOE.SALES_AMT/100) AS SALES,
(SOE.COST_GOODS_SOLD/100) AS COGS,
(SOE.SALES_AMT/100) - (SOE.COST_GOODS_SOLD/100) AS MARGIN,
COUNT(TRACKING.PALLET_ID)
FROM
SOE_HEADER SOE
INNER JOIN CUST_NAME CUST
ON SOE.CUSTOMER_NO = CUST.CUSTOMER_NO
INNER JOIN INSIDE_SALES INSIDE
ON SOE.INSIDE_ROUTE = INSIDE.INSIDE_ROUTE
INNER JOIN OUTSIDE_SALES OUTSIDE
ON SOE.SALESMAN_NO = OUTSIDE.SALESMAN_NO
INNER JOIN PICKUP PICKUP
ON SOE.TYPE_OF_FRGHT = PICKUP.TYPE_OF_FRGHT
INNER JOIN PALLET_SALES_ORD SALES
ON SOE.SALE_ORDER_NO = SALES.SALE_ORDER_NO
INNER JOIN PALLET_TRACKING TRACKING
ON SALES.PALLET_ID = TRACKING.PALLET_ID
WHERE
SOE.TYPE_OF_ORDER = '00'
AND SOE.ORDERS_STATUS = '06'
AND SOE.DATE_OF_ORDER > 20080101
AND SOE.TYPE_OF_FRGHT IN ('06','08','10','13','14')
AND SOE.CUSTOMER_NO <> '1000027000'
AND SOE.CUSTOMER_NO <> '1000039000'
AND SOE.CUSTOMER_NO <> '1014869000'
AND SOE.CUSTOMER_NO <> '1014869001'
AND SOE.CUSTOMER_NO <> '1014869002'
AND SOE.CUSTOMER_NO <> '1014869003'
AND SOE.CUSTOMER_NO <> '1014889000'
AND SOE.CUSTOMER_NO <> '1014890000'
AND SOE.CUSTOMER_NO <> '4400000000'
AND SOE.CUSTOMER_NO <> '4499998000'
AND SOE.CUSTOMER_NO <> '4500012000'
AND SOE.CUSTOMER_NO <> '4500018000'
AND SOE.CUSTOMER_NO <> '6900002000'
AND CUST.CUST_NAME NOT LIKE '%PETCO%'
GROUP BY
OUTSIDE
.OUTSIDE_SALES,
INSIDE.INSIDE_SALES,
CUST.CUST_NAME,
SOE.CUSTOMER_NO,
SOE.SALE_ORDER_NO,
SOE.INVOICED_DATE,
PICKUP.PICKUP,
(SOE.SALES_AMT/100),
(SOE.COST_GOODS_SOLD/100),
(SOE.SALES_AMT/100) - (SOE.COST_GOODS_SOLD/100)
ORDER BY
OUTSIDE
.OUTSIDE_SALES,
CUST.CUST_NAME,
SOE.INVOICED_DATE,
SOE.TYPE_OF_FRGHT
Another option would be to encapsulate the second query in a scalar UDF (if using SQL2k or greater) which would get the count for each sales order and then just return this in your select statement.
HTH!

ODBC IN WIN95 & NT

제품 : ODBC
작성날짜 : 1997-10-10
The ODBC (Open Database Connectivity) interface allows applications to
access data in DBMS ( Database management systems) using SQL(structured query language). Oracle ODBC driver is a DLL that implements ODBC
function callsand interacts with a data source.
The flow of control when communicating from an application through
ODBC to Oracle database is as shown below.
Application
|
ODBC driver manager
|
Oracle7 ODBC Driver
|
OCI layer
|
SQL*Net Driver
|
Network Software
( PCTCP, Novell NetWare, Microsoft LAN Manager, etc,.)
|
SQL*Net Listener
|
Oracle7 RDBMS
When a third party application communicates with the Oracle database
in a Client/Server environment, several dynamic link libraries are
involved. ODBC driver is a DLL that implements ODBC function calls.
The ODBC driver communicates with the OCI layer. The DLLs used in
the OCI layer are part of Required Support Files. Required Support
Files are bundled with SQL*Net. Each version of the ODBC driver is
linked with a specific version of RSF. Each version of SQL*Net is
also dependent on a specific version of RSF. The matrix below shows
the dependency.
ODBC driver| 16/32| Supported | Supported | RSF version | RDBMS
version | bit | Platforms | SQL*NET ver| used | version
1.11.00.05 | 16 | Windows | 2.0.X | 7.0.X | 7.0
| bit | 3.1X | for Windows| |
| | | | |
1.11.01.05 | 16 | Windows | 2.1.X | 7.1.X | 7.1
| bit | 3.1X | for Windows| |
1.14.01.00 | 16 | Windows | 2.2.X | 7.2.X | 7.2
| bit | 3.1X | for Windows| |
1.15.3.0.1A| 16 | Windows | 2.3.X | 7.3.X | 7.3
| bit | 3.1X | for Windows| |
1.15.3.1 | 16 | Windows | 2.3.X | 7.3.2.1.1 | 7.3
| bit | 3.1X | for Windows| |
1.16.3.1A | 16 | Windows | 2.3.X | 7.3.2.1.1 | 7.3
| bit | 3.1X | for Windows| or later |
1.13.05.00 | 32 | Windows NT | 2.2.X | 7.2.X | 7.2
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.13.05.04 | 32 | Windows NT | 2.2.X | 7.2.X | 7.2
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.15.3.0.1A| 32 | Windows NT | 2.3.X | 7.3.X | 7.3
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.15.3.1 | 32 | Windows NT | 2.3.X | 7.3.X | 7.3
| bit | 3.1/3.51 | (32-bit)~~ | |
| | and | | |
| | Windows95 | | |
1.16.3.1.0A| 32 | Windows NT | 2.3.X | 7.3.2.1.1 | 7.3
| bit | 4.0 and | (32-bit)~~ | or later |
| | Windows95 | | |
~~ : You must use SQL*Net for Windows NT, if you are running your
application
on Windows NT. If you are running your application on Windows 95,
you must use SQL*Net for Windows 95.
NOTES:
If you are running an ODBC driver not listed in the above matrix, we
strongly recommend that you upgrade your ODBC driver.
Basics:
If your application is a 32-bit application, you must use 32-bit Oracle
ODBC driver and 32-bit SQL*Net for the platform, your application is
targeted. For a 16-bit application, you must use 16-bit Oracle ODBC
driver along with SQL*Net for Windows(16-bit).
SQL*Net Version 1.X
If you are using SQL*Net Version 1.X, your connection should work
against 7.2 or older Oracle databases. SQL*Net Version 1.X was
de-supported June 30,1996. We recommend that you upgrade your SQL*Net.
Connecting to Standalone Personal Oracle Database:
If you connect to a local, standalone Personal Oracle database, you
will use a two-task driver ( In the above flow chart the two-task
driver will replace SQL*Net). The connect string is 2:<SID> where
<SID> is the instance ID. The default SID is ORCL. (no period)
ODBC Documentation:
The Oracle7 ODBC driver comes with on-line help. The help file name
is DRVORA7*.HLP * could take values NULL, 1, or 2 depending upon the
version of the Oracle ODBC driver installed.
For ODBC API documentation, refer ODBC 2.0 Programmer's Reference and
SDK Guide from Microsoft Press. The online version of ODBC 2.0
Programmer's Reference and SDK guide is part of MSVC++ compiler.
Version of Oracle product: How to find ?
To find the versions of Oracle software installed on your machine run
the Oracle installer (ORAINST.EXE). In case of errors, versions
numbers are an important part of problem definition.
Common ODBC Q&A
Q. I have two ODBC drivers, 1.11.0.5.0 and 1.11.1.5.0. Which driver
should I install?
A. The version of the ODBC driver you will install is dependent on the
Required Support Files (RSF) you have on your system. If you are
running RSF 7.0.X, you need to install 1.11.5.0. If you are running
RSF 7.1X, you need to install 1.11.1.5.0.
You can find the RSF version by running ORAINST.EXE, the Oracle installer.
When ORAINST.EXE is run the Software Asset Manager displays the
products
available to install as well as those products already installed.
Search for the Required Support File and make note of the version.
Q. What other products do I need so that the ODBC driver works?
A. You definitely need the appropriate SQL*Net version (16-bit or 32-bit).
Make sure that SQL*Net is installed and configured correctly before you
try to connect through ODBC. For example, if you are using 32-bit ODBC
driver for Windows 95, and TCP/IP is your protocol, you must have SQL*Net
for Windows 95 (TCP/IP) installed and configured, before you can make a
connection through ODBC.
Note: If you are connecting to a standalone Personal Oracle7 for
MS Windows, you do not need SQL*Net. Personal Oracle7 uses a two
task driver - SQL2TT.dll to connect to its standalone databse.
32-bit ODBC driver required 32-bit SQL*Net and
16-bit ODBC driver requires 16-bit SQLNet.
You also need the appropriate version of Required Support Files installed
on your system.
Error: specified driver could not be located
solution:
a) Check the odbc driver is present (see 1. above) and pointed to.
b) Check correct RSFs are installed and OH\bin is on the DOS path.
For Windows can set the DOS path in autoexec.bat or before
running windows. For Win 95 can only set in autoexec.bat. For
NT can set in autoexec.bat but usually through Control Panel,
System - has list of system environment variables.
c) For older installs nettest may be available else may have
tnsping. If this or any Oracle product can connect then the
net (and Sqlnet if Oracle product) is ok.
Error: error occurred in networking software, check log file
c:\msocklib.txt
but only from ODBC connections - other oracle products are fine.
Log file: TSR/DLL version incorrect
Solution:
a) Check the version of msocklib.dll. Sqlplus etc often picks up
the correct one whereas ODBC will use the DOS path. Ensure
OH\bin is first in the DOS path.
Problem: Have ODBC 1.11 and Sqlnet 2.2 and getting gpfs in nls dlls etc.
Solution:
a) Generally any version of the RSFs can call any equivalent or
later version of Sqlnet. In 2.2 of Sqlnet they changed the
calls so they were no longer backwardly compatible. This was
fixed in Sqlnet 2.3. Thus 7.0 and 7.1 RSFs can use net 2.0, 2.1
or 2.3.
Problem: Want to connect to a V6 database.
Answer: Can't. ODBC queries the dictionary views which changed in O7.
Problem: Using Lotus Approach version 3.0 and having various problems,
eg no tables being retrieved for users.
Solution: Get a patch from Lotus to take Approach to version 3.0.2.
Problem: VB Enterprise Edition (4.0) provides a remote data control.
This gives "driver not capable" errors.
Reason: The data control uses RDO which we would not support most
features of anyway since RDO is ODBC level 2 (see compliancy
above). There is also a bug (371374) that prevents any part
of it being used.
Problem: Calling a stored procedure from Visual C++ with an out
character parameter gives ora-6502: numeric or value error.
Solution: a) initialise the C variable before it is passed to the
procedure.
b) make the C variable a char and not an unsigned char (uchar).
Problem: Getting a "driver not capable" error when calling
SQLBindParameter or SQLSetParam.
Solution: Change any references to SQL_C_ULONG or SQL_C_SLONG to
SQL_C_LONG (equivalent of SQL_C_SLONG). SQL_C_ULONG and
SQL_C_SLONG are level 2 datatypes and so not supported.
Note SQLBindParameter is also level 2 but is allowed since
our drivers simply convert the calls to SQLSetParam.
Problem: With NLS settings such that the NLS_NUMERIC_CHARACTERS are
the opposite to usual (G = . and D = ,) a fetch of a decimal
number gives "SQLSTATE: 22005, Native Return Code: 0" errors
when querying through ODBCTEST, MS Query etc.
Solution: This is a bug (297648) which is fixed in the 1.16 ODBC drivers.
Question: Is there an ODBC driver for use with Java?
Answer: JavaSoft is currently writing one for Oracle 7 on SUNOS.
General Suggestions:
Please read the release notes and the online documentation. They contain
important information.
In case of error, please write down the entire error message as seen on the
monitor(screen). An error message is key in finding the problem.
Where can I get Oracle ODBC drivers?
The Oracle ODBC drivers are available as free products on the world-wide web.
The URL is http://www.oracle.com/

try to use trust connection in sql server
and it will work

How to pass Multi and Singlr value Parameters to DB2 query, which is using in SSRS report for ODBC connection

Hi Guys,
I am using DB2 database in SSRS. I have to pass Single Value and Multi Value Parameters. I tried with Select * From DB2Table Where
Column=@PRM_Name Or Select * From DB2Table Where
Column=:PRM_Name . It is not working and throwing error. Please help me out.
Connection Details: ODBC
Thanks Shiven:)

Hi SKM,
So you mean to say that Go to DataSource->Add Dataset-> Query Type-Text-> Under Query:
click on fx (Expression)-> Write this expression
For Single Value Parameter:
="SELECT customer_name, telephone_number, address1, address2, city from MyTable
WHERE city = '" + Parameters!City.Value + "'"
OR
="SELECT customer_name, telephone_number, address1, address2, city from MyTable
WHERE city = '" & Parameters!City.Value & "'"
Keep it in mind if Parameter is String then
It should be in Single quote ''.
Like
="SELECT customer_name, telephone_number, address1, address2, city from MyTable WHERE city
='Hyderabad' "
For Multivalu Parameter:
="SELECT EmployeeID, FirstName, LastName, LoginID FROM SHIVEN.AUDIT Where FirstName
in ('" + REPLACE(JOIN(Parameters!City.Value,","),",","','") + "')"
NOTE:
If your Parameter is Single Value Parameter and You want to enter string values with Coma (,)
separated (Like Hyderabad, Chennai, Delhi).
In this case, you have to use below expression.
="SELECT customer_name, telephone_number, address1, address2, city from MyTable
WHERE city IN ('" + REPLACE(Parameters!City.Value ,",","','") + "')"
OR
="SELECT customer_name, telephone_number, address1, address2, city from MyTable
WHERE city IN ('" & REPLACE(Parameters!City.Value ,",","','") & "')"
In above expression: Replace will replace all , with ‘,’ and city IN (‘Hyderabad’, ‘Chennai’,
‘Delhi’) will not throw any error.
Note: You have to write expression in one line in Expression editor for dataset
query
Thanks It is working fine but it is tough job if query is big.
Hi S kumar,
The above approach we use when we have source like DB2, becasue DB2 has some syntactical differences to pass multivalue paramaeter. I tested and it works good, if i am mentioning the query in above format by using Fx button while creating dataset.
but if we want fetch data from view which exist in DB2 and we need to call db2 view in SSRS and pass multivalue parameter in a way we did above then could you please mention the steps and way to achieve this.
Thanks in advance!

How pass ext characters to a stored proc by odbc when enable sqlserver syntax is on??

how pass french characters or extended characters to a stored procedure by odbc
error: ORA-01756: quoted string not properly terminated
une chaine entre apostrophhes ne se termine pas correctement
oracle Retrieving extended characters thru ODBC
PL/SQL procedure parameters
hi, i hope you can help to me.
I have a problem with french and german characters.
i have a little stored procedure than return what i'm passing to him.
see these example: (the second one work fine on plsql)
first exemple:
1) i created a new odbc dsn
2) i'm going into sqlserver migration tab to choose
Enable Exac Syntax.
3) i'm open Winsql (this is a odbc tools)
http://www.indus-soft.com/winsql/
4) i'm write
exec ksp_test 0,'HiLLO ORACLE'
i receive this error:
Error: ORA-01756: quoted string not properly terminated
(State:S1000, Native Code: 6DC)
I trying to changed too the NLS_LANG in the registry
like FRENCH_CANADA.WE8ISO8859P1
French_France.WE8ISO8859P1
but without any success..
i got the same problem with
oracle 9 database with utf8 characters set.
oracle 8.1.7 with iso8859p1 characters set.
i trying all latest odbc driver from oracle website.
second exemple:
SQL> variable mytest refcursor;
SQL> exec ksp_test (0,'HiLLO ORACLE',:MYTEST);
PL/SQL procedure successfully completed.
SQL> PRINT MYTEST;
Your Database Value
HiLLO ORACLE
CREATE OR REPLACE PACKAGE KSP_PLSQLRSETPKG
AS
TYPE RCT1 IS REF CURSOR;
END;
CREATE OR REPLACE PROCEDURE KSP_TEST (
PATCH INT DEFAULT 0,
PONC VARCHAR2,
RC1 IN OUT KSP_PLSQLRSETPkg.RCT1
AS
BEGIN
OPEN RC1 FOR
SELECT PONC "Your Database Value" FROM DUAL;
FROM DUAL;
RETURN ;
END;
i'm trying also different nls setting but no good result.
AMERICAN_AMERICA.US7ASCII
AMERICAN_AMERICA.WE8MSWIN1252
FRENCH_CANADA.WE8DEC
FRENCH_CANADA.UTF8
FRENCH_CANADA.WE8MSWIN1252
FRENCH_FRANCE.WE8DEC
FRENCH_FRANCE.UTF8
FRENCH_FRANCE.WE8MSWIN1252
is working well on sqlplus but not by odbc..
also..
i'm declare a variable and
i set
v_variable := 'id'
and the procedure return the good syntax...
i think is a odbc driver problem....
the driver don't want to accept a extended characters set by a parameters coming from the procedure.
can you confirm to me ..this is a major bug for the driver..
my procedure is very basic to make a little test.
did you try my procedure to be sure you have the same problem?
i try with a oracle instance utf8,WE8MSWIN1252 and
i got always the same problem.
if i write insert into test values ('di');
everything is fine...but when i call the procedure...
the procedure don't want to accept any german..french or any extended characters...
our application is working by odbc driver.
i'm pretty sure is a bug in the driver ...the bug is coming only when i select "ENABLE EXEC SYNTAX" IN THE DSN (SQLSERVER MIGRATION SECTION) ... i try with Shema Database and Owner and Empty and i got
always the same problem
exec KSP_TEST 0,'TiEST'
------------------------>>>>>>>NOT WORKING.
BUT IF I WRITE
CALL KSP_TEST (0,'TiEST')
------------------------->>>>IS WORKING
if i select enable exec or i unselect enable exec...
the CALL KSP_TEST...... is always working properly.
BETWEEN THESE SYNTAX THE NLS_LANG IS NEVER CHANGED....
IS WORKING.....THE NLS_LANG IS GOOD.......because i make a little modification in procedure to be sure the INSERT IS inside the database CORRECTLY.
CREATE OR REPLACE PROCEDURE KSP_TEST
PATCH INT,
PONC VARCHAR2
AS
v_test varchar2(100);
BEGIN
v_test := 'test';
INSERT INTO YYY VALUES (PONC);
END;

If "just using Crystal Reports XI R2" means using Crystal Report Viewer and do not want to see the prompt, please follow the below steps.
1. Select the report you want to see
2. Select "Process" tab
3. Select Parameters menu under the process tab.
4. You would see two date parameters there.
Select the [Empty] value for each parameter and fill out the value you want.
Hope this would help.

ODBC 8.1.7 Error when calling a stored procedure that owned by an other user

I am testing my application VB for certified to use the
Client 8 with ODBC Driver 8.1.7.0 , because today this application
have been working with Client 7 and ODBC driver 7.3 version 2.5.
But i have some surprises:
Set qy = con.CreateQuery("", "{CALL OFS.INSERT_DEPT (?,?,?)}")
OFS is the owner of the proc
(other combinations {BEGIN ...;END;} also doesn't work, except the owner executes the stmt)
qy(0) = "6"
qy(1) = "ABCDEF"
qy(2) = "L88"
at this point it gives an VB error:
40041 Object Collection: Couldn't find item indicated by text.
PS: With previous ODBC Driver 7.3 v2.5 this error doesn4t occur.
I have the rights to execute the procedure
GRANT EXECUTE ON OFS.DEPT TO OFS_USERS;
Is there any other way to get this procedure work? Its a BUG ?
My Procedure:
create or replace procedure INSERT_DEPT(
in_deptno in number,
in_dname in varchar2,
in_loc in varchar2)
is
begin
insert into dept(deptno, dname, loc)
values(in_deptno, in_dname, in_loc);
end;
show errors;
GRANT EXECUTE ON OFS.INSERT_DEPT TO OFS_USERS;
Environment:
Client:
VB 5.0 SP3 (using RDO 2.0)
NT 4.0 SP6
Oracle8i Client 8.1.7.0.0
Oracle ODBC Driver 8.1.7.0.0
PS: This error already occured with Oracle ODBC Driver 8.1.7.7.0
Server:
Oracle8i Enterprise Edition Release 8.1.7.4.1
Win 2000 SP2
Thanks in advance.

I have no problem executing that statement from ODBCTest on my machine
Client:
Win2k,
Oracle ODBC driver 8.1.7.7
Oracle client 8.1.7.0
Server:
Oracle 8.1.7.0
First, can you try replacing the ?'s with explicit parameters? I can't imagine that an error binding the variables would cause an error like this, but I'd just like to rule it out.
Second, can you grab the ODBC SDK from Microsoft <http://www.microsoft.com/data> if you haven't already and try that statement from within the ODBCTest sample application? If that works for you, then there must be something in the layers between your application and the ODBC driver which are confusing things. Which API are you actually using from VB? I'm guessing ADO, but I'd like confirmation on that.
Third, did you set any parameters to non-default values when you configured your DSN? I left everything as-is on my machine, so I'll try to replicate any changes you might have made to see if that changes anything.
Finally, can you post the connection string you're using?
Justin

CR10 viewer : Error ODBC Access on Windows Vista with multi-JOIN

Post Author: Stephane
CA Forum: Data Connectivity and SQL
Hi all,
I've got an error using a report in CR10 viewer on Windows Vista + Access 2000 :
"Echec de l'ouverture d'un jeu de lignes. Détails : 4200:[Microsoft][Pilote ODBC Microsoft Access] Erreur de syntaxe dans la clause FROM."
wich can be translate :
"4200:[Microsoft][ODBC Microsoft Access Driver] Syntax error in FROM clause."
This error only appear on Vista + Access, not on Vista + SQL and not on XP + Access.
The SQL query of my report (see details below) contains lots of INNER JOIN and 2 LEFT OUTER JOIN. If I replace those 2 LEFT OUTER JOIN by 2 INNER JOIN, the reports displays (but is wrong).
Somebody knows this problem?
Thanks in advance for your help.
Stephane.
The SQL query below :
SELECT TblDataCurrentValue.`ValDtaId`, TblDataCurrentValue.`ValIdShape`, TblDataCurrentValue.`ValOk`, TblDataCurrentValue.`ValMain`, TblDataCurrentValue.`ValIndex`, TblDataCurrentValue.`ValValue`, TblDataCurrentValue.`ValValueId`, TblDataLinks.`LnkDtaIdPrimary`, TblDataValues.`ItmValue`, TblDataValues.`ItmColor`, TblData.`DtaLabel`, tblGraphs.`GId`, tblGraphs.`GName`, tblGraphs.`GRef`, TblShapesGraph.`ShTextShape`FROM ((((`TblDataCurrentValue` TblDataCurrentValue LEFT OUTER JOIN `TblDataValues` TblDataValues ON TblDataCurrentValue.`ValValueId` = TblDataValues.`ItmId` AND TblDataCurrentValue.`ValDtaId` = TblDataValues.`ItmDtaId`) INNER JOIN `TblData` TblData ON TblDataCurrentValue.`ValDtaId` = TblData.`DtaId`) INNER JOIN `tblGraphs` tblGraphs ON TblDataCurrentValue.`ValIdGraph` = tblGraphs.`GId`) INNER JOIN `TblShapesGraph` TblShapesGraph ON TblDataCurrentValue.`ValIdShape` = TblShapesGraph.`ShIdShape`) LEFT OUTER JOIN `TblDataLinks` TblDataLinks ON TblDataCurrentValue.`ValDtaId` = TblDataLinks.`LnkDtaId`WHERE TblDataCurrentValue.`ValOk` <> 0ORDER BY tblGraphs.`GId` ASC, TblDataCurrentValue.`ValIdShape` ASC

Moving back to the 10_2 instant client works. Not certain why there is an issue with the 11_2 client.

Error updating data source from SQL Server ODBC into SQL Native Client 10.0

I am converting Crystal 8.5 reports into Crystal XI release 2. The data source was ODBC using SQL Server 2000 and pointing to a stored procedure. In the new server the data source has to be ODBC again, but it uses the SQL Native Client 10.0 Driver, because the new server is SQL Server 2008. I have copied the same old stored procedure on the new server and it works fine as a data source to a brand new Crystal XI report. But when I am opening an existing 8.5 version crystal report and updating the data source to the new location I get the error message "Some tables could not be replaced, as no match was found in the new data source".
I thought I could tackle this error by creating a temporary data source using the standard ODBC SQL Driver linked to the SQL 2008 Server instead of the SQL Native Client 10 ODBC. So I first updated the crystal data source to link to this temp ODBC using SQL Driver and it worked fine. But after that, when I try to update the data source to link to the SQL Native Client 10 ODBC, I get the same error again.
So I guess that the problem is not the new server itself, but the switch between SQL Server ODBC and SQL Native Client 10 ODBC.
Does anyone know what's going on with this SQL Native Client 10 in updating crystal report data sources?

CR XI does not support that driver. Try selecting the Native driver or upgrade to CR XI R2 for free and use SP4, 5 and 6 and then FP 6.4 or upgrade to CR 2008 and SP 3 and Fix Pack 3.3
Thank you
Don

ODBC Connection problem with SQL Native Client driver with CR 11

I am having an issue connecting my crystal reports to an ODBC connection that uses the SQL Native Client driver (Version 2005.90.2047.00). My reports work fine when using the SQL Server driver (Version 2000.85.3006.00). The ODBC connection is setup to use Integrated Windows Authentication and is defaulted to go to the correct database. When I test the ODBC connection in the 'ODBC Data Source Adminstrator' it connects fine.
The reports are trying to connect to stored procedures on a SQL Server 2005 database. I can log onto the ODBC connection in CR X1. When I try to set the Datasource connection for one of my reports to the ODBC connection I created, I get the following error:
'Some tables could not be replaced, as no match was found in the new data source. Please specify the table required for any unmodified tables.'
When I drill down to the SP and try to update the datasource location of the SP directly I get the following errors:
'Data Object cannot be opened/accessed'
and
'Unknown Database Connector Error'
As I said, I don't have any problems when using the SQL Server 2000 driver. One other thing to mention, when I initially connect to the ODBC connection in CR X1 with the SQL Native Client driver, it asks for a username and password. I leave these blank since I'm using Windows Authentication.
Any advice would be appreciated.
System:
Windows XP
Service Pack 3
Crystal Reports XI:
Product Version 11.0.0.1282

Hi Jeff,
I just tried to create a new report using the native driver and there is no option to use Trusted Authentication. This would be why it's failing.
I don't believe we fully supported Native driver in Cr XI. Try downloading CR Xi R2 and install SP6 from this info:
Go to this link: http://www.sdn.sap.com/irj/boc and download the trial version of CR XI R2 and use your XI keycode, then apply the patches which you can get to by clicking on the BusinessObjects tab above, then Downloads.
Direct link to the Trial version: http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx
I tested it in R2 and the Trusted Authentication option is there so your reports should work.
Thank you
Don

Connection failed: SQLState:'01000' SQL Server Error:67 [Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState:'08001' SQL Server Error:17 [Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist o

Help,
setup a new sql server 2012 on a windows 2012r2 server to replace old sql server 2005 on an old windows server 2003 machine. When i test the ODBC connection locally on the server it works fine, however when i try to connect via windows 7 client machine
i get the following error:
Connection failed:
SQLState:'01000'
SQL Server Error:67
[Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState:'08001'
SQL Server Error:17
[Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
I think it must be a permissions thing, I've turned off the firewall for now and still no difference, 've also made sure remote connection is enabled. I can connect to the other sql server in studio manager on the new machine however, i can't go do
the same in the old server, says:
cannot connect to hbfsqlpro1\hbfsqlpro1
Additonal information a network related or instance specifc error occured while establising a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL server is configured to
allow remote connections. (provider:SQL Network Interfaces, error 26 - error locationg server/instance specified) (Microsoft SQL server)
the instance is def correct, as that is what i use to connect locally on the new machine and what it comes up on the studio manager on the new machine. STarting to pull my hair out somewhat, i'm sure it's something really simple!

Hello,
You are trying to connect to a named instance. Make sure the SQL Server Browser service is started on the SQL Server computer.
Make sure TCP/IP is enabled.
http://msdn.microsoft.com/en-us/library/ms191294(v=sql.110).aspx
Try to disable Windows Firewall or security software on both, SQL Server instance and client computer.
Test basic connectivity too. Try to ping from the client computer to the SQL Server computer.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Using BV stored in the repository brings up ODBC(RDO) dialog box

Post Author: matthewh
CA Forum: Data Connectivity and SQL
                                                  Hi - not sure if this is the right forum - tried elsewhere on this site with no joy, and been struggling with this for 2 days now, and I really need it sorted, so here goes:I'm trying
to get a report designed on my desktop PC with Crystal XI connecting
to my remote server running Crystal Server XI R2 & MySQL 5. I have
a business view created and I can access it fine via the repository, but when I go to
create the report or browse the data in the fields I get the ODBC (RDO)
dialogue box asking for a DSN! Surely the point of the server is that it
handles all the connectivity? I have the password stored with the
connection in the repository on the server - have I set up something
incorrectly at the server end? I've used all bog-standard settings,
nothing fancy or different and using Enterprise authentication. I've tried using single sign-on but couldn't get it to work. This
is my first proper report against a data warehouse I'm building and my
first use of Crystal Server in anger, so it's possible I've missed
something. Also - is the Data Connection user name and password the Enterprise user name or the database user name?

Hi Houffle,
You need to provide more details. For example, I cannot reproduce the behavior you describe by doing the following:
1. Create a "minprivs" user on a 10g XE database
2. Grant connect, resource to minprivs;
3. Create a connection for minprivs of type=Basic with Host/Port/SID=localhost/1521/xe
4. Connect to minprivs
5. Create a procedure in minprivs (without any dependencies on any other schema):
create or replace PROCEDURE secure_dml
IS
BEGIN
IF TO_CHAR (SYSDATE, 'HH24:MI') NOT BETWEEN '08:00' AND '18:00'
        OR TO_CHAR (SYSDATE, 'DY') IN ('SAT', 'SUN') THEN
     RAISE_APPLICATION_ERROR (-20205,
          'You may only make changes during normal office hours');
END IF;
END secure_dml;Running this procedure either normally or in debug mode works without an additional password prompt. It does not matter whether the Save Password check box was ticked or not in the New / Select Database Connection dialog.
Regards,
Gary
SQL Developer Team

JDBC ODBC bridge for MS Access - language/locale problems

Hi,
I have an application that uses a MS Access database.
I have a user in Turkey that is experiencing the following problem:
My Java app requests for example the following query:
select name from activitiesThen I get the following error:
java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver]
The Microsoft Jet database engine cannot find
the input table or query 'ACT�V�T�ES'.
Make sure it exists and that its name is spelled correctly.Apparantly the character 'i' is replaced by '�', how can I avoid this?

Hi,
I was looking for something in that direction.
When I start the db connection using charset="Turkish" i get the following error:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d6cb0b2, pid=4480, tid=5000
# Java VM: Java HotSpot(TM) Client VM (1.5.0_04-b05 mixed mode)
# Problematic frame:
# V [jvm.dll+0x8b0b2]
# An error report file with more information is saved as hs_err_pid4480.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#Is this because my MS Access does not recognize the charset?
What should I use if I don't pas the 'Turkey' argument, just 'utf-8'?
Message was edited by:
fredje_2000

Dbcovert() replacement in ODBC

Similar Messages

Maybe you are looking for