Visual Basic&database, Q:RDO and 32-bit Oracle drivers compatible?

Q:RDO and 32-bit Oracle drivers compatible?

Author	Message
Gerardo P. Fragan #1 / 6	Q:RDO and 32-bit Oracle drivers compatible? Will RDO and RDC work with the new Oracle-supplied 32-bit driver? I believe this is not from Visigenic like the one shipped with VB4 Enterprise Edition. I downloaded the Oracle 32-bit driver recently and it worked fine with Access 7.0. But when I tried it with VB4 and the RDOTEST program from Microsoft, I get a message saying that the "Microsoft ODBC Manager does not support this function". The "function" is a very elementary "select * from <table>" SQL statement. Thanks, GV
Mon, 01 Feb 1999 03:00:00 GMT

Gv Fragan #2 / 6	Q:RDO and 32-bit Oracle drivers compatible? Quote: >The oracle odbc driver is not compliant with the odbc 2.0 specification and >will not work with RDO. Forget the Visigenic one... use either OpenLink's >or Intersolv's drivers. We are using Intersolv's driver and are happy with >the response. Make sure that you upgrade to VB 4.0a and get the RDO 1.0b >upgrade from the MS FTP Software Library. Thank you very much for your response. Could you elaborate why Visigenic is not a favorable choice? Also, how do I upgrade to VB4.0a? I already upgraded to RDO 1.0b. Quote: >We have also found a problem with an open cursor being left on oracle when >opening an RDO resultset. The open cursor is from an rdo prepared >statement that is opened every time you open a resultset. You can get >around this problem by closing the prepared statement when you close the >resultset. We have found that the best way to do this is to explicitly >open a prepared statement (do not give it a name and it will not be added >to the collection), open the resultset using the prepared statement and >then explicitly closing both the resultset and the prepared statement. With what ODBC driver does this occur? OpenLink or InterSolv? Quote: >Good Luck. Thanks. GV
Tue, 02 Feb 1999 03:00:00 GMT

Tim Ricciard #3 / 6	Q:RDO and 32-bit Oracle drivers compatible? The oracle odbc driver is not compliant with the odbc 2.0 specification and will not work with RDO. Forget the Visigenic one... use either OpenLink's or Intersolv's drivers. We are using Intersolv's driver and are happy with the response. Make sure that you upgrade to VB 4.0a and get the RDO 1.0b upgrade from the MS FTP Software Library. We have also found a problem with an open cursor being left on oracle when opening an RDO resultset. The open cursor is from an rdo prepared statement that is opened every time you open a resultset. You can get around this problem by closing the prepared statement when you close the resultset. We have found that the best way to do this is to explicitly open a prepared statement (do not give it a name and it will not be added to the collection), open the resultset using the prepared statement and then explicitly closing both the resultset and the prepared statement. Good Luck. Quote: > Will RDO and RDC work with the new Oracle-supplied 32-bit driver? I believe > this is not from Visigenic like the one shipped with VB4 Enterprise > Edition. I downloaded the Oracle 32-bit driver recently and it worked fine > with Access 7.0. But when I tried it with VB4 and the RDOTEST program from > Microsoft, I get a message saying that the "Microsoft ODBC Manager does not > support this function". The "function" is a very elementary "select * from > <table>" SQL statement. > Thanks, > GV
Tue, 02 Feb 1999 03:00:00 GMT

Chris Thornto #4 / 6	Q:RDO and 32-bit Oracle drivers compatible? Quote: > Forget the Visigenic one... use either OpenLink's > or Intersolv's drivers. We are using Intersolv's driver and are happy with > the response. I tried the OpenLink driver, but it didn't appear to be compatible with SQL*NET. It seems to have its own RPC mechanism, and its own "listener" at the host. My DBA would shoot me if I tried to do this. Did you get the same imperssion? I understand that the Intersolv's driver requires a run-time license. Do you know (about) how much per seat (developer and user)? -- Chris Thornton Eastman Kodak Company (All opinions expressed are my own, and not necessarily those of my employer)
Sun, 14 Feb 1999 03:00:00 GMT

Keith Majk #5 / 6	Q:RDO and 32-bit Oracle drivers compatible? Quote: >> Forget the Visigenic one... use either OpenLink's >> or Intersolv's drivers. We are using Intersolv's driver and are happy with >> the response. >I tried the OpenLink driver, but it didn't appear to be compatible with >SQL*NET. It seems to have its own RPC mechanism, and its own "listener" >at the host. My DBA would shoot me if I tried to do this. Did you get >the same imperssion? OpenLink has two kinds of drivers. The one you tried does have it's own client/server, but I think the "normal" ODBC driver is called OpenLink Lite... Quote: >I understand that the Intersolv's driver requires a run-time license. >Do you know (about) how much per seat (developer and user)? >-- >Chris Thornton >Eastman Kodak Company >(All opinions expressed are my own, and not necessarily those of my >employer)
Tue, 16 Feb 1999 03:00:00 GMT

Chris Thornto #6 / 6	Q:RDO and 32-bit Oracle drivers compatible? Quote: > OpenLink has two kinds of drivers. The one you tried does have it's > own client/server, but I think the "normal" ODBC driver is called > OpenLink Lite... Ah! I'll go check again! Thanks, -- Chris Thornton Eastman Kodak Company (All opinions expressed are my own, and not necessarily those of my employer)
Tue, 16 Feb 1999 03:00:00 GMT

Page 1 of 1

[ 6 post ]