connectivity to Oracle

[rahul]

Hello every1
Can any1 tell me that What are teh various methods by which we can
connect our
database in sql to our project's front end which is in VB ??
I wanna know the pros and cons of various types of Connectivities?

[RobinS]

You need to give more information. Is your project in VB6,
VB.Net, or VB2005? Is your database Oracle? What kind of
connectivity? Are you talking about a desktop app using the
database for display and reporting and updates?

Robin S.
-------------------------
"rahul" <ra********@gmail.comwrote in message
news:11**********************@h40g2000cwb.googlegr oups.com...

Hello every1
Can any1 tell me that What are teh various methods by which we can
connect our
database in sql to our project's front end which is in VB ??
I wanna know the pros and cons of various types of Connectivities?

[rahul]

Yeah Robi thanx 4 ur concern..
My project is VB6. and tables,i mean database is in oracle.
So wat r the various methods by which i can connect a form of vb to the
table there in oracle?
I mean i don't wanna open recordsets and write long queries.
Each field in the form should directly get it value form the table
fields by itself.
So ,is that possible??
RobinS wrote:

You need to give more information. Is your project in VB6,
VB.Net, or VB2005? Is your database Oracle? What kind of
connectivity? Are you talking about a desktop app using the
database for display and reporting and updates?

Robin S.
-------------------------
"rahul" <ra********@gmail.comwrote in message
news:11**********************@h40g2000cwb.googlegr oups.com...

Hello every1
Can any1 tell me that What are teh various methods by which we can
connect our
database in sql to our project's front end which is in VB ??
I wanna know the pros and cons of various types of Connectivities?

[RobinS]

You should post VB6 questions to comp.lang.basic.visual.misc
and/or microsoft.public.vb. (The first one seems more active.)

That said, you are talking about data binding an Oracle database
to some fields on a form in VB6, right?

Data binding in VB6 was not reliable, and generally not used.
So you might be able to do that, but it would not be recommended.
You might be able to get away with it if you are only
viewing data. Check out ADO and the ADODC control.

Microsoft didn't really "fix" databinding until VB2005.

Robin S.
--------------------------------------
"rahul" <ra********@gmail.comwrote in message
news:11********************@v33g2000cwv.googlegrou ps.com...

Yeah Robi thanx 4 ur concern..
My project is VB6. and tables,i mean database is in oracle.
So wat r the various methods by which i can connect a form of vb to
the
table there in oracle?
I mean i don't wanna open recordsets and write long queries.
Each field in the form should directly get it value form the table
fields by itself.
So ,is that possible??
RobinS wrote:

>You need to give more information. Is your project in VB6,
VB.Net, or VB2005? Is your database Oracle? What kind of
connectivity? Are you talking about a desktop app using the
database for display and reporting and updates?

Robin S.
-------------------------
"rahul" <ra********@gmail.comwrote in message
news:11**********************@h40g2000cwb.googleg roups.com...

Hello every1
Can any1 tell me that What are teh various methods by which we can
connect our
database in sql to our project's front end which is in VB ??
I wanna know the pros and cons of various types of Connectivities?

[Cor Ligthert [MVP]]

>

Microsoft didn't really "fix" databinding until VB2005.

Robin, there have not been much changes after the 2002 version. (Some names
are changed and some new classes are created mostly from old ones).

Cor

[RobinS]

What I understand is that when they first developed VB.Net,
MS pretty much thought WinForms and desktop apps would go
by the wayside, so they concentrated on the web development
aspect. Then they found out they were wrong.

So with VB2005, they revisited the entire issue and rewrote
the backend of the forms stuff and added all the now-working
databinding capability.

I learned this listening to the guys on the DotNetRocks podcast.

Robin S.
-------------------------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:eJ**************@TK2MSFTNGP03.phx.gbl...

Microsoft didn't really "fix" databinding until VB2005.

Robin, there have not been much changes after the 2002 version. (Some
names are changed and some new classes are created mostly from old
ones).

Cor

[Cor Ligthert [MVP]]

Robin,

Than he is completely wrong. The strongly typed dataset has some changes
both (and different) in ASPNET and WindowForms. I don't like the path ASPNET
is going. Some years to go and we can take back the documentation around the
classic ASP in my opinion. The guys now on top of that department do in my
idea not understand what were the great advantages in ASPNET in the
2002/2003 version (although it was far from complete). If you now create a
dataset with ASPNET than it is incompatible with the windowsform version
2005. This was not in 2002/2003 where you could intermix a DataSet and all
its behaviour in Windowsform, Webservices, PDA, ASPNET.

You can see it slightly because we have now Projects and Websites which were
in 2002/2003 only Projects, something new in the 2005 version. ASPNET does
remind me always to the movie Back to the Future.

Cor



"RobinS" <Ro****@NoSpam.yah.noneschreef in bericht
news:UY******************************@comcast.com. ..

What I understand is that when they first developed VB.Net,
MS pretty much thought WinForms and desktop apps would go
by the wayside, so they concentrated on the web development
aspect. Then they found out they were wrong.

So with VB2005, they revisited the entire issue and rewrote
the backend of the forms stuff and added all the now-working
databinding capability.

I learned this listening to the guys on the DotNetRocks podcast.

Robin S.
-------------------------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:eJ**************@TK2MSFTNGP03.phx.gbl...

>
Microsoft didn't really "fix" databinding until VB2005.

Robin, there have not been much changes after the 2002 version. (Some
names are changed and some new classes are created mostly from old ones).

Cor

[RobinS]

Does that mean you can no longer define a Business Layer (project),
a web site project, and a win form project in the same solution?
I haven't done any web stuff yet (next step); I've been concentrating
on learning VB2005. I thought you could use the same BL and DAL with
both a WinForm and web project. Maybe you can, but not share a
dataset?

Thanks for the info.

Robin S.
-------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

Robin,

Than he is completely wrong. The strongly typed dataset has some
changes both (and different) in ASPNET and WindowForms. I don't like
the path ASPNET is going. Some years to go and we can take back the
documentation around the classic ASP in my opinion. The guys now on
top of that department do in my idea not understand what were the
great advantages in ASPNET in the 2002/2003 version (although it was
far from complete). If you now create a dataset with ASPNET than it is
incompatible with the windowsform version 2005. This was not in
2002/2003 where you could intermix a DataSet and all its behaviour in
Windowsform, Webservices, PDA, ASPNET.

You can see it slightly because we have now Projects and Websites
which were in 2002/2003 only Projects, something new in the 2005
version. ASPNET does remind me always to the movie Back to the Future.

Cor



"RobinS" <Ro****@NoSpam.yah.noneschreef in bericht
news:UY******************************@comcast.com. ..

>What I understand is that when they first developed VB.Net,
MS pretty much thought WinForms and desktop apps would go
by the wayside, so they concentrated on the web development
aspect. Then they found out they were wrong.

So with VB2005, they revisited the entire issue and rewrote
the backend of the forms stuff and added all the now-working
databinding capability.

I learned this listening to the guys on the DotNetRocks podcast.

Robin S.
-------------------------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:eJ**************@TK2MSFTNGP03.phx.gbl...

>>
Microsoft didn't really "fix" databinding until VB2005.

Robin, there have not been much changes after the 2002 version.
(Some names are changed and some new classes are created mostly from
old ones).

Cor

[Cor Ligthert [MVP]]

Robin,

The wizards generates different code (not a real class in ASPNET just a
single XML file) as well is in my idea the connection string saved in
another way.

(At least that it was last year)

Cor

"RobinS" <Ro****@NoSpam.yah.noneschreef in bericht
news:Ct******************************@comcast.com. ..

Does that mean you can no longer define a Business Layer (project),
a web site project, and a win form project in the same solution?
I haven't done any web stuff yet (next step); I've been concentrating
on learning VB2005. I thought you could use the same BL and DAL with
both a WinForm and web project. Maybe you can, but not share a
dataset?

Thanks for the info.

Robin S.
-------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>Robin,

Than he is completely wrong. The strongly typed dataset has some changes
both (and different) in ASPNET and WindowForms. I don't like the path
ASPNET is going. Some years to go and we can take back the documentation
around the classic ASP in my opinion. The guys now on top of that
department do in my idea not understand what were the great advantages
in ASPNET in the 2002/2003 version (although it was far from complete).
If you now create a dataset with ASPNET than it is incompatible with the
windowsform version 2005. This was not in 2002/2003 where you could
intermix a DataSet and all its behaviour in Windowsform, Webservices,
PDA, ASPNET.

You can see it slightly because we have now Projects and Websites which
were in 2002/2003 only Projects, something new in the 2005 version.
ASPNET does remind me always to the movie Back to the Future.

Cor



"RobinS" <Ro****@NoSpam.yah.noneschreef in bericht
news:UY******************************@comcast.com ...

>>What I understand is that when they first developed VB.Net,
MS pretty much thought WinForms and desktop apps would go
by the wayside, so they concentrated on the web development
aspect. Then they found out they were wrong.

So with VB2005, they revisited the entire issue and rewrote
the backend of the forms stuff and added all the now-working
databinding capability.

I learned this listening to the guys on the DotNetRocks podcast.

Robin S.
-------------------------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:eJ**************@TK2MSFTNGP03.phx.gbl...

Microsoft didn't really "fix" databinding until VB2005.
>
Robin, there have not been much changes after the 2002 version. (Some
names are changed and some new classes are created mostly from old
ones).

Cor

[RobinS]

Thanks. I think I'll wait and worry about this when I start doing
ASP.Net. :-)
Robin S.
------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:O1**************@TK2MSFTNGP04.phx.gbl...

Robin,

The wizards generates different code (not a real class in ASPNET just
a single XML file) as well is in my idea the connection string saved
in another way.

(At least that it was last year)

Cor

"RobinS" <Ro****@NoSpam.yah.noneschreef in bericht
news:Ct******************************@comcast.com. ..

>Does that mean you can no longer define a Business Layer (project),
a web site project, and a win form project in the same solution?
I haven't done any web stuff yet (next step); I've been concentrating
on learning VB2005. I thought you could use the same BL and DAL with
both a WinForm and web project. Maybe you can, but not share a
dataset?

Thanks for the info.

Robin S.
-------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>>Robin,

Than he is completely wrong. The strongly typed dataset has some
changes both (and different) in ASPNET and WindowForms. I don't like
the path ASPNET is going. Some years to go and we can take back the
documentation around the classic ASP in my opinion. The guys now on
top of that department do in my idea not understand what were the
great advantages in ASPNET in the 2002/2003 version (although it was
far from complete). If you now create a dataset with ASPNET than it
is incompatible with the windowsform version 2005. This was not in
2002/2003 where you could intermix a DataSet and all its behaviour
in Windowsform, Webservices, PDA, ASPNET.

You can see it slightly because we have now Projects and Websites
which were in 2002/2003 only Projects, something new in the 2005
version. ASPNET does remind me always to the movie Back to the
Future.

Cor



"RobinS" <Ro****@NoSpam.yah.noneschreef in bericht
news:UY******************************@comcast.co m...
What I understand is that when they first developed VB.Net,
MS pretty much thought WinForms and desktop apps would go
by the wayside, so they concentrated on the web development
aspect. Then they found out they were wrong.

So with VB2005, they revisited the entire issue and rewrote
the backend of the forms stuff and added all the now-working
databinding capability.

I learned this listening to the guys on the DotNetRocks podcast.

Robin S.
-------------------------------------
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:eJ**************@TK2MSFTNGP03.phx.gbl...

>Microsoft didn't really "fix" databinding until VB2005.
>>
Robin, there have not been much changes after the 2002 version.
(Some names are changed and some new classes are created mostly
from old ones).
>
Cor
>