|
-
Oct 7th, 2002, 01:42 AM
#1
Thread Starter
Hyperactive Member
VB to Oracle
Hi guys, I haven't needed to talk to an Oracle databse for sometime. Is the best way to do it still ODBC?
That's Mr Mullet to you, you mulletless wonder.
-
Oct 7th, 2002, 03:17 AM
#2
ADO ?
See able computing link below...
Vince
Feeling like a fly on the inside of a closed window (Thunk!)
If I post a lot, it is because I am bored at work! ;D Or stuck...
* Anything I post can be only my opinion. Advice etc is up to you to persue...
-
Oct 7th, 2002, 03:30 AM
#3
Thread Starter
Hyperactive Member
Cheers Vince, that link was exactly what I needed and yes ADO does seem to be the best method.
That's Mr Mullet to you, you mulletless wonder.
-
Oct 7th, 2002, 07:11 AM
#4
Fanatic Member
Originally posted by Paul Warren
Cheers Vince, that link was exactly what I needed and yes ADO does seem to be the best method.
Paul, from the perspective of someone whose bread and butter is VB Oracle, I'd confirm ADO is ideal, but you need to consider these points:
OO4O is quicker still - one less layer, basically direct connection to the Oracle Call Interface (OCI). However, it's a new learning curve, and not supoprted as well as ADO.
If you use ADO and OLE DB, use Microsofts OLE DB version, not Oracles - it's ****.
Do most of your coding in PLSQL - it's quick, and not too difficult to pick up (plus its another language on the CV)
Check out the VB Oracle books from Wrox publishing - they cut thorugh the crap and also give some nive COM tutorials.
-
Oct 7th, 2002, 07:19 AM
#5
Thread Starter
Hyperactive Member
Cheers Gaffer, I had heard of OO4O but like you say it's a learning curve and I haven't got time unfortunately. We're using stored procedures here so no need to delve into PLSQL although I've done lot's of Oracle before so if needs be...although that was version 7.31!
That's Mr Mullet to you, you mulletless wonder.
-
Oct 7th, 2002, 08:07 AM
#6
Fanatic Member
Originally posted by Paul Warren
Cheers Gaffer, I had heard of OO4O but like you say it's a learning curve and I haven't got time unfortunately. We're using stored procedures here so no need to delve into PLSQL although I've done lot's of Oracle before so if needs be...although that was version 7.31!
Heh, yeah Oracle only stated to sort out PLSQL in version 8i - dynamic SQL was a blimmin nightmare prior to 8i....
check out those Wrox books though - even if you don;t buy them, you can download the tutorial files from their website.
-
Oct 8th, 2002, 08:15 AM
#7
Thread Starter
Hyperactive Member
Gaffer - What do I need for the Data Source in my connection string? I'm used to using DSN with ODBC but it looks different with OLE DB?
That's Mr Mullet to you, you mulletless wonder.
-
Oct 8th, 2002, 09:25 AM
#8
Fanatic Member
Try this:
cn.ConnectionString = "Provider=MSDAORA.1;Password=password;User ID=userid;Data Source=dbname;Persist Security Info=False"
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|