By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,306 Members | 1,621 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,306 IT Pros & Developers. It's quick & easy.

Strongly Typed DataSet Vs Un-Typed Dataset

P: n/a
I am confused how strongly typed dataset is different from un-typed dataset.
Is there any good link explaining pros and cons of both? Which one should be
used preferably?
Jul 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Job,

A strongly typed dataset is not different from an untyped dataset.

It is still the same dataset.

Although a strongly typed has some methods and properties in it that helps
to make it more describing, does it still inherits from dataset. It has
never more performance then if you use an untyped datasets with the same
methods.

What you want to use is mostly a matter of preference. An objective to
choose that can be how much your team is. How much the experience in the
team is. etc etc.

I am forever confused by the by VSNet generated strongly typed dataset
because of the names that those use and prefer therefore normally the
untyped dataset. (However, just my preference).

A little extra problem is that a "generated" strongly typed dataset is not
easily to change, it is forever renewed, so when you do yourself some
additions to it, than you loose those when there has to be changed something
and generates than a new strongly type dataset and your additions are gone.

Most is just my thought,

Cor
Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.