ODBC Direct, Oracle, with Oracle's ODBC Driver

All,

I am attempting to use ODBC Direct to hit the oracle database.  Everything works correctly for the first recordset opened, and then when I attempt to open another recordset (whether or not the first one is closed), the program hangs.  The ODBC Direct calls are correct (I open a workspace and then a connection).  It doesn't matter if I call the queries ASYCH or not, it still hangs..

Any suggestions?
LVL 6
anthonycAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

clifABBCommented:
If I read your question correctly, are you opening a second workspace (hence a second connection) for the second recordset?
If so, don't.
0
clifABBCommented:
The above was posted as a comment.  If it solves your problem, let me know and I'll resubmit it as an answer.
0
anthonycAuthor Commented:
No...... That's not what I am doing.  I am opening 1 workspace, 1 Connection, many recordsets.

I tried substituting Intersolv's driver, no luck.  I wrote a little test program using ODBC Direct on 1 form, RDO ont he other.  RDO works perfectly, ODBC direct hangs
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

bin_huwairibCommented:
anthonyc,

Try to set QueryTimeout property to zero after you open the conneciton.

Example
=======
 Set Cn = Ws.OpenConnection("", dbDriverNoPrompt, False, strConn)
 Cn.QueryTimeout = 0


Bin Huwairib
0
anthonycAuthor Commented:
resubmit that as an answer, it seemed to work.

Anthony
0
bin_huwairibCommented:
anthonyc,

Try to set QueryTimeout property to zero after you open the conneciton.

Example
=======
 Set Cn = Ws.OpenConnection("", dbDriverNoPrompt, False, strConn)
 Cn.QueryTimeout = 0


Best regards
Bin Huwairib
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.