Strongly typed DataSet and custom objects

[John Bonds]

I'm trying to decide if I want to use a strongly typed DataSet or an Untyped
DataSet with its definition in my DataBase module.

The impression I'm getting about strongly typed DataSets is that they have a
lot of design-time and RAD (Rapid App. Dev.) benefits. Basically I want to
build objects that are databound to the DataSet and then build forms that
are databound to my objects. Should I generate a strongly typed dataset or
build a custom one in code?

Thanks,

John

 

[Cowboy \(Gregory A Beamer\)]

The strongly typed dataset also performs better. The downside is the pain of
chaging schemas. If you are filling freeform, you do not have this pain. On
the other hand, when you change data, you are most likely changing UI, as
well, so it is not that big of a point, unless you are autogenning
everything.

--
Gregory A. Beamer
MPV; MCP: +I, SE, SD, DBA

**********************************************************************
Think outside the box!
**********************************************************************

 

[John Bonds]

I just read a post by a guy named Michael Lang:
http://groups.google.com/groups?hl=...te+strongly+typed+dataset+objects&sa=N&tab=wg

It seemed to say that if you are building an application of any size and you
want to do things the "right" way, you should seperate your logic out in the
following layers:

Data Access
Business Logic
User Interface

He also says that this doesn't really fit in with the idea of a strongly
typed dataset. So I'm thinking that I will create a DataSet in my data
module and really only use it for doing stuff like cached updates and stuff
like that. Really only use the functionality that a dataset offers to scale
applications. I'm not really interested in Rapid Application Development
features. I prefer to build a system where it's easy to make changes because
the code structure is good and I have control over the code. I find that
taking some time to write good industrial strength code is enjoyable and
helps me think and piece together all the components of a system.

John

 

[IbrahimMalluf]

Actually, if performace is your most critical requirement, then Strongly
Typed Datasets are not your best option.

Weakly typed datasets offer the best performance provided you are accessing
collection members using index numbers instead of string indexes ie:

MyTable("Employees") is slower than strongly typed datasets
MyTable(0) is faster thasn strongly typed datasets



Ibrahim

 

[John Bonds]

Why is it that looking up by an integer index is slower than looking up by a
string based index?

John